Mandatory Sprint 2 Codewars Katas

Open
#372 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
content

Research direction

Start with the linked Codewars collection and the Codewars Progress Checker. Complete the mandatory katas, then submit the progress-checker URL as described; check the collection naming because the issue references both Sprint 2 and Sprint 1. Use the linked CYF Codewars documentation or #cyf-codewars for help.

Written by the indexing model from the issue text.

Description

🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 2 Core Module-Data-Flows Submit:None
Link to the coursework

https://www.codewars.com/collections/cyf-data-flows-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 Flows | 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 pair programming slot from the available pairing appointments in the CYF Pair Programming 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
276
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeYourFuture/Module-Data-Flows

All issues in CodeYourFuture/Module-Data-Flows

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.