🏷️ backlog

Module-JS1 πŸ”—

[TECH ED] Check module success criteria πŸ”— Clone

https://curriculum.codeyourfuture.io/js1/success/

Why are we doing this?

πŸ”‘ The most important thing is that you are secure in your understanding.

At the end of the course, we will expect you to build novel applications using your understanding. If you cannot build things, we cannot put you forward for jobs. It is in your personal interest to make sure you have properly understood this module.

To progress to the next module you need to meet the success criteria for this module. How will you as a cohort meet the module success criteria? Discuss it in your class channel and make a plan together.

πŸ§‘πŸΏβ€πŸŽ€ good strategies

  • asking volunteers to review your code
  • helping each other with coursework blockers
  • arranging midweek study sessions
  • using Saturday time to review code and cohort tracker

πŸ™…πŸΏ bad strategies

  • opening empty PRs
  • copying and pasting
  • breaking the Trainee Agreement
  • mistaking the measure for the target

Maximum time in hours

.5

How to get help

Discuss with your cohort. Support each other.

How to submit

In week 4 of your module you will need a representative to report to the organisation. Here’s your template, fill in your details and delete as appropriate:

πŸ“ˆ Cohort Progress Report from @cohort-name to @programme-team

  • criterion
  • criterion
  • criterion
  • criterion

βœ… We are progressing to the next module.
β›” We are taking a consolidation week to meet our targets.

  • 🎯 Topic Code Review
  • 🎯 Topic Communication
  • 🎯 Topic Delivery
  • 🎯 Topic Requirements
  • 🎯 Topic Teamwork
  • 🎯 Topic Testing
  • 🎯 Topic Time Management
  • πŸ• Priority Mandatory
  • πŸ¦” Size Tiny
  • πŸ“… Week 1
  • πŸ“… Week 4
[TECH ED] Portfolio: branch to branch πŸ”— Clone

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, but it’s important to start one.

Explore and revise

  • If you want help or to break the “blank page” fear for writing your case study, try getting a first draft from Claude and then revise the text to express your own ideas.
  • It’s not a good idea to let AI write everything for you. Why? (One reason is you cannot “stand out” by copy-pasting the same bland verbiage everyone else is copy-pasting.) What other drawbacks are there? Discuss in class.
  • You’ve written quite a lot of reflections and technical writing by now, just by doing pull requests. Can you take some inspiration from that work?

Maximum time in hours

1

How to get help

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, but it’s important to start one.

How to submit

Follow the submission instructions in Portfolio.

  • πŸ• Priority Mandatory
  • πŸ‡ Size Small
  • πŸ“… JS1
  • πŸ“… Week 1
[PD] Review your development plan πŸ”— Clone

Coursework content

Using the Build Your Life plan and your first version of your Career Development plan, we want you to continuously think about the goals you want to achieve: short/medium/long-term. These should still be linked to the areas you want to develop.

Remember: 2-3 areas are enough to change in such a short time, so it’s better to focus on a few, get them nailed, and then choose another area.

Ensure you are not only thinking of technical knowledge you want to acquire but especially skills and processes that will help you become a developer.

Examples of goals

  • Short term: Practicing coding = Code 1 hour a day on weekdays
  • Medium-term: Enhance my written English = Trying to correct by myself the errors that the automated grammar tool is showing in my text
  • Long term: Get a job in tech = Send 1 tailored CV per day when I have graduated from Code Your Future

Estimated time in hours

0.5

What is the purpose of this assignment?

Define where you want to be in the short, medium and long term. This helps give you perspective and clarity of where your direction is and if you are doing the right things to get there.

How to submit

  • Share your development plan link as a comment, open to anyone to comment
  • Write a paragraph, as a comment on this issue, about what you have learned/changed
  • πŸ• Priority Mandatory
  • πŸ‡ Size Small
  • πŸ“… JS1
  • Week 1
[PD] What do you think? πŸ”— Clone

Coursework content

Use critical thinking skills to answer a client’s request on a web page you developed.

Estimated time in hours

1

What is the purpose of this assignment?

A client requested the navigation bar at the bottom of their web page. Research what best practice is and why this would be a good, a bad or a neutral idea.

These are the tips to help you write it:

  • Provide appropriate and sufficient arguments and examples
  • Research arguments against and for the statement before coming to your conclusions.
  • Choose terms that are precise, appropriate, and persuasive
  • Make clear the transitions from one thought to another to ensure the overall logic of the presentation

How to submit

  • Create a text with at least 250 words.
  • Make sure your text is reviewed by a grammar tool. It should have at most 3 mistakes.
  • Add the link to the Google doc to comment on this issue. Make sure it is open for anyone to comment.
  • πŸ• Priority Mandatory
  • πŸ‡ Size Small
  • πŸ“… JS1
  • Week 1
[PD] Regular Study Sessions πŸ”— Clone

Coursework content

Organise a study session with your group. Use this session to work through your Personal Development coursework as a team.

  1. Set up the invite on Google Calendar
  2. Define the agenda (what aspects of the PD lessons or coursework you will be covering)
  3. Have the session using either Google Meet or Slack.
    This must be done before the next class.

Estimated time in hours

0.5

What is the purpose of this assignment?

The aim is to have one study session with a group at least once every module, but you can decide as a group how often you want to have it recur.
Once you’ve decided on the periodicity after your first session, edit your calendar invite to a recurring meeting.

How to submit

  • Add a screenshot of the calendar invite as a comment to this ticket
  • Add a comment summarising how your first session went and what you discussed

Anything else?

Use this video to learn how to create a calendar invite.

  • πŸ‡ Size Small
  • πŸ”‘ Priority Key
  • πŸ“… JS1
  • Week 1
[PD] Writing an email for an internship πŸ”— Clone

Coursework content

Draft an email to apply for an internship at a fictional company called Vonda. Make sure to include the five things below:

  1. Why you want to become a software developer
  2. Your background and your past
  3. What you are doing at the moment
  4. Where you see yourself in the future
  5. Why Vonda should give you the opportunity to do an internship

The email should be formatted in a way that is ready to be sent. Make sure you include a subject title and pay attention to the formatting (font type and size, alignment etc).

Estimated time in hours

1

What is the purpose of this assignment?

This assignment aims to improve your writing skills.

How to submit

Share the link to the Google doc on the ticket on your coursework board.

  • 🎯 Topic Communication
  • πŸ• Priority Mandatory
  • πŸ‡ Size Small
  • πŸ“… JS1
  • Week 1
[TECH ED] Code review πŸ”— Clone

To prepare for code reviewing, read this article to learn how to write good code reviews:
Google code review best practices

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.

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

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

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

  • πŸ• Priority Mandatory
  • πŸ‚ Size Medium
  • πŸ”‘ Priority Key
  • πŸ“… JS1
  • Week 1
[TECH ED] Prepare for live session πŸ”— Clone

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

  • :brain: Prep work
  • πŸ• Priority Mandatory
  • πŸ‚ Size Medium
  • πŸ“… JS1
  • πŸ“… Week 1