Task code

CYF-1013 - make sure to include this in your PR title or description.

Link to the coursework

https://curriculum.codeyourfuture.io/itp/onboarding/success/

Why are we doing this?

🔑 The most important thing is that you are secure in your understanding.

To enroll as a trainee and progress to the next module you need to meet the success criteria for this module. How will you meet the module success criteria? You have lots of people to help you. Discuss it in your Slack channel and make a plan together. Help each other.

🧑🏿‍🎤 good strategies

• asking volunteers to review your code and responding to that review
• helping each other with coursework blockers
• arranging midweek study sessions
• using Saturday time to review code and the dashboard steps

🙅🏿 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

It’s just like ITD. Submit your step on the course platform for volunteer review.

Task code

CYF-1010 - make sure to include this in your PR title or description.

Presenting information is really important. You need to start practicing giving demos.

During this module, you must attend at least one demo session. We highly recommend you give at least one demo in a demo session, as well. We recommend you come to more, and give more. Your demo can be on anything you want. You can attend this demo session in any sprint. After this module, you will be required to give at least one demo per module.

There are demo sessions every Tuesday evening and Friday morning. They are advertised on Slack.

Aim for a 5 minute demo. But your demo must be at least 1 minute and at most 10 minutes long. Check out our guide about presenting.

You will need to attach a screenshot when submitting your Step for this Module. Make sure to take a screenshot of you on the call, showing that one of the following members of the CYF team was on your call:

• Daniel Wagner-Hall
• Karen Klein
• Colin Farquhar
• Poonam Rajput
• Léon McGregor
• Peter Mudra
• Liam Greenfield

If you are not available during any of the demo times, please message on Slack to arrange an alternate time.

Task code

CYF-1004 - make sure to include this in your PR title or description.

Link to the coursework

https://github.com/CodeYourFuture/Module-Onboarding/tree/main/Form-Controls

Why are we doing this?

To build a successful web application, you must understand the requirements of the user and be able to translate them into a working program. In this challenge, you are given a summary of what the application should do and a series of acceptance criteria that you can use to measure your work against the expectations of the task.

You will be required to make decisions about how best to implement the solution and explore your own code with the browser’s Dev Tools. You will likely encounter blockers - remember to follow the guidance below on asking for help.

Maximum time in hours

4

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

Remember that you should switch to the main branch before creating a new branch.

1. Fork to your Github account.
2. Switch to the main branch
3. Make a branch for this project called feature/form-controls.
4. Make regular small commits in this branch with clear messages.
5. When you are ready, open a PR to the CYF repo, following the instructions in the PR template. Read this guide, which explains more about how pull requests work at Code Your Future. 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.

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 week

💡Tip

If you’re on a library computer, fork this Codepen to see live updates while you work. You might need to use Edge instead of Chrome to access DevTools.

Task code

CYF-1007 - make sure to include this in your PR title or description.

Coursework content

You will have made a plan in your head about how to take an intensive training like ours. As an adult you know you have to find time to work, look after a family, solve legal issues, get healthy, commute, etc.

Like all speculations, this plan is usually not accurate. CYF grads report they were quite wrong about the actual time and energy they needed to do the programme.

Even a good plan for the course is rarely accurate. If you have planned to return to your everyday life after the course until you find a job, then this plan will fail.

We know that successful CYF graduates begin their lives as tech professionals when they begin our course, and do not stop.

If you want to be a developer, you have to act like a developer daily. Becoming a developer is not about getting a job. It’s about playing a role in software development weekly, daily, if possible. If you want to be a DevOps Engineer, a Product Owner, a Scrum Master, an IT Professional, a Business Analyst, a Functional Consultant, a Data Engineer, or any of the other roles in tech, you need to start as you mean to go on.

Becoming a professional in this field requires constant improvement and practice. It doesn’t stop after your training. This training is just the beginning. Whatever plan you make, you must project it for the rest of your life. Tech professionals are continuous, life long, self-learners.

Estimated time in hours

1

What is the purpose of this assignment?

If your goal is to move into tech, you must commit to it. And that doesn’t mean only committing during the training. It means committing until you find a job in tech, which doesn’t have a fixed deadline.

This exercise will help you identify your time. It will help you plan your time. It will help you to always have enough time to be healthy, happy and a developer.

Let’s identify your weekly activities and availability,

• Make a copy of this spreadsheet onto your drive

• Fill in the number of hours for every weekly activity. Consider an average week so you don’t have to update this week by week. Your summary will describe how your week divides between these activities. Don’t write details about these activities, just write how much time you spend on each. Make sure you include the time you spend in each. If your week changes a lot, average across four sample weeks in the last six months.

• Add a row if you have an activity not included in these items.

How to submit

Feel free to share this with anyone you feel comfortable to do so.

It’s good to get review. Everyone at CYF has different time constraints. Share your insights and help each other. And you can get tips for yourself at the same time.