Frontend Advanced JS

[bhas]

Summary

Issue: #73

Tip

You can see the final output on GitHub here

Added Advanced Javascript content week 1-4 according to the proposal.

• Proposal
• Previous discussion
• Existing JS material:
  • JS2 week 2 (new week 1)
  • JS2 week 3 (new week 2)
  • JS3 week 2 (new week 3)
  • JS3 week 3 (new week 4)

Additional ideas:

• Split the module into 2 so each can be catered to its specialization
• TODO Create new homework project for each specialization.

Homework & Project

Below is a suggestion on a project we can run for each specialization which cover the same topics but tailored to their track:
OBS we should keep in mind which modules runs before and after.

Notes

• Removed Scopes from the learning goals of week 2 because JS2 week 3 didn't include it. It is taught in JS1 Week 2

[adamblanchard]

Really nice, thanks for taking on this big task @bhas!

Regarding the overall content, learning goals, and flow of the weeks i think it looks great.

Regarding the frontend/backend split: While i think the examples/exercises make sense to stay quite generic during the lessons (to focus on the concepts) I'm assuming we would tweak them in the backend version to be more backend-orientated (and vice versa, where necessary, but lots of them looked more frontendy to me).

Same goes for assignments.

Let me know if you have a different plan, but I'm up for trying to get stuff merged and iterating in smaller PRs. It could make sense to me to:

1. Tidy this up as the "frontend advanced js" module
2. Feel free to leave any major "todo" like the assignment projects, which we can raise another PR for. Also like updating all the "homework" words to "assignment". Just keep a list of the other tasks we still need to do. I can also help with some of those, or other people can too, if you'd like.
3. Complete the backend version in another PR

That's just a suggestion, if you have other plans on how to keep it moving that's also cool 👌

[adamblanchard]

Would we ideally use different examples in the backend version of the module? I'm wondering about what you are expecting to change as part of creating the backend version.

[bhas]

I think we would have to have a look at the content once it gets a bit more refined. I am also neither and expert on js nor node. So it is a bit hard for me to come up with great examples

[adamblanchard]

Oh, and fyi i created a "module template" to try and keep all the new modules in a similar structured format https://github.com/HackYourFuture-CPH/programme/tree/main/contributing/templates/module

If you're copying and pasting legacy content, you don't have to change it all to suit the template in this PR. Just fyi for the future, in case you didn't see that yet. We can do that in another PR after this, if needed!

[adamblanchard]

Bjørn and I chatted on a call about the status and next steps.

Things left:

1. We do have the legacy assignments in place, but maybe we'd like to run a project instead. Take this decisions along with the "what do we do about meal sharing/final projects" discussion, and see if we should run something from this module as well.
2. Week 4 only covers classes. A reasonable topic, but not for a full week. Maybe reduce to 50% and add something else. Or cover practice previous topics more.
3. This PR covers frontend only. We need a backend version of this module too.
4. There are some linting issues that are false positives. Some linting rules are a bit strict, and we will merge in the meantime and tackle in a different task.

Next steps:

• @adamblanchard to merge this PR in it's current state
• @adamblanchard take "what projects should we run" discussion starting at tomorrow's mentor meeting
• @adamblanchard raise task for linting improvements
• @adamblanchard add "session lead guide" improvements to mentor guide task
• @bhas raise task for backend specialisation module with as much context as possible for the next people to help
• @bhas raise task for improving learning goals/scope for week 4