Week by week coursework review

[SallyMcGrath]

Which module(s) and week(s) does this change affect? Module(s): ALL Week(s): ALL

What is the work that needs to be done?

Review each week's coursework and mark non-essential work as stretch.

Why is this work important to do?

We keep adding work in the syllabus and not taking work away. This is progressively making our course less accessible to people with only the minimum time commitment available (20h).

We already have nominated one key piece each week, with a key symbol, for prioritisation.

There may be some pieces we can stop assigning. There are some pieces currently mandatory that might be ok to set to stretch. Inside some coursework, there are some pieces set as mandatory that might be skippable. For example, in JS1 there are many many exercises exploring methods that might be skippable for some trainees.

I have made a ticket for each week of the course (28) and anyone can grab a week and complete the ticket. There is no need to do it in order. Just grab the ticket when you have capacity, add your name, and get started. Please don't own tickets you are not actively working on.

You will need to update in each place this work exists: the syllabus, the Boilerplate Google Classroom, and the coursework repos

• Syllabus: https://syllabus.codeyourfuture.io/
• Boilerplate Google Classroom: https://classroom.google.com/c/MzYyMTYyNjEwMDMx
• Coursework Repos: https://github.com/CodeYourFuture/Table-of-Contents

Please connect to both the issue you have selected AND this ticket on your PR, by typing # and then typing 494

HTML-CSS

• [ ] #495
• [ ] #496
• [ ] #497
• [ ] #498

JS1

• [ ] #499
• [ ] #500
• [ ] #501
• [ ] #502

JS2

• [ ] #503
• [ ] #504
• [ ] #505
• [ ] #506

JS3

• [ ] #507
• [ ] #508
• [ ] #509
• [ ] #510

React

• [ ] #511
• [ ] #512
• [ ] #514
• [ ] #516

Node

• [ ] #517
• [ ] #518
• [ ] #519
• [ ] #520

Databases

• [ ] #521
• [ ] #522
• [ ] #523
• [ ] #524

Additional context

Who might need to know about this change?