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.

Choose some kata from the Data Groups collection but now also work through the Array and Object Methods collection. This collection specifically helps you practice working with arrays and arrays of objects. Look on the sidebar, it has a giant list of the methods that you can practice with this collection, but most important it has lots of map filter and reduce problems, which you will use all the time in programming.

Time traveller

Don’t just go forwards through the collections. Loop back and review your work from last month. How have you progressed? Would you choose another solution now?

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

Share a link in the form https://codeyourfuture.github.io/Codewars-Progress-Checker/#YOUR_CODEWARS_USERNAME.

You can obtain the link from the browser location bar after submitting your Codewars username on the Codewars Progress Checker page.

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. What about different languages?

Why are we doing this?

Pair programming is an excellent way to develop programming and communication skills. It is often much easier to work through something when working on something 1-to-1. It is also helps you to prepare for technical interviews when you may need to code in front of other people or explain your solution to a problem.

Pick one piece of programming you’re doing (we recommend a Codewars kata) and pair up with a volunteer to work on it together.

See the mentored pair programming guide for guidance.

Book time with a volunteer using one of the Scheduling links in the #cyf-pair-programming slack channel’s canvas. If there are no available times, please post in #cyf-pair-programming.

Remember, as a learner, you will need to explain your thought process, plan out what to do, write the code and check it works.

Submission & Review

You well get feedback from the volunteer during the session. If there are specific topics you would like to receive feedback on then let them know at the start of the session so they know what to focus on.

Link to the coursework

https://github.com/CodeYourFuture/Module-Data-Groups/tree/main/Sprint-2

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.

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

Link to the coursework

https://github.com/CodeYourFuture/terminal-tic-tac-toe

Why are we doing this?

One of the most important abilities you can have as a software developer, is the ability to work well within a team. There are many aspects to this, including:

• communicating clearly and consistently
• breaking down work into smaller tasks that can be shared among the members of the team
• handling disagreements with your team mates
• working with Git as a team

In this project, you will need to work as part of a team of 3 people. Use Slack to find 2 other people in your region to work with. Organise a time to meet with your team. Together, follow the steps in the README.md file of the repository. In this sprint, you can work through steps 1 to 5, and start working on step 6.

Maximum time in hours

3

How to get help

If you get stuck or need help, discuss your questions or problems with your teammates. If you need further help, raise your questions on Slack.

Submission & Review

Nothing to submit for this issue. Your team will be completing it’s work in the next sprint.

Link to the coursework

https://www.codewars.com/collections/cyf-data-groups-sprint-2-mandatory

Why are we doing this?

Every week, you need to complete all of the katas in the collection. If you have extra time, you can do extra katas at random on CodeWars.

Spend at least 20 minutes per kata, find time at least three times a week to complete this.

Find the Collection called “CYF Data Groups | Sprint 2 | Mandatory” on the CodeYourFuture account.

Check your Codewars completion status via the Codewars Progress Checker.

Maximum time in hours

2

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 Book a pair programming slot from the available pairing appointments in the CYF Pair Programming Slack Canvas

How to submit

Share a link in the form https://codeyourfuture.github.io/Codewars-Progress-Checker/#YOUR_CODEWARS_USERNAME.

You can obtain the link from the browser location bar after submitting your Codewars username on the Codewars Progress Checker page.

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 coursework

https://overthewire.org/wargames/bandit/

Why are we doing this?

Basic Linux skills are essential for roles in Cloud, DevOps, Cyber, and SRE so it’s a good idea to practice them. At the basic level this means using a computer from the command line instead of a GUI. You will learn to use commands to move from folder to folder, to open and edit files, and to get info like the size of a file or its location. At CYF we develop these skills by playing a game called The Bandit.

There are many levels, and many more games after The Bandit, but your goal is to get to Level 20 by the end of this module. There is time in Sprint 1 and Sprint 2 to work on this task.

Maximum time in hours

2

How to get help

Refer back to the blog post from the previous module for a reminder of the first five steps.

Work through the puzzles together in #cyf-over-the-wire.

Don’t share solutions in this channel, or you steal from others the opportunity of learning.

