Backlog

Module-Decomposition 🔗  

Expand all

Mandatory Tasks

These tasks will help consolidate your learning for this sprint. You should complete as many of these as possible before class on Saturday.

Middleware exercises 🔗 Clone

Middleware exercises 🔗

Task code

CYF-1165 - make sure to include this in your PR title or description.

https://sdc.codeyourfuture.io/decomposition/sprints/3/prep/

Why are we doing this?

Reasoning about code re-use is an important skill, and middlewares are common patterns.

Maximum time in hours

2

How to submit

Make a pull request against the CodeYourFuture fork of this repository adding two new directories - one containing your Express application with two custom-written middlewares, and one which replaces one with an off-the-shelf middleware.

Complete the mid-way survey 🔗 Clone

Complete the mid-way survey 🔗

Follow this link to the survey: https://forms.gle/3Ktdu1rebDyjhdxi9

This is an anonymous survey that should take a maximum of 5 minutes to complete.

Why are we doing this?

This survey helps you continue to reflect on your skills, Slack engagement and community engagement now you’ve reached the mid-way point in the SDC. It also helps us know what we’re doing well and what could be improved.

Submission & Review

Finish the survey and click submit, thank you!

Optional Tasks

These are optional "stretch goals" to attempt when you have finished the mandatory tasks. They may be more challenging or require some additional research.

Give a demo in a demo session

Give a demo in a demo session

Presenting information is really important. You need to practice giving demos, and each week build on the feedback you got the previous week.

At CYF we expect you to demo your work to the class. You must have many opportunities to practice how to clearly and simply explain your work to others. This is really important both for interviews and for getting promoted later on.

Attend the SDC demo sessions this week during the saturday class, and give a presentation about a topic of your choosing.

Also try to give some feedback to one of your fellow trainees during this session on their demo.

Aim for a 5 minute demo. But your demo must be at least 1 minute and at most 10 minutes long. Check out our guide about presenting.

You only need to give one of these demos every two weeks. You can give extra demos in addition whenever you want more practice.

Mentored Coding (volunteer team)

Mentored Coding (volunteer team)

Learning Objectives

Mentored coding 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 team up with a volunteer to work on it together.

See the mentored coding guide for guidance.

Book time with a volunteer using one of the scheduling links in the #cyf-mentored-coding Slack channel’s canvas. If there are no available times, please post in #cyf-mentored-coding.

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

You will 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.