Give a demo in a demo session
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 55/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- content
Research direction
Start by checking the presenting guide linked in the issue and the Slack announcements for a Tuesday or Friday demo session. Done means attending at least one session, giving a 1–10 minute demo with a CYF staff member present, and attaching a screenshot showing the presentation and feedback.
Written by the indexing model from the issue text.
Description
Presenting information is really important. You need to start practicing giving demos.
During this module, you must attend at least one demo session, and give at least one demo. We recommend you come to more, and give more. But you are required to do at least one. Your demo can be on anything you want. You can give this demo in any sprint.
There are demo sessions every Tuesday evening and Friday morning. They are advertised on Slack.
Aim for a 5 minute demo. But your demo must be at least 1 minute and at most 10 minutes long. Check out our guide about presenting.
You can present anything you want. If you're stuck for ideas, some examples:
- Explain a term you have learnt and show how it works
- Tell us about a blocker you experienced and how you tackled it
- Show something you have made
- Show a tool that assists your learning
- Tell us about your dream job and how you will get there
- Teach us something about one of your hobbies
You will need to attach a screenshot when submitting your Step for this Module. Make sure to take a screenshot of you presenting on the call, showing that one of the following members of CYF staff was on your call and gave you feedback:
- Daniel Wagner-Hall
- Karen Klein
- Colin Farquhar
- Poonam Rajput
- Léon McGregor
- Liam Greenfield
If you are not available during any of the demo times, please message on Slack to arrange an alternate time.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 327
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CodeYourFuture/Module-Data-Groups
-
🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 1 Core Module-Data-Groups Submit:None 🦔 Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
📅 Sprint 1 NotCoursework
CodeYourFuture/Module-Data-Groups#1443 · 1 assignee ·
-
🏝️ Priority Stretch 🐇 Size Small 📅 Sprint 2 Module-Data-Groups Optional Submit:Issue
Difficulty 1/5 Under an hour Newbie friendliness 58/100
-
🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 2 Core Module-Data-Groups Submit:Issue
Difficulty 1/5 1-3 hours Newbie friendliness 58/100
-
🏝️ Priority Stretch 🐂 Size Medium 📅 Sprint 3 Module-Data-Groups Optional Submit:None
Difficulty 1/5 Under an hour Newbie friendliness 35/100
All issues in CodeYourFuture/Module-Data-Groups
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
palladius/rails8-app-on-gcp#145 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
dotenvx/dotenv-vscode#139 ·
-
test-change-proposal
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
web-platform-tests/interop#1455 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100