Welcome to the Youth Coding League! YCL staff will be tracking students’ (coders) progress through the Youth Coding League at YouthCodingLeague.com. Coders will be able to see how they rank against other Youth Coding League coders and schools (teams), and parents will be able to follow along with what their kids are learning throughout the semester. Here’s how YCL staff will be tracking coder and team scores throughout the league.
A note on scores and team rankings:
- Team rankings will be based on an average of the coders’ scores.
- For teams with 9 coders or less, 100% of their coder scores count towards their team score.
- For teams with 10 or more coders, 90% of coder scores count towards their team score.
- For teams with 20 or more coders, 85% of coder scores count towards their team score.
- For teams with 30 or more coders, 75% of coder scores count towards their team score.
- Scoring is broken out by attribute below; coders can score up to 10 points per attribute and up to 80 points per sprint.
- Coder scores will be cumulative as they accrue.
Attributes Tracked Each Sprint
- What it is: Attendance.
- What we’re looking for: Did the coder attend YCL that sprint or session? We track this in the CS First dashboard (or YCL Coders dashboard, for YCL Curriculum users) by seeing if the student completed steps + completed work.
- What it is: Code documentation, an important skill that developers use daily in the workplace.
- What we’re looking for: Did the coder answer the reflection or discussion questions provided by CS First in the comments section of their Scratch project (or by the YCL Staff in the "Review" section of their Coders Dashboard, for YCL Curriculum users), and did they do so fully and thoughtfully and in-depth versus minimal, one-word answers?
- What it is: Steps completed for each sprint.
- What we’re looking for: Did the coder complete each step in the day’s curriculum, including answering any included surveys and watching the videos? We track this by reviewing how many steps were completed for each sprint in the CS First dashboard under Student Progress (or in the YCL Coders Dashboard, for YCL Curriculum users).
- What it is: Objectives completed.
- What we’re looking for: Did the coder complete all of the stated objectives for each sprint?
- What it is: Additional objectives (add-ons) completed.
- What we’re looking for: How many add-ons the coder attempted and successfully executed.
- What it is: Quality assurance.
- What we’re looking for: Does the project work smoothly and as intended?
- What it is: Coder feedback
- What we’re looking for: Did the coder provide feedback for a teammate in their own comment box?
- Coders will look at a teammate's project and then add a line of feedback in their own project's comment box. They should include the CSusername of the teammate that they are writing the feedback about.
- For coders using the YCL Curriculum, add feedback to the "Review" section of their own Coders dashboard. They should include the YCL handle of the teammate that they are writing the feedback about.
- Examples of a 0-points Collaboration score:
- No feedback listed
- Silly nonsense words
- “I liked it”
- Examples of a 10-point Collaboration score:
- “I really like how they used the “if/then” block to show that if ___ occurred, then ___ would happen.”
- “It worked fine until I got to ___ part, and it stopped working. They could debug ___ to make it better.”
- What it is: Creativity.
- What we’re looking for: How creative and involved the coder made their project.
Epics and Milestones
Epics are overall thematic challenges that go above and beyond the eight attributes of the daily sprint scoring. Each Epic is made up of a Milestone that corresponds with each sprint.
The Scribe Epic is creative, and intended to tell a story.
The Explorer Epic is a technical, open-ended component; each milestone can be completed in a variety of ways. The end result is what’s important, and how it is completed is secondary.
The Sage Epic rewards kids who successfully complete every single Add-On for each sprint.
The Cerebral Assassin Epic carries over into other seasons and is tracked by a CS Username and is numerically based; for example, the 100! Milestone rewards a coder with a perfect score of 80 for any one sprint.
Coder vs. Coder
The Coder vs. Coder Epic rewards team participation; the Team Work Makes the Dream Work milestone is awarded when a coder joins a team and submits a group playoff project.