πŸ“… backlog

Module-Databases πŸ”—

[TECH ED] Module Project Level 100 πŸ”— Clone

https://github.com/CodeYourFuture/Full-Stack-Project-Assessment

Why are we doing this?

Here is the fabled Full Stack Assessment. This project will help you prepare for Final Projects. You must reach level 100 this week, but you can progress as much as you like.

Make sure you complete each level before moving on to the next stage. Your project can only be assessed as reaching a level when all the requirements for that level are met. When you get stuck, open a PR and explain your blocker. Get help from colleagues and mentors.

As a professional developer, you will often encounter blockers in your daily work. It can feel frustrating. Learning to share your blockers productively and resolve them collaboratively is an important step in becoming a good developer.

https://github.com/CodeYourFuture/Full-Stack-Project-Assessment

Maximum time in hours

6

How to get help

Share your blockers in your class channel. Use the opportunity to refine your skill in Asking Questions like a developer.

How to submit

  1. Fork to your Github account.
  2. Make a branch called Level 100
  3. Make regular small commits to your branch with clear messages.
  4. When you are ready, open a PR to the CYF repo, following the instructions in the PR template.

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 week

Anything else?

Final Projects Entry and Exit Criteria

  • 🎯 Topic Functional Programming
  • 🎯 Topic Iteration
  • 🎯 Topic Requirements
  • 🎯 Topic Structuring Data
  • 🎯 Topic Testing
  • πŸ• Priority Mandatory
  • πŸ”‘ Priority Key
  • πŸ¦‘ Size Large
  • πŸ“… Databases
  • Week 1
[TECH ED] PG Exercises πŸ”— Clone

https://pgexercises.com/questions/basic/

Why are we doing this?

Complete the first six of these ‘Simple’ SQL Queries.

https://pgexercises.com/questions/basic/

If you have time you can look at some of the others, but they may require extra research to complete.

Maximum time in hours

3

How to get help

Share your blockers in your class channel. Use the opportunity to refine your skill in Asking Questions like a developer.

How to submit

No submission step

  • 🎯 Topic Programming Fundamentals
  • 🎯 Topic Structuring Data
  • 🏝️ Priority Stretch
  • πŸ‚ Size Medium
  • πŸ“… Databases
  • Week 1
[TECH ED] Codewars πŸ”— Clone

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.

Maximum time in hours

1

How to get help

Collaborate with your peers in the #cyf-codewars channel.

How to submit

Your Codewars progress is tracked automatically.

  • 🎯 Topic Problem-Solving
  • 🎯 Topic Programming Fundamentals
  • 🎯 Topic Testing
  • πŸ• Priority Mandatory
  • πŸ‚ Size Medium
  • πŸ‡ Size Small
  • πŸ“… Databases
  • Week 1
[TECH ED] Prepare for Saturday's class πŸ”— Clone

https://www.youtube.com/playlist?list=PLozA7cloMbPh8gF7q5T9TnUAltjE3o33O

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 (Tech has max 16 per week total)

3

How to get help

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

  • :brain: Prep work
  • πŸ• Priority Mandatory
  • πŸ‚ Size Medium
  • πŸ“… Databases
  • Week 1
[PD] STAR Framework πŸ”— Clone

Coursework content

Use the provided spreadsheet to come up with interview examples in line with the STAR framework. The examples can be taken from previous work, study, or volunteering experience.

Estimated time in hours

4

What is the purpose of this assignment?

This assignment will improve your competency-based interview skills.

How to submit

Share the link to your copy of the spreadsheet on the ticket on your board.

  • πŸ• Priority Mandatory
  • πŸ‚ Size Medium
  • πŸ“… Databases
  • Week 1
[TECH ED] Check module success criteria πŸ”— Clone

https://curriculum.codeyourfuture.io/databases/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] Play the Bandit πŸ”— Clone

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. You can do this by completing one level a week from JS2 onwards. You can do one level a week!

You should be at level 16 or higher this week.

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 1