Link to the coursework

https://curriculum.codeyourfuture.io/

Why are we doing this?

The curriculum is our shared plan. It’s how you find out what to do when. You need to be able to use the curriculum, and help volunteers (who may have just arrived that day!) understand how to use it too.

Make a default set of tabs in your work browser:

1. Your Coursework Planner Project (to organise your backlog - look at the example planners for inspiration)
2. The curriculum
3. MDN
4. Your Google Calendar (to easily record your study sessions, classes, events, and meetings)

Book a time in your calendar to start your prep

Book a recurring time in your calendar every Wednesday (at a time you can actually do) to begin your prep work for the week. Now make sure you know where the prep view is! The prep view on the curriculum has information you will need to participate in class and complete your coursework. The work on the prep view is the main new content each week, and includes exercises, videos, tutorials, and more.

🔑 You must prioritise doing the prep work.

Many trainees at CYF like to organise study sessions to go through the prep together. This is great for motivation and keeping yourself on track. You are welcome to come to Gathertown to work on prep.

Maximum time in hours

.15

Coursework content

The typical CodeYourFuture trainee (you) will have made a plan in their head on how to take an intensive training like ours and still find time to work, look after a family, and children, solve legal issues, get healthy, commute, etc. This plan is typically inaccurate to the actual time and energy levels needed to dedicate enough time to each one of the activities, particularly studying.

This plan will typically last until you graduate, at which point you will have planned to return to your everyday life until you find a job. We know that successful CYF graduates begin their lives as developers when they begin our course and continue throughout life.

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.

Becoming a professional in this field requires constant improvement and practice. It doesn’t stop after your training. This training will be just the beginning. Whatever plan you make, you must project it for the rest of your life.

Estimated time in hours

0.75

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, but committing until you find a job in tech - which doesn’t have a fixed deadline.

This exercise will help you identify your time to plan it accordingly, 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 give you a detailed description of how your week passes between these activities. You do not need to provide details about these activities, just how much time you dedicate to each. Make sure you include the time you spend in each. If your week changes a lot, describe a week that summarises the hours you dedicate to each activity.
• 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 have a review to ensure you have everything and are being optimistic/pessimistic about your time and tasks.

Link to the coursework

https://github.com/CodeYourFuture/GitHomeworkTest

Why are we doing this?

Follow the instructions in this repository to submit a description about yourself.

This is how you’ll be submitting your coursework for the rest of this course, so if you hit a problem, you must speak up.

Maximum time in hours

1

How to get help

Ask for help with your blocker in the class channel.

How to submit

Follow the instructions on the readme to work out how to submit this piece of coursework.

Link to the coursework

https://github.com/CodeYourFuture/GitHomeworkFixErrors

Why are we doing this?

This issue will allow you to practice the Git workflow you’ll need for submitting your coursework.

Maximum time in hours

1

How to get help

Ask for help with your blocker in the class channel.

How to submit

Follow the instructions on the repository’s readme.md to submit this piece of coursework.

Coursework content

Organise a study session with the pair you were assigned to during class - check out the Google Sheet. Think about how you manage your time and which tools you use (add some examples and suggestions from our side). If you still need to start using them, research some and bring them to this meeting.

Estimated time in hours

2

What is the purpose of this assignment?

• Understand how you and your pair organise your time
• Identify at least 2 time management tools each
• With your pair, write a short paragraph about your findings
• Share your findings in the “Time Management Tools” thread on your cohort Slack Channel. Search for it on the channel. If the thread is not yet available, you can create it
• Read your peers text and react to it the the appropriate emoji

How to submit

• Add the link to your post on Slack on this coursework
• Add a screenshot of your post on this coursework

Coursework content

Research a developer’s daily activities and behaviours. What will you expect to know or do when you get your first job? Activities are specific actions, tasks, or operations to accomplish a particular goal or objective.

Example 1: A marketing analyst must conduct market research and data analysis to identify consumer trends Behaviour is the observable actions, reactions, or conduct of someone.
Example 2: A marketing analyst must be able to effectively communicate complex data clearly and understandably to stakeholders.

Estimated time in hours

1

What is the purpose of this assignment?

• Research a developer’s daily activities and behaviours
• Write between 50 to 100 words on a Google Docs file
• Check the grammar using an available too, for example, Grammarly
• Share the file with your cohort on the “Developers daily activities” thread. If the thread doesn’t exist yet, create it.
• Read two contents shared with you
• Leave at least 2 comments or questions on each text you read

How to submit

Add the link to your Google Docs
Add a screenshot of your post sharing your coursework