Coursework content

Consider the following types of conflict and choose one.

• A technical disagreement about how to write the code for a well-understood task.
• The manager wants you to work faster but with a smaller team by rushing.
• A competitive and ambitious person wants you to look bad so they can get a promotion instead.

Sort the following list of approaches or questions into priority and usefulness. Add your own strategies to this list.

• Don’t let your emotions control you.
• Paraphrase what the other person said, confirming your understanding and showing empathy.
• Each conflict is an opportunity.
• Find out what facts the other person knows.
• What do they want? Relatively few people have hidden agendas.
• What do you want? Assert your points clearly without being too shy.
• What is their general attitude and approach?
• What possible solutions to this conflict might exist?
• Agree on part of the solution if you can’t agree on all of it.
• Build a network of people to support your resilience and perhaps mediate the conflict.
• Communicate clearly before there is a conflict.
• Be assertive enough to make your point.
• Escalate the topic to someone more senior to arbitrate.
• Keep away from the other person and find your own solution without them.
• … add your own strategies.

Estimated time in hours

0.5

What is the purpose of this assignment?

Reflecting on your learning of last week’s class about resolving conflict

How to submit

• Add your final order on a comment on this issue

Anything else?

Coursework content

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.

Estimated time in hours

1.5

What is the purpose of this assignment?

• Think about risks at work and risk mitigation strategies.
• Practice writing a business proposal.

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.

Anything else?

Coursework content

Read one of the CVs that hasn’t been reviewed yet on the #cyf-profile-review https://codeyourfuture.slack.com/archives/C7MBLPR6F 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.

Estimated time in hours

1

What is the purpose of this assignment?

• See the variety of content people write in their CVs.
• Judge a CV as an external reader. Then you can know what to write better.
• Give constructive feedback to your peers.

How to submit

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

Anything else?

Link to the coursework

The exercises and challenges for this week are located in the module repo: https://github.com/CodeYourFuture/Module-JS2 inside the week-2 directory. Ensure you read the readme.md first to figure out what to do.

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.

gitGraph
    commit id: "start"
    branch feature/week-2-exercises
    commit id: "skeleton page code"
    commit id: "Fonts and colours"
    commit id: "mobile layout"
    commit id: "lighthouse audit revisions mobile"
    commit id: "desktop layout"
    commit id: "lighthouse audit revisions desktop"
    checkout main
    merge feature/week-2-exercises

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

Link to the coursework

https://render.com

Why are we doing this?

You’ll need to sign up to render so you can host some of the applications you build on the course.

Maximum time in hours

0.05

How to get help

Share your blockers in your class channel
https://syllabus.codeyourfuture.io/guides/asking-questions

Why are we doing this?

You’ll need to regularly check solutions to evaluate your understanding.
However, you must attempt the activities first before you use the solutions.
You can find the solutions for all the assignments in this repo’s solutions branch.

Maximum time in hours

0.5

Link to the coursework

https://github.com/CodeYourFuture/Portfolio/tree/Module-JS-2

Why are we doing this?

At Code Your Future, we expect everyone to graduate with a unique professional portfolio. You will begin building this portfolio as soon as you begin our Software Development Course. At first, your portfolio will be a simple HTML/CSS page deployed to Github Pages or Netlify. This is your MVP.

Every module, you will iterate on your portfolio, adding a new project and improving your design and presentation. By the time you apply to Final Projects, your portfolio will help you show you are ready to be accepted on to a development team. The process of developing the portfolio, through specified git workflows, through small scoped feature development, and through case study and written presentation, will all help you succeed in Final Projects.

Maximum time in hours

3

How to get help

Share your blockers in #cyf-portfolios.

Use the opportunity to refine your skill in Asking Questions like a developer.

How to submit

1. Fork to your Github account.
2. Check out the branch for the module you are on.
3. Make regular small commits with clear messages.
4. When you are ready, open a PR to the CYF repo, to the matching branch, following the instructions in the CYF repo.

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 time

Anything else?

To get a job in tech you need a minimum set of tools that you need to acquire or build over the course of this year. You need:

1. a well written CV
2. a solid portfolio of junior level work that makes you memorable to a recruiter
3. to be able to plan, build, and ship a working product in an Agile team
4. to be able to score reasonably well in a timed technical test
5. to be able to do an interview in fluent English

Keep this in mind.

From Module-JS2 created by SallyMcGrath: CodeYourFuture/Module-JS2#5

From Module-JS3 created by Dedekind561: CodeYourFuture/Module-JS3#18

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.

Find the Collection for this week on the CodeYourFuture account.

Take some time to check your levels. Before you are accepted on to a Final Project on the developer track, you need to complete the Final Projects collection and reach a Level 5 kyu in Codewars. Are you on track to reach this standard? Have you run a study group to work on kata? Have you reached out on the #cyf-codewars channel? What is your plan to meet this goal?

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

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.

Link to the coursework

Use the prep view from the CYF curriculum to prepare for this week.

Why are we doing this?

It is essential to start learning new concepts and ideas before Saturday’s session. During the week, we expect you to get stuck and form questions about the new content so you can address misconceptions during Saturday’s session. The prep work here will introduce you to the new concepts for the week.

Maximum time in hours

4

How to get help

Share your blockers in your class channel. Remember to Ask Your Questions like a developer.

How to submit

Write down at least one specific technical question to bring to the group.

How to review

Come to class with your questions