Link to the prep material

https://curriculum.codeyourfuture.io/js1/sprints/3/prep/

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

3

How to get help

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

Link to the coursework

https://www.codewars.com/users/CodeYourFuture/authored_collections

Why are we doing this?

Every week you need to complete at least three kata. Spend at least 20 minutes, three times a week, on your kata workout.

Find the Collection for this week on the CodeYourFuture account.

Take some time to check your levels. Before you are accepted on to a Final Project on the developer track, you need to complete the Final Projects collection and reach a Level 5 kyu in Codewars. Are you on track to reach this standard? Have you run a study group to work on kata? Have you reached out on the #cyf-codewars channel? What is your plan to meet this goal?

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

1

How to get help

• Join the #cyf-codewars Slack channel
• Read the CYF Codewars docs
• Read Codewars advice from CYFers
• Read Codewars advice from mentors

Remember, after 20 minutes, take a break.

How to submit

Your codewars progress is tracked automatically and is available on the public API. You don’t need to submit it.

How to review

Once you have completed your kata, look at the other solutions in the solutions view. Consider how many different approaches there are.

Link to the coursework

https://syllabus.codeyourfuture.io/guides/intro-to-tests

Why are we doing this?

Testing is an essential tool as a developer. We use tests as a means of ensuring how code behaves in a specific way; but they’re also incredibly useful for breaking down problems.

Maximum time in hours

1

How to get help

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

Link to the coursework

https://syllabus.codeyourfuture.io/git/terminal/lesson

Why are we doing this?

Most developers spend a lot of time using something called the terminal. This week, you are going to complete your course to learn about the terminal - it has its own homework page here for you to work from.

Maximum time in hours

2

How to get help

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

How to submit

Fork the repo to your own GitHub account
Make regular small commits with clear messages
When you are ready, open a Pull Request to the CYF repo
Make sure you fill in the PR template provided

Why are we doing this?

Learning to read and review other people’s code is a key skill for a developer. When you join a new team, you will usually also join an existing codebase, and you will need to be able to read it. If you’ve never looked at code written by other people, you will find this really challenging (it’s already hard!).

1. Ask for a code review from a colleague on your Module-JS1 coursework
2. Complete a code review for a colleague on their Module-JS1 coursework.

Maximum time in hours

1

How to submit

Link the PR you reviewed on your copy of this ticket. Paste the url in comment on your ticket.

Coursework content

Invite one person (fellow trainee or a volunteer) from the class you have worked with this week and arrange a call. Ask for their feedback to help you get more insight into how you are progressing with your learning.

Write a 250-word essay reflecting on your strengths and development areas as a result of their feedback.

Estimated time in hours

2

What is the purpose of this assignment?

To provide and receive constructive feedback.

How to submit

Share the link to the Google doc of your reflections on your ticket. Make sure the document is open to view and comment by anyone.

Coursework content

Everyone experiences rejection. Learning from past examples helps us to deal with the possible future instances. Think of some situations where you felt rejected. Perhaps you didn’t get on a sports team or didn’t get offered a job. Write a 250-word text about this personal experience. Try to answer the following questions:

• What did you learn as a result of this rejection?
• Did the experience teach you more about yourself?
• What positive things came out of the rejection (perhaps not immediately, but later)?
• How would you recommend other people to behave in that situation?

Estimated time in hours

1

What is the purpose of this assignment?

This assignment will help you to reflect on personal rejection instances and make you realise how you can benefit from them.

How to submit

Share the link to the Google doc of your reflections on your ticket. Make sure the document is open to view and comment by anyone.

Anything else?

n/a

Link to the coursework

The exercises and challenges for this week are located in the module repo: https://github.com/CodeYourFuture/Module-JS1 inside the week-3 directory. Ensure you read the readme.md first to figure out what to do.

Why are we doing this?

These challenges are designed to develop your problem-solving skills.

Maximum time in hours

6

How to get help

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

How to submit

1. Fork to your Github account.
2. Make a branch for this project.
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.

There are several projects in this repo. Make a new branch for each project.

Link to the coursework

https://github.com/CodeYourFuture/Portfolio/tree/Module-JS-1

Why are we doing this?

You will slowly iterate on your Portfolio over the whole course of CYF. You need to build your portfolio so you can use it to get into The Launch module, and then later use it to apply for jobs.

This module we’re exploring a branch to branch pattern in Git. Read the readme carefully and follow the instructions.

Bring your portfolio to class to get help and feedback from your community. Writing a great case study will help you understand how to explain and present your work to recruiters and employers. Your first case study doesn’t have to be great, don’t panic!

Explore and revise

• Review a colleague’s case study
• Do your review on their PR on the Portfolio repo, using the GitHub Code Review interface

Maximum time in hours

1

How to get help

Bring your portfolio to class to get help and feedback from your community. Taking the reviewer role will help you put yourself in the shoes of a recruiter or employer (who does not know you) reading a portfolio. Understanding this perspective will make your own portfolio better. What context is missing from the case study you are reading?

How to submit

Use the GitHub Code review interface on https://github.com/CodeYourFuture/Portfolio/pulls