π·οΈ backlog
Module-Servers π
[TECH ED] Play the Bandit π Clone
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. It’s a good idea to practice Linux skills to make yourself more employable and feel more comfortable operating computers.
Your goal is to get to Level 20 by the end of the Databases module.
Maximum time in hours
.5
How to get help
Work through the puzzles together in #cyf-over-the-wire
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 and some courses (like CYF+ ) you must demonstrate these skills, so it would be a good idea to learn them.
Anything else?
Here’s an AI 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.
And remember: every time an LLM offers code you don’t recognise, you must ask “Is this valid?” and “is this safe?” before you continue. AI is confidently wrong, a lot.
- π― Topic Problem-Solving
- π― Topic Programming Fundamentals
- π Priority Mandatory
- π¦ Size Tiny
- π Week 4
[PD] Interview with an AI π Clone
Coursework content
Practice interviews and selling yourself with ChatGPT or a similar tool. Explain to the AI tool, your background, and the role you are interested in. Then, ask it to interview you. Use this document to guide you on how to do the interview.
Estimated time in hours
0.5
What is the purpose of this assignment?
You donβt have to wait for a peer or volunteer to enhance your interviewing skills. Use AI tools for this purpose.
How to submit
Copy/paste your conversation with ChatGPT on a Google doc and share it on this issue. Make sure the file is open for comments.
- ποΈ Priority Stretch
- π Size Small
- π Node
- π Week 4
[PD] Update your development plan π Clone
Coursework content
Define actions from your own feedback and the interviewer following the mock interview. Update your personal development plan according to this feedback.
Estimated time in hours
0.5
What is the purpose of this assignment?
This assignment will help you improve the areas identified during the mock interview.
How to submit
Share your development plan for this section as a Google doc/sheet. Make sure it is open for comments.
- π Priority Mandatory
- π Size Small
- π Node
- π Week 4
[PD] Mock interview π Clone
Coursework content
Pair up with a peer. Find a job advertisement you are both interested in. Arrange an online meeting to interview each other for that role.
Interview each other using a video conference software (you should be able to record the interview). Spend a maximum of 15 minutes per person.
Following the interview, watch the recording and think about 2 examples in which you sold yourself well and why. Then, think about 2 examples in which you didn’t sell yourself well and why. Write a reflection (what went well/not so well) of a minimum of 100 words.
Estimated time in hours
1,15
What is the purpose of this assignment?
This assignment will help you to practice interviewing skills. You will be able to see both sides of the process and identify your areas for improvement.
How to submit
- Share your reflection on a thread in the main channel.
- Share the link or screenshot of your reflection on this ticket as a comment
- π Size Small
- π Priority Key
- π Node
- π Week 4
[TECH ED] Check module success criteria π Clone
Link to the coursework
https://curriculum.codeyourfuture.io/node/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 Trainee Agreement
- 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
In week 4 of your module you will need a representative to report to the organisation. Here’s your template, fill in your details and delete as appropriate:
π Cohort Progress Report from @cohort-name to @programme-team
- criterion
- criterion
- criterion
- criterion
β
We are progressing to the next module.
β We are taking a consolidation week to meet our targets.
- π― Topic Code Review
- π― Topic Communication
- π― Topic Delivery
- π― Topic Requirements
- π― Topic Teamwork
- π― Topic Testing
- π― Topic Time Management
- π Priority Mandatory
- π¦ Size Tiny
- π Week 1
- π Week 4
[TECH ED] Mailing list API π Clone
Link to the coursework
https://github.com/CodeYourFuture/Module-Node/tree/main/mailing-list-api
Why are we doing this?
In this challenge you will take all your knowledge of APIs and backend thus far to build an API that can process a full range of different HTTP requests.
Maximum time in hours
12
How to get help
Share your blockers in your class channel
https://syllabus.codeyourfuture.io/guides/asking-questions
How to submit
- Fork to your Github account.
- Make a branch for this project.
- Make regular small commits in this branch with clear messages.
- When you are ready, open a PR to the CYF repo, following the instructions in the PR template.
- Connect your PR to this ticket by writing #89 in your message
gitGraph commit id: "start" branch feature/mailing-list-api commit id: "update gitignore" commit id: "skeleton code with requirements" commit id: "tests for route lists" commit id: "GET, PUT" commit id: "DELETE" commit id: "revising tests, small fixes, listed" checkout main merge feature/mailing-list-api
- π Priority Mandatory
- π Size Medium
- π Priority Key
- π Week 4
[TECH ED] Codewars π Clone
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.
- π― Topic Code Review
- π― Topic Problem-Solving
- π― Topic Programming Fundamentals
- π― Topic Requirements
- π― Topic Time Management
- π Priority Mandatory
- π Node
- π Week 4