πŸ“… backlog

Module-JS2 πŸ”—

[TECH ED] Prepare for the live session πŸ”— Clone

Use the prep view from the CYF curriculum to prepare for this week.

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

4

How to get help

Share your blockers in your class channel. Remember to Ask Your Questions like a developer.

How to submit

Write down at least one specific technical question to bring to the group.

How to review

Come to class with your questions

  • :brain: Prep work
  • 🎯 Topic Programming Fundamentals
  • πŸ• Priority Mandatory
  • πŸ‚ Size Medium
  • πŸ“… Week 2
[TECH ED] Codewars πŸ”— Clone

From Module-JS2 created by SallyMcGrath: CodeYourFuture/Module-JS2#5

From Module-JS3 created by Dedekind561: CodeYourFuture/Module-JS3#18

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

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.

  • 🎯 Topic Code Review
  • 🎯 Topic Problem-Solving
  • 🎯 Topic Programming Fundamentals
  • 🎯 Topic Requirements
  • 🎯 Topic Time Management
  • πŸ• Priority Mandatory
  • πŸ“… JS2
  • πŸ“… Week 2
[TECH ED] Portfolio πŸ”— Clone

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

Why are we doing this?

At Code Your Future, we expect everyone to graduate with a unique professional portfolio. You will begin building this portfolio as soon as you begin our Software Development Course. At first, your portfolio will be a simple HTML/CSS page deployed to Github Pages or Netlify. This is your MVP.

Every module, you will iterate on your portfolio, adding a new project and improving your design and presentation. By the time you apply to Final Projects, your portfolio will help you show you are ready to be accepted on to a development team. The process of developing the portfolio, through specified git workflows, through small scoped feature development, and through case study and written presentation, will all help you succeed in Final Projects.

Maximum time in hours

3

How to get help

Share your blockers in #cyf-portfolios.

Use the opportunity to refine your skill in Asking Questions like a developer.

How to submit

  1. Fork to your Github account.
  2. Check out the branch for the module you are on.
  3. Make regular small commits with clear messages.
  4. When you are ready, open a PR to the CYF repo, to the matching branch, following the instructions in the 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 next time

Anything else?

To get a job in tech you need a minimum set of tools that you need to acquire or build over the course of this year. You need:

  1. a well written CV
  2. a solid portfolio of junior level work that makes you memorable to a recruiter
  3. to be able to plan, build, and ship a working product in an Agile team
  4. to be able to score reasonably well in a timed technical test
  5. to be able to do an interview in fluent English

Keep this in mind.

  • 🎯 Topic Iteration
  • πŸ• Priority Mandatory
  • πŸ‡ Size Small
  • πŸ“… JS2
  • πŸ“… Week 2
[TECH ED] Review solutions for last week's coursework πŸ”— Clone

Why are we doing this?

You’ll need to regularly check solutions to evaluate your understanding.
However, you must attempt the activities first before you use the solutions.
You can find the solutions for all the assignments in this repo’s solutions branch.

Maximum time in hours

0.5

  • πŸ• Priority Mandatory
  • πŸ“… JS2
  • πŸ“… Week 2
[TECH ED] Sign up for render πŸ”— Clone

https://render.com

Why are we doing this?

You’ll need to sign up to render so you can host some of the applications you build on the course.

Maximum time in hours

0.05

How to get help

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

  • πŸ• Priority Mandatory
  • πŸ‚ Size Medium
  • πŸ“… JS2
  • πŸ“… Week 2
[TECH ED] Complete week 2 exercises πŸ”— Clone

The exercises and challenges for this week are located in the module repo: https://github.com/CodeYourFuture/Module-JS2 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.

  • πŸ• Priority Mandatory
  • πŸ‚ Size Medium
  • πŸ”‘ Priority Key
  • πŸ“… JS2
  • πŸ“… Week 2
[PD] Review a fellow trainee's CV πŸ”— Clone

Coursework content

Read one of the CVs that hasn’t been reviewed yet on the #cyf-profile-review https://codeyourfuture.slack.com/archives/C7MBLPR6F and give feedback on it.

Make sure you react to the post so people know you are on it (i.e. two eyes when looking, done when finished), and add the feedback as comments directly on the file or the thread.

When reading the CV, use your interviewer hat. Would you call this person for an interview? In ether answer, yes or no, make sure you give them a clear example as to why you think this way.

Estimated time in hours

1

What is the purpose of this assignment?

  • See the variety of content people write in their CVs.
  • Judge a CV as an external reader. Then you can know what to write better.
  • Give constructive feedback to your peers.

How to submit

  • Add the link to the CV doc you reviewed as a comment on this issue.
  • Add a screenshot of you reacting to the message on the #cyf-profile-review Slack channel.

Anything else?

  • πŸ‡ Size Small
  • πŸ”‘ Priority Key
  • πŸ“… Week 2