Backlog
Module-Tools ๐
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.
Individual shell tools exercises ๐ Clone
Individual shell tools exercises ๐
Task code
CYF-1145 - make sure to include this in your PR title or description.Link to the coursework
https://github.com/CodeYourFuture/Module-Tools/tree/main/individual-shell-tools
Why are we doing this?
We use shell tools every day when writing software. Understanding them, and being fluent thinking about them, is an important skill.
Also, using shell tools encourages us to think about how we can break problems down into smaller sub-problems, which someone else may have already solved, saving us time solving them ourselves.
Maximum time in hours
4
How to submit
Submit a PR from your fork of the Module-Tools repo with the answers added to the files.
Number systems exercises ๐ Clone
Number systems exercises ๐
Task code
CYF-1146 - make sure to include this in your PR title or description.Link to the coursework
https://github.com/CodeYourFuture/Module-Tools/tree/main/number-systems
Why are we doing this?
Binary and hexadecimal numbers come up a lot when writing software. Understanding them, and being fluent thinking about them, is an important skill.
Maximum time in hours
1
How to submit
Submit a PR from your fork of the Module-Tools repo with the answers added to the files.
Give a demo in a demo session
Give a demo in a demo session
Learning Objectives
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 (Edu Team) ๐ Clone
Mentored Coding (Edu 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 your assigned education mentor for this.
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 your mentor 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.