Mandatory Sprint 2 Codewars Katas
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 30/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- content
Research direction
Open the linked Codewars collection and review the Sprint 2 mandatory katas. Complete all katas, then use the Codewars Progress Checker and submit the resulting link; the issue also points to the CYF Codewars documentation and Slack help channels.
Written by the indexing model from the issue text.
Description
Link to the coursework
https://www.codewars.com/collections/cyf-data-groups-sprint-2-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 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 Data Groups | Sprint 2 | 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
- 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
-
🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 2 Core Module-Data-Groups Submit:Issue
Difficulty 1/5 1-3 hours Newbie friendliness 58/100
-
🏝️ Priority Stretch 🐂 Size Medium 📅 Sprint 3 Module-Data-Groups Optional Submit:None
Difficulty 1/5 Under an hour Newbie friendliness 35/100
All issues in CodeYourFuture/Module-Data-Groups
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