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-Flows/tree/main/debugging/book-library

Why are we doing this?

A big part of any development role is identifying and fixing bugs in code. Sometimes you will find these bugs yourself, other times users or colleagues will report them to you.

In this exercise we have provided some code which doesn’t work properly. Start by running the code, then work through the list of bugs and attempt to fix them.

Maximum time in hours

3

How to get help

1. Share your blockers in your class channel. Use the opportunity to refine your skill in Asking Questions like a developer.

2. Use the debugger! Write tests! Use the tools you have been learning to help you solve problems methodically.

Submission & Review

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 based on main for each project.

Why are we doing this?

Being on LinkedIn isn’t enough to get noticed. You also need to make sure that you are active on it.

LinkedIn created a Social Selling Index (https://www.linkedin.com/sales/ssi.) which shows how you are in relationship to others in your industry or your network. You can use this as a key performance indicator to ensure you are being ranked higher after your actions.

Think about your strategy to get more active on LinkedIn. Some examples are below, but you can use your creativity. Start with one action and then build upon it.

• Repost interesting articles at least once a week
• React to one of your connections’ posts three times a week
• Share an important Professional Development learning of this week
• Share an important Technical Education learning of this week (not on the same day as the PD one)
• Comment on one of your connections’ posts once a week

Maximum time in hours

0.5

Submission & Review

• Share the screenshot of your LinkedIn Social Selling Index on this issue.
• Add what is the one action you will commit to. Write it using in a SMART way and add it as a comment on this issue.

Link to the coursework

https://www.codewars.com/collections/cyf-data-flows-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 Flows | Sprint 1 | 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.

Why are we doing this?

In order to use LinkedIn effectively it’s important to reflect on what works for you and on what doesn’t work so well.

Write a 100-word text with the top 3 tips you have learnt about LinkedIn and how to use it effectively.

Review the text with an automated grammar tool.

Estimated time in hours (PD has max 4 per week total)

0.5

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?

A SWOT analysis is a tool used to asses Strengths, Weaknesses, Opportunities and Threats.

Conduct a personal SWOT analysis. By answering the following questions, consider the key areas you want to improve. Remember to refer to the development plan you have already been working on:

• Strengths: What are you great at? What makes you stand out? What positive comments do people say about your strengths? What are your greatest achievements?
• Weaknesses: What hard and soft skills do you need to work on? Where do you need to improve? What holds you back? What key habits do you want to overcome? What do others say about your development areas?
• Opportunities: Who can help you achieve your goals? What can you do differently to become more employable? How can you go the extra mile? How can you create opportunities?
• Threats: What could stop you from achieving your career goals? What do you need to stop doing now? What’s out of your control?

Write your analysis down.

Maximum time in hours

1

How to submit

• Share the link to the doc with your SWOT analysis on your issue. Make sure anyone with this link can comment on it.
• Review your Career Development Plan if it is applicable.

Why are we doing this?

Work on your Career Development plan, so that it reflects your learnings and where you evolved. Your goals might be different now, and writing them down can keep your focus and give you a tool to discuss them with anyone you trust who would like an opinion.

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.

Technical knowledge is important, but the skills and processes are also important so you can get a job in tech. So think about both sides.

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

Maximum time in hours

0.5

Submission & Review

Your development plan is your own and so there is no need to submit it for review. If you would like feedback you could share it with a mentor or peer you respect and ask for their advice.