[TECH ED] Codewars
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 20/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- content, documentation
Research direction
Start with the linked Codewars collection and the CYF Codewars documentation, including the advice pages. Complete at least three weekly kata sessions, check progress toward the required Final Projects collection and 5 kyu level, and use the #cyf-codewars channel or a study group for support; progress is tracked automatically, so no code submission is needed.
Written by the indexing model from the issue text.
Description
Link to the coursework
https://www.codewars.com/users/CodeYourFuture/authored_collections
Why are we doing this?
Every week you need to complete at least three kata. Spend at least 20 minutes, three times a week, on your kata workout.
Find the Collection for this week on the CodeYourFuture account.
Take some time to check your levels. Before you are accepted on to a Final Project on the developer track, you need to complete the Final Projects collection and reach a Level 5 kyu in Codewars. Are you on track to reach this standard? Have you run a study group to work on kata? Have you reached out on the #cyf-codewars channel? What is your plan to meet this goal?
Maximum time in hours (Tech has max 16 per week total)
1
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
Remember, after 20 minutes, take a break.
How to submit
Your codewars progress is tracked automatically and is available on the public API. You don't need to submit it.
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
- 74
- 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-Servers
-
π Priority Mandatory π Size Small π Servers π Week 2
Difficulty 1/5 1-3 hours Newbie friendliness 62/100
CodeYourFuture/Module-Servers#21 Β·
-
π― Topic Problem-Solving π― Topic Programming Fundamentals π Priority Mandatory π Servers π Week 4 π¦ Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 45/100
CodeYourFuture/Module-Servers#142 Β·
-
π― Topic Problem-Solving π― Topic Testing π Priority Mandatory π Size Small π Servers π Week 1
CodeYourFuture/Module-Servers#141 Β· 1 assignee Β·
-
[TECH ED] APIs Open:brain: Prep work π― Topic Programming Fundamentals π― Topic Requirements π― Topic Teamwork π Priority Mandatory π Servers π Week 1 π¦ Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 35/100
CodeYourFuture/Module-Servers#140 Β·
-
[PD] Give feedback Openπ Priority Mandatory π Size Medium π Servers π Week 2
Difficulty 1/5 1-3 hours Newbie friendliness 35/100
CodeYourFuture/Module-Servers#139 Β·
All issues in CodeYourFuture/Module-Servers
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