Coursework content

Finding a job in tech is your goal. And to achieve that, you must have many tools and skills. One of the most important tools is your CV (Curriculum Vitae).

A strong CV effectively communicates your qualifications, skills, and experiences leaving a positive impression on potential employers.

Estimated time in hours

2

What is the purpose of this assignment?

• Ensure your CV is up-to-date with the best practices
• Use your transferable skills and past experiences to describe skills that a developer needs and you already have
• When writing, think about a friend. How would you describe them? We tend to be more positive about others than ourselves.
• Use an Applicant Management/Tracking system. See some examples in this guide.

How to submit

• Share your Google Doc of your CV as a comment on this issue and on your MigraCode slack channel. Make sure the file is open to be commented on by anyone.
• Attach a screenshot of your slack channel post as a comment on this issue.

Anything else

Check out the CYF´s CV Guide

Coursework content

Once again, think about the Build Your Life plan and your latest Career Development plan, and review the goals you want to achieve. These should still be linked to the areas you want or must 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

Link to the coursework

https://github.com/Migracode-Barcelona/Module-Data-Groups

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, and review this CYF workshop on asking questions. 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 MigraCode 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://developer.chrome.com/docs/devtools/network/

Why are we doing this?

You’ll be using the network tab in the next module, so take some time now to follow along with this workshop. There’s a video and screenshots, but make sure you open Devtools and do the steps yourself.

Maximum time in hours

.5

How to get help

Try searching stackoverflow this time.

How to submit

No submission step. Just do it and be glad! 😛

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. Junior Cloud and DevOps roles are growing in the industry; React and fullstack junior roles are becoming scarce. So it’s a good idea to practice Linux skills to make yourself more employable. 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 MigraCode we build this skill 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 course. Set a task in your calendar to repeat every other day and spend 15 minutes a time.

1. This blog post by Tanner Dolby will walk you through level 1 to 5. Yes, you get the first 5 levels done for you.
2. Try to help others on the slack channel.

Maximum time in hours

2

How to get help

Work through the puzzles together in Slack

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

How to submit

There is no submission step. However, to apply for some roles, you must demonstrate these skills so it would be a good idea to learn them.

Anything else?

Here’s a ChatGPT prompt you can use to get the best, most helpful learning experience:

Please act as a friendly, warm, straightforward technical mentor. You are an experienced Site Reliability Engineer who uses the terminal regularly and understands all shell commands in bash. You can explain clearly, using English mostly at CEFR B2 level, how to execute shell commands and how to navigate Linux file systems. We will be playing The Bandit, Over the Wire, shell game together. I don’t want you to give me all the answers. I want you to walk me towards the answer, helping me to find out and learn Linux commands, explaining clearly what is happening as we go. Please answer my questions carefully and do not offer code solutions, just explain in English the approach I should take and then review the commands I suggest to you. Say okee dokee if you understand.

Link to the coursework

http://blog.cleancoder.com/uncle-bob/2014/12/17/TheCyclesOfTDD.html

Why are we doing this?

It is essential that you continue to use your TDD skills throughout the course. It is only through continual practice that you’re able to master all the steps in TDD. The best way to master TDD is by solving katas with this method in a strict time-bound fashion.

Maximum time in hours (Tech has max 16 per week total)

.5

How to get help

Review CYF´s workshop on asking questions https://programming.codeyourfuture.io/guides/getting-help/asking-questions/

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

Follow this mentored pair programming guide for guidance.

Book time with your volunteer using the slack channels. If there are any scheduling conflicts for this exercise, please inform the MigraCode team.

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

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 our learners to prepare for technical interviews when they’ll need to code in front of other people.

Acceptance criteria

• You have pair programmed on a piece of programming with a volunteer for at least one hour this sprint.

Objectives

• Talk aloud when thinking about a problem.
• Write code in front of someone else.
• Analyse your strategies for solving problems in code.

Link to the coursework

Data Groups collection

MigraCode Instructions – How to Access the Coursework

These Codewars exercises are part of the CodeYourFuture authored collections, so to access them:

1. Sign up to a Codewars account using your Github: https://www.codewars.com/join
2. Once signed up and logged in, follow the CodeYourFuture profile: https://www.codewars.com/users/CodeYourFuture
3. Then go to the collections page: https://www.codewars.com/users/CodeYourFuture/authored_collections

You should now be able to access all the relevant exercises. If you’re having trouble seeing the collections:

• Double-check that you’re logged in.
• Make sure you have followed the CodeYourFuture user on Codewars.
• Try opening the link in a different browser or incognito window.

Why are we doing this?

Choose some kata from the Data Groups collection. Could you demo a solution on Saturday? How would you do that? What would be interesting for others to know about your solution?

Maximum time in hours (Tech has max 16 per week total)

1

How to get help

Check the following links. Keep in mind that some of the instructions are very CYF-focused. However, most of it are general tips that are useful for everyone. If they mention to do something within the CYF slack, ignore it and apply it to MCB.

• Refer to the CYF Codewars docs
• Read Codewars advice from CYFers
• Read Codewars advice from mentors

Every week you need to complete at least three kata. Spend at least 20 minutes, three times a week, on your kata workout. Remember, after 20 minutes, take a break.

How to submit

Your codewars progress is tracked automatically and is available on the public API. You don’t need to submit it.

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?

Link to the coursework

https://migracode-itp.netlify.app/data-groups/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 student fulfilments
• 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

At the end of your module you will need to submit your own work through the MigraCode Submission Form. This means things like links to pull requests you have written sent from your GitHub account, and/ or Google Docs you have written.

What you need to submit is listed on the success page for the module.

Remember - the goal is your understanding. If you are not confident you could delete and re-do the work you’re submitting easily, you should take more time to revise the topics. It’s more important that you understand the work, than that it gets done quickly.