πŸ“… backlog

Module-JS3 πŸ”—

[TECH ED] Review Solutions for Last Weeks Coursework πŸ”— Clone

You can find the solutions to the exercises for this project in the solutions branch of this repo.

Why are we doing this?

You must check your work against our solutions. It is important to continually evaluate your work and identify any areas of weakness in your understanding.

Maximum time in hours (Tech has max 16 per week total)

0.5

How to get help

https://curriculum.codeyourfuture.io/guides/asking-questions

How to submit

n/a

  • 🎯 Topic Code Review
  • πŸ• Priority Mandatory
  • πŸ‚ Size Medium
  • πŸ“… JS3
  • πŸ“… Week 3
[TECH ED] Programmer Humour πŸ”— Clone

https://github.com/CodeYourFuture/Module-JS3/tree/main/programmer-humour

Why are we doing this?

We’re making a very tiny application, the smallest one you can think of, that fetches from an API and shows something on a page. You should do this many times. Make ten more of these if you finish this early. Make it as simple as possible.

Remember: always do the simplest thing that can possibly work.

Maximum time in hours (Tech has max 16 per week total)

1

How to get help

Share your blockers in your class channel. Use the opportunity to refine your skill in Asking Questions like a developer.

How to submit

  1. Fork to your Github account.
  2. Make a branch for this project called feature/xkcd
  3. Make regular small commits in this branch with clear messages.
  4. When you are ready, open a PR to the CYF repo, following the instructions in the PR template.
gitGraph commit id: "start" branch feature/xkcd commit id: "stub-files" commit id: "fetch-from-xkcd" commit id: "template-layout" commit id: "lighthouse-audit-revisions" checkout main merge feature/xkcd

There are several projects in this repo. Make a new branch for each project. This might feel challenging at first, so this is a good problem to bring to class to work on in groups with mentors.

Don’t make one giant PR with all your work in for the module. Make a separate PR for each assignment.

How to review

  1. Complete your PR template
  2. Ask for review from a classmate or mentor
  3. Make changes based on their feedback
  4. Review and refactor again once the coursework solutions are released.
  • 🎯 Topic Programming Fundamentals
  • 🎯 Topic Requirements
  • πŸ• Priority Mandatory
  • πŸ“… JS3
  • πŸ“… Week 3
[TECH ED] TV Show Project - Part 3/4 πŸ”— Clone

https://github.com/CodeYourFuture/JS3-Module-Project

Your goal this week is to complete level 400.

Reminder: You will need to be paired up with someone for this project.

That means:

  • Finishing anything from weeks 1 and 2 which isn’t finished
  • Achieving level 300 yourself in your own repository
  • Achieving level 400 yourself in someone else’s repository
  • Discussing your different approaches with your pair, and making sure you’re both happy with each other’s code

Why are we doing this?

After learning new skills and concepts, it’s important to practice using this knowledge to check if you’ve understood everything properly. The tv show project will provide you with an opportunity to use your knowledge from JS1 and JS2 to create a website from scratch.

Maximum time in hours (Tech has max 16 per week total)

8

How to get help

https://syllabus.codeyourfuture.io/guides/asking-questions

How to submit

Remember to follow the instructions here: https://github.com/CodeYourFuture/JS3-Module-Project/blob/main/levels/level-0.md

  • 🎯 Topic Delivery
  • 🎯 Topic Functional Programming
  • 🎯 Topic Iteration
  • 🎯 Topic Problem-Solving
  • 🎯 Topic Requirements
  • πŸ• Priority Mandatory
  • πŸ‹ Size X-Large
  • πŸ“… JS3
  • πŸ“… Week 3
[TECH ED] Mid-Course Feedback πŸ”— Clone

https://docs.google.com/forms/d/e/1FAIpQLSfrAtvR5HonJZiqlPXocAz7d1l-Kn57X5xp3oH_NmVUL9xTQQ/viewform

Why are we doing this?

We’re now over half way through the Full Stack Course!

Your feedback is really important to us. We use your feedback to improve the
course for all of the hundreds of trainees across CodeYourFuture now and
in the future.
This feedback is anonymous meaning we won’t have an idea who you are after you submit.

We really appreciate you being honest since this allows us to improve faster.

Maximum time in hours (Tech has max 16 per week total)

0.5

How to get help

https://syllabus.codeyourfuture.io/guides/asking-questions

How to submit

Submit your feedback using this form https://docs.google.com/forms/d/e/1FAIpQLSfrAtvR5HonJZiqlPXocAz7d1l-Kn57X5xp3oH_NmVUL9xTQQ/viewform

  • 🎯 Topic Communication
  • 🏝️ Priority Stretch
  • πŸ¦” Size Tiny
  • πŸ“… JS3
  • πŸ“… Week 3
[TECH ED] JavaScript Challenges πŸ”— Clone

https://github.com/CodeYourFuture/JavaScript-Core-3-Challenges

Why are we doing this?

If you’re completing the coursework with time to spare, you’re not getting the most you can out of your time here. Stretch yourself with extra challenges.

No time given as this is a stretch goal.

Maximum time in hours (Tech has max 16 per week total)

0

How to get help

Share your blockers in your class channel.
https://syllabus.codeyourfuture.io/guides/asking-questions

How to submit

  1. Fork to your Github account.
  2. When you are ready, open a PR to a CYF repo.

How to review

  1. Complete your PR template
  2. Ask for review from a classmate or mentor
  3. Make changes based on their feedback
  4. Review and refactor again once the coursework solutions are released.
  • 🎯 Topic Problem-Solving
  • 🎯 Topic Programming Fundamentals
  • 🏝️ Priority Stretch
  • πŸ‚ Size Medium
  • πŸ“… JS3
  • πŸ“… Week 3
[TECH ED] Prepare for live session πŸ”— Clone

tbc

Why are we doing this?

It is essential to start learning new concepts and ideas before Saturday’s session. During the week, we expect you to get stuck and form questions about the new content so you can address misconceptions during Saturday’s session. The prep work here will introduce you to the new concepts for the week.

Maximum time in hours (Tech has max 16 per week total)

3

How to get help

Share your blockers in your class channel
https://curriculum.codeyourfuture.io/guides/asking-questions

How to submit

n/a

  • πŸ• Priority Mandatory
  • πŸ‚ Size Medium
  • πŸ“… JS3
  • :brain: Prep work
  • πŸ“… Week 3
[TECH ED] Array Destructuring πŸ”— Clone

https://github.com/CodeYourFuture/Module-JS3/tree/main/array-destructuring

Why are we doing this?

Array destructuring is very useful and used a lot in React.

https://www.freecodecamp.org/news/array-destructuring-in-es6-30e398f21d10/

Maximum time in hours (Tech has max 16 per week total)

1

How to submit

  1. Fork to your Github account.
  2. Make a branch for this project called feature/destructuring
  3. Make regular small commits in this branch with clear messages.
  4. When you are ready, open a PR to the CYF repo, following the instructions in the PR template.
gitGraph commit id: "start" branch feature/destructuring commit id: "ex-1-update-argument" commit id: "ex-2-teachers-pet" commit id: "ex-3-print-receipt" checkout main merge feature/destructuring

There are several projects in this repo. Make a new branch for each project. This might feel challenging at first, so this is a good problem to bring to class to work on in groups with mentors.

Don’t make one giant PR with all your work in for the module. Make a separate PR for each assignment.

How to review

  1. Complete your PR template
  2. Ask for review from a classmate or mentor
  3. Make changes based on their feedback
  4. Review and refactor again once the coursework solutions are released.
  • 🎯 Topic Programming Fundamentals
  • 🎯 Topic Requirements
  • πŸ• Priority Mandatory
  • πŸ‡ Size Small
  • πŸ“… JS3
  • πŸ“… Week 3