This repository has been archived by the owner on Aug 17, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 123
Week by week coursework review #494
Labels
enhancement
New feature or request
Comments
This was referenced Oct 27, 2022
Closed
Closed
Closed
Closed
This was referenced Oct 27, 2022
This was referenced Oct 27, 2022
40thieves
added a commit
to CodeYourFuture/JavaScript-Core-1-Coursework-Week4
that referenced
this issue
Apr 1, 2023
We did it! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Please connect to both the issue you have selected AND this ticket on your PR, by typing # and then typing 494
HTML-CSS
JS1
JS2
JS3
React
Node
Databases
Additional context
Who might need to know about this change?
The text was updated successfully, but these errors were encountered: