CodeYourFuture / CodeYourFuture/Module-Servers

[TECH ED] Codewars

未关闭
#7 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
🎯 Topic Code Review 🎯 Topic Problem-Solving 🎯 Topic Programming Fundamentals 🎯 Topic Requirements 🎯 Topic Time Management 🏕 Priority Mandatory 📅 Servers 📅 Week 1
主要语言
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.

贡献指南

打开贡献指南

调研方向

从链接的 CodeYourFuture Codewars 集合和 CYF Codewars 文档开始。完成本周至少三个 kata,三次每次至少投入 20 分钟,并检查进度是否可通过公开的 Codewars API 查看;未指定任何 repository 文件或测试。

由索引模型根据 Issue 内容生成。

评估

领域
documentation
Issue 类型
文档
难度
1/5
预计耗时
1 小时以内
活跃度
停滞
描述清晰度
需要澄清
新手友好度
25/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。