Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

πŸ§‘πŸΎβ€βš–οΈ Check module success criteria #12

Open
4 tasks
SallyMcGrath opened this issue Jul 16, 2024 · 0 comments
Open
4 tasks
Labels
πŸ• Priority Mandatory This work is expected πŸ“… React πŸ¦” Size Tiny Less than 30 minutes 🎯 Topic Code Review Reading, understanding, and analysing code 🎯 Topic Communication Reading, writing, speaking, and listening in English; expressing our ideas 🎯 Topic Delivery Shipping our work, deploying our code, delivering our product 🎯 Topic Requirements Interpreting requirements with precision and accuracy 🎯 Topic Teamwork Working productively with other people 🎯 Topic Testing It's important that software works and that people can use it 🎯 Topic Time Management Managing competing needs and meeting deadlines πŸ“… Week 3 Assigned during Week 3 of this module πŸ“… Week 4 Assigned during Week 4 of this module

Comments

@SallyMcGrath
Copy link
Collaborator

Link to the coursework

https://curriculum.codeyourfuture.io/react/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.

Strategies

πŸ§‘πŸΏβ€πŸŽ€ 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
  • 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

In week 4 of your module you will need a representative to report to the organisation. Here's your template, fill in your details and delete as appropriate:

Template

πŸ“ˆ Cohort Progress Report from @cohort-name to @programme-team

  • criterion
  • criterion
  • criterion
  • criterion

βœ… We are progressing to the next module.
β›” We are taking a consolidation week to meet our targets.

@SallyMcGrath SallyMcGrath added 🎯 Topic Code Review Reading, understanding, and analysing code 🎯 Topic Communication Reading, writing, speaking, and listening in English; expressing our ideas 🎯 Topic Delivery Shipping our work, deploying our code, delivering our product 🎯 Topic Requirements Interpreting requirements with precision and accuracy 🎯 Topic Teamwork Working productively with other people 🎯 Topic Testing It's important that software works and that people can use it 🎯 Topic Time Management Managing competing needs and meeting deadlines πŸ• Priority Mandatory This work is expected πŸ“… React πŸ“… Week 3 Assigned during Week 3 of this module πŸ“… Week 4 Assigned during Week 4 of this module πŸ¦” Size Tiny Less than 30 minutes labels Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
πŸ• Priority Mandatory This work is expected πŸ“… React πŸ¦” Size Tiny Less than 30 minutes 🎯 Topic Code Review Reading, understanding, and analysing code 🎯 Topic Communication Reading, writing, speaking, and listening in English; expressing our ideas 🎯 Topic Delivery Shipping our work, deploying our code, delivering our product 🎯 Topic Requirements Interpreting requirements with precision and accuracy 🎯 Topic Teamwork Working productively with other people 🎯 Topic Testing It's important that software works and that people can use it 🎯 Topic Time Management Managing competing needs and meeting deadlines πŸ“… Week 3 Assigned during Week 3 of this module πŸ“… Week 4 Assigned during Week 4 of this module
Projects
None yet
Development

No branches or pull requests

1 participant