Link to the coursework

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

Why are we doing this?

The CYF curriculum is an open source project. Like all software, it is continually revised and improved in iterations.

Help improve the curriculum by giving quick emoji feedback on any assignment.

Feedback on this assignment by pressing the emoji reaction button on the top comment.

Emoji Key

👍 = Useful
👎 = Not useful

🚀 = Way too much time given
😕 = Not enough time given

You are invited to give feedback on any assignment in this way. Do this on the CYF issue, not your copy, so CYF can track it using the GitHub reactions API.

Maximum time in hours

.05

How to submit

Click the emoji button on the first post on any coursework assignment.

From Module-React created by SallyMcGrath: CodeYourFuture/Module-React#34

Link to the coursework

https://react.dev/learn

Why are we doing this?

The React documentation is brilliant. It’s actually weirdly similar to our original course, especially https://react.dev/learn/thinking-in-react so we now link to it heavily instead of maintaining our own version.

We highly recommend you follow the whole thing, but we will point to vital pieces throughout the prep material.

Link to the coursework

https://overthewire.org/wargames/bandit/

Why are we doing this?

Basic Linux skills are essential for roles in Cloud, DevOps, Cyber, and SRE. Junior Cloud and DevOps roles are growing in the industry; React and fullstack junior roles are becoming more scarce. So it’s a good idea to practice Linux skills to make yourself more employable. At the basic level this means using a computer from the command line instead of a GUI. You will learn to use commands to move from folder to folder, to open and edit files, and to get info like the size of a file or its location. At CYF we build this skill by playing a game called The Bandit.

Your goal is to get to Level 20 by the end of the Databases module. You can do this by completing one level a week from JS2 onwards. You can do one level a week!

Try to get to at least level 7 this week.

Maximum time in hours

1

How to get help

Work through the puzzles together in #cyf-over-the-wire

Don’t share solutions in this channel, or you steal from others the opportunity of learning.

How to submit

There is no submission step. However, to apply for some roles and some courses (like CYF+ ) you must demonstrate these skills, so it would be a good idea to learn them.

Anything else?

Here’s a ChatGPT prompt you can use to get the best, most helpful learning experience:

Please act as a friendly, warm, straightforward technical mentor. You are an experienced Site Reliability Engineer who uses the terminal regularly and understands all shell commands in bash. You can explain clearly, using English mostly at CEFR B2 level, how to execute shell commands and how to navigate Linux file systems. We will be playing The Bandit, Over the Wire, shell game together. I don’t want you to give me all the answers. I want you to walk me towards the answer, helping me to find out and learn Linux commands, explaining clearly what is happening as we go. Please answer my questions carefully and do not offer code solutions, just explain in English the approach I should take and then review the commands I suggest to you. Say okee dokee if you understand.

And remember: every time ChatGPT offers code you must write “Is this valid” before you continue. ChatGPT makes up invalid code all the time.

Coursework content

Review your Teamwork Project team members’ LinkedIn profiles and provide constructive feedback.

Consider the information added to their profile, their photos, their transferrable skills, if you can spot any grammar or spelling mistakes, what they’ve posted recently and how they are interacting on it.

When giving feedback, remember that this is an important moment to give your peer a present.

• Describe what you can see/evaluate on their LinkedIn page
• Explain why you think it is good with a clear example
• Explain the impact of it, either positive or negative
• Have a conversation about it

Estimated time in hours (PD has max 4 per week total)

1

What is the purpose of this assignment?

Code Your Future believes in collective intelligence, which focuses on openness and sharing. This assignment will allow you to support your peers and learn from each other.

How to submit

• Share the screenshot of your feedback on this issue.
• If you provided feedback in person, write it down and add it as a comment on this issue.

Link to the coursework

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.

Link to the coursework

https://github.com/matthiasn/talk-transcripts/blob/master/Hickey_Rich/HammockDrivenDev.md

Why are we doing this?

Here’s the video of this talk https://www.youtube.com/watch?v=f84n5oFoZBc

All the way through this course, we are trying to teach you one Big Idea: programming is problem solving.

We never want you to have no problems on this course! We want you to find problems and then solve them. The more problems you have, the better you are doing.

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

0

How to submit

Share a solution in your class channel – write up your troubleshooting process and the solution you found for any problem.

Link to the coursework

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

Link to the coursework

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.

Link to the coursework

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

Link to the coursework

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.