Check module success criteria
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Under an hour
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- content, documentation
Research direction
Start by reading the linked module success criteria page and compare it with the expectations described in this issue. Discuss any missing or unclear criteria with the cohort, then confirm that the page and the submission guidance clearly describe what learners must complete and submit.
Written by the indexing model from the issue text.
Description
Link to the coursework
https://programming.codeyourfuture.io/data-groups/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 as a cohort 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 and cohort tracker
๐ ๐ฟ 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
- 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
CodeYourFuture/Module-Data-Groups#945 ยท
-
๐ Priority Mandatory ๐ Size Medium ๐ Sprint 2 Core Module-Data-Groups Submit:Issue
Difficulty 1/5 1-3 hours Newbie friendliness 58/100
CodeYourFuture/Module-Data-Groups#944 ยท
-
๐๏ธ Priority Stretch ๐ Size Medium ๐ Sprint 3 Module-Data-Groups Optional Submit:None
Difficulty 1/5 Under an hour Newbie friendliness 35/100
CodeYourFuture/Module-Data-Groups#941 ยท
All issues in CodeYourFuture/Module-Data-Groups
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 ยท