Check module success criteria
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 30/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- documentation
Research direction
Start with the linked coursework success page and compare its criteria with your current module work. Discuss a shared plan in your cohort channel, then submit the required work through the CYF dashboard; done means your own submissions meet the listed success criteria and you understand them well enough to redo the work.
Written by the indexing model from the issue text.
Description
Link to the coursework
https://programming.codeyourfuture.io/structuring-data/success/
Why are we doing this?
🔑 The most important thing is that you are secure in your understanding.
At the end of the course, we will expect you to build novel applications using your understanding. If you cannot build things, we cannot put you forward for jobs. It is in your personal interest to make sure you have properly understood this module.
To progress to the next module you need to meet the success criteria for this module. How will you meet the module success criteria? Discuss it in your class channel and make a plan together.
🧑🏿🎤 good strategies
- asking volunteers to review your code
- helping each other with coursework blockers
- arranging midweek study sessions
- using Saturday time to review code together
🙅🏿 bad strategies
- opening empty PRs
- copying and pasting
- breaking the Trainee Agreement
- mistaking the measure for the target
Maximum time in hours
.5
How to get help
Discuss with your cohort. Support each other.
How to submit
At the end of your module you will need to submit your own work in the CYF dashboard. This means things like pull requests you have written sent from your GitHub account, and Google Docs you have written.
What you need to submit is listed on the success page for the module.
Remember - the goal is your understanding. If you are not confident you could delete and re-do the work you're submitting easily, you should take more time to revise the topics. It's more important that you understand the work, than that it gets done quickly.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 397
- PR merge metrics
- No merged PRs in 30d
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-Structuring-and-Testing-Data
-
🏕 Priority Mandatory 📅 Sprint 1 Core Submit:None
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
🏕 Priority Mandatory 📅 Sprint 3 Core Module-Structuring-And-Testing-Data Submit:None 🦔 Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 1 Submit:PR
Difficulty 3/5 1-2 days Newbie friendliness 72/100
-
:gear: bug 📅 Sprint 3 Module-Structuring-And-Testing-Data NotCoursework
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
-
🏕 Priority Mandatory 📅 Sprint 1 Core Module-Structuring-And-Testing-Data Submit:None 🦔 Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 35/100
All issues in CodeYourFuture/Module-Structuring-and-Testing-Data
Similar issues
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AllTheMods/ATM-10-L#19 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
SignalK/n2k-signalk#345 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
JuliaPluto/PlutoPlotly.jl#72 ·