CodeYourFuture / CodeYourFuture/Module-Servers

[TECH ED] Codewars

未關閉
#9 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
🎯 Topic Code Review 🎯 Topic Problem-Solving 🎯 Topic Programming Fundamentals 🎯 Topic Requirements 🎯 Topic Time Management 🏕 Priority Mandatory 📅 Servers
主要語言
JavaScript
星號
0
分支
74
PR 合併指標
30 天內沒有已合併 PR

描述

### 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](https://www.codewars.com/users/CodeYourFuture/authored_collections).

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](https://docs.codeyourfuture.io/leaders/running-the-course/codewars)
- Read [Codewars advice from CYFers](https://docs.codeyourfuture.io/leaders/running-the-course/codewars/codewars-advice-from-cyfers)
- Read [Codewars advice from mentors](https://docs.codeyourfuture.io/leaders/running-the-course/codewars/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.

貢獻指南

開啟貢獻指南

研究方向

從連結的 Codewars 集合和 CYF Codewars 文件開始,包括建議頁面。至少完成三次每週 kata 練習,檢查朝向必要的 Final Projects 集合和 5 kyu 級別的進度,並使用 #cyf-codewars 頻道或讀書會獲得支援;進度會自動追蹤,因此不需要提交程式碼。

由索引模型根據 Issue 內容生成。

評估

領域
content, documentation
Issue 類型
文件
難度
1/5
預估耗時
1 小時以內
活躍度
停滯
描述清晰度
描述清楚
新手友好度
20/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。