CodeYourFuture / CodeYourFuture/Module-Data-Groups

Check module success criteria

未关闭
#6 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
🏕 Priority Mandatory 📅 Sprint 1 Module-Data-Groups Setup Submit:None 🦔 Size Tiny
主要语言
JavaScript
星标
1
派生
326
平均合并
3 小时 25 分钟
30 天内合并 PR
2

描述

### Link to the coursework

https://programming.codeyourfuture.io/data-groups/success/

### Why are we doing this?

### 🔑 The most important thing is that you are secure in your understanding.

At the end of the course, we will expect you to build novel applications _using your understanding_. If you cannot build things, we cannot put you forward for jobs. It is in your personal interest to make sure you have properly understood this module.

To progress to the next module you need to meet the success criteria for this module. How will you as a cohort meet the module success criteria? Discuss it in your class channel and make a plan together.

### 🧑🏿‍🎤 good strategies
- asking volunteers to review your code
- helping each other with coursework blockers
- arranging midweek study sessions
- using Saturday time to review code and cohort tracker

### 🙅🏿 bad strategies
- opening empty PRs
- copying and pasting
- breaking the [Trainee Agreement](https://docs.codeyourfuture.io/organisation/agreements-and-rules/student-agreement)
- mistaking the measure for the target

### Maximum time in hours

.5

### How to get help

Discuss with your cohort. Support each other.

### How to submit

At the end of your module you will need to submit your own work in the CYF dashboard. This means things like pull requests you have written sent from your GitHub account, and Google Docs you have written.

What you need to submit is listed on the success page for the module.

Remember - the goal is your understanding. If you are not confident you could delete and re-do the work you're submitting easily, you should take more time to revise the topics. It's more important that you understand the work, than that it gets done quickly.

贡献指南

打开贡献指南

调研方向

首先阅读链接的模块成功标准页面,并将其与此 issue 中描述的预期进行比较。与 cohort 讨论任何缺失或不明确的标准,然后确认该页面和提交指南清楚地说明学习者必须完成和提交的内容。

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

评估

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

把新 issue 发到你的邮箱

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