How to submit

There is no submission step for this exercise.

Why are we doing this?

Understanding mental models will help you prepare for the debugging workshop in class.

Read https://jamesclear.com/mental-models and a few of the linked mental models (whichever you find interesting).

Maximum time in hours

1

Submission & Review

There is nothing to submit for this task

Why are we doing this?

Everybody’s CV will be slightly different. When you read someone else’s CV you will see examples of this - some will be things you like, some will be things you don’t like. In this exercise you will give both positive and constructive feedback on a colleague’s CV.

Read one of the CVs that hasn’t been reviewed yet on the #cyf-profile-review 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.

Maximum time in hours

1

Submission & Review

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

Why are we doing this?

Providing and receiving constructive feedback is very important. When working in a team you will need to ask colleagues for feedback and they may ask you to provide feedback for them. You need to be able to turn that feedback into actions to help you improve.

Invite one person (fellow trainee or a volunteer) from the class you have worked with this week and arrange a call. Ask for their feedback to help you get more insight into how you are progressing with your learning.

Write a 250-word essay reflecting on your strengths and development areas as a result of their feedback.

Maximum time in hours

2

Submission & Review

Create the Google Doc in your own Google Drive. Ensure the document can be opened and commented on by reviewers - you can find out how to do that here. Share the link to the document in a comment on this issue in your planner.

Why are we doing this?

We give and receive feedback in many ways. Sometimes we do it face-to-face, other times we do it in writing.

In pairs, within your groups review 1 of the 3 written emails on the issue Writing a meeting request email. Provide objective feedback and actionable improvement points for either person’s English or the content itself. You can do this in person or via a call. Later send it in writing to your peer.

Maximum time in hours

1

How to submit

• Share the link to your written feedback as a comment on this issue

Why are we doing this?

LinkedIn is a platform where professionals from a range of industries can connect and share their experience. It is also a useful place to find jobs and take online courses. Familiarity with the platform and how it works will be useful in your future career.

1. Set up a LinkedIn profile if you don’t already have one.
2. Find 3 LinkedIn profiles that you think are good and reflect on why they are good or effective.
3. Think about what you can use/adapt from these people’s LinkedIn profiles to yours.

Maximum time in hours

0.5

Submission & Review

• Share the link to your LinkedIn profile on this issue.
• Share the list of things you would like to use/adapt on your profile as a comment on this issue.

Why are we doing this?

Research how to write a business proposal to share within your workplace. For example, see:

• Write a Proposal to Management
• How to present an idea to your boss

Imagine taking a risk in a software development job. You want to suggest a new step in your e-commerce checkout process, persuading customers to subscribe to 1-day delivery like Amazon Prime. The step might improve customer loyalty or cause confusion and complaints. It might increase revenues. It might be too complicated to get right.

Write a proposal like an email, proposing the step in the checkout process to your team, what risks you perceive and how you will mitigate the risks. Write it in a document between 0.5 to 1 page long.

Maximum time in hours

1.5

How to submit

• Share your document on the cohort channel, asking for feedback.
• Give feedback on your peer’s proposal.
• Post a screenshot of your post with some feedback, if possible, as a comment on this issue
• Also post your google doc as a comment here. Make sure the file is open for comments.

Link to the coursework

https://www.codewars.com/collections/cyf-data-groups-sprint-2-stretch

Why are we doing this?

Every week, you need to complete all of the katas in the collection. If you have completed the mandatory katas for Data Groups Sprint 2, you can try these stretch katas.

Spend at least 20 minutes per kata.

Find the Collection called “CYF Data Groups | Sprint 2 | Stretch” on the CodeYourFuture account.

Check your Codewars completion status via the Codewars Progress Checker.

Maximum time in hours

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 Book a pair programming slot from the available pairing appointments in the CYF Pair Programming Slack Canvas

How to submit

Share a link in the form https://codeyourfuture.github.io/Codewars-Progress-Checker/#YOUR_CODEWARS_USERNAME.

You can obtain the link from the browser location bar after submitting your Codewars username on the Codewars Progress Checker page.

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.