Mandatory Sprint 1 Codewars Katas
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- documentation
Research direction
Start with the linked Codewars collection, then use the Codewars Progress Checker to check the required kata list and your completion status. Read the linked Codewars guidance or use the #cyf-codewars channel if you need help. Done means completing all mandatory Sprint 1 katas and submitting the resulting progress-checker link.
Written by the indexing model from the issue text.
Description
Link to the coursework
https://www.codewars.com/collections/cyf-structuring-plus-testing-data-sprint-1-mandatory
Learning Objectives
- Practice applying concepts related to the sprint's prep material in a kata.
- Problem solve a new coding challenge.
Why are we doing this?
Every week, you need to complete all of the katas in the collection. If you have extra time, you can do extra katas (either from the stretch codewars task or at random on CodeWars).
Spend at least 20 minutes per kata, find time at least three times a week to complete this.
Find the Collection called "CYF Structuring + Testing Data | Sprint 1 | Mandatory" on the CodeYourFuture account.
Check your Codewars completion status via the Codewars Progress Checker.
Maximum time in hours
2
How to get help
Join the #cyf-codewars Slack channel
Read the CYF Codewars docs
Read Codewars advice from CYFers
Read Codewars advice from mentors
Book a mentored coding slot from the available appointments in the CYF Mentored Coding Slack Canvas
How to submit
Share a link in the form https://codeyourfuture.github.io/Codewars-Progress-Checker/#YOUR_CODEWARS_USERNAME.
You can obtain the link from the browser location bar after submitting your Codewars username on the Codewars Progress Checker page.
How to review
Once you have completed your kata, look at the other solutions in the solutions view. Consider how many different approaches there are.
- 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 ·