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-2 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.

gitGraph
    commit id: "start"
    branch feature/week-2-exercises
    commit id: "skeleton page code"
    commit id: "Fonts and colours"
    commit id: "mobile layout"
    commit id: "lighthouse audit revisions mobile"
    commit id: "desktop layout"
    commit id: "lighthouse audit revisions desktop"
    checkout main
    merge feature/week-2-exercises

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

Coursework content

Invite one fellow trainee from the class you have worked with this week for a feedback session. Arrange the call so you can give and receive feedback and get more insight into how you are progressing with your learning.

Read about the different frameworks of feedback on this page, so you can think about how you will structure the feedback to be given.

Estimated time in hours

1

What is the purpose of this assignment?

To provide and receive constructive feedback on your and your peers’ behaviours in the last class.

How to submit

1. Prepare the feedback for your peer. You must have at least 1 positive and 1 to be developed example.
2. When you receive the feedback, please remember your active listening techniques.
3. Write a 250 words essay reflecting on your strengths and development areas as a result of their feedback and what is one action for each you will take.

Anything else?

Remember to update your Development Plan, if applicable.

Coursework content

Read this article about respectful and constructive code review.
And this article about how to handle code review.

Estimated time in hours

1

What is the purpose of this assignment?

Reflect on the relationship between code review and feedback. Think about these questions:

• How are code review and feedback related?
• How are they different?
• How would you explain code review to a new applicant for this course?
• How would explain feedback to this same person?

How to submit

1. Write a text that you would send to a new applicant of this course explaining:

   • The importance of code review and an example of when you used it and what difference it made
   • The importance of feedback and an example of when you used it and what difference it made
   • Any tip you think you would have liked to have received when you were starting this course

2. Post the link to your text as a comment on this issue (Make sure your document is open to be viewed and commented on)

3. Share your document on the thread of the post on Slack for this coursework. If you cannot find the post, you might be the first one, so create it.

4. Read at least 2 texts of fellow trainees and give your feedback on them. Focus on the ones that haven’t had feedback yet. Don’t forget to use an emoji so other people can see this content has already had a review.

Anything else?

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 others, 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.

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 prep material

https://curriculum.codeyourfuture.io/js1/sprints/2/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/