🏷️ backlog

Module-Databases πŸ”—

[TECH ED] Coursework feedback πŸ”— Clone

https://github.com/CodeYourFuture/Module-Databases/issues/

Why are we doing this?

The CYF curriculum is an open source project. Like all software, it is continually revised and improved in iterations.

Help improve the curriculum by giving quick emoji feedback on any assignment.

Screenshot 2024-02-23 at 14 06 56

Feedback on this assignment by pressing the emoji reaction button on the top comment.

Emoji Key

πŸ‘ = Useful
πŸ‘Ž = Not useful

πŸš€ = Way too much time given
πŸ˜• = Not enough time given

You are invited to give feedback on any assignment in this way. Do this on the CYF issue, not your copy, so CYF can track it using the GitHub reactions API.

Maximum time in hours

.05

How to submit

Click the emoji button on the first post on any coursework assignment.

  • 🎯 Topic Iteration
  • 🎯 Topic Teamwork
  • 🏝️ Priority Stretch
  • πŸ¦” Size Tiny
  • πŸ“… Week 3
[PD] Practice job interviews πŸ”— Clone

Coursework content

  • Practice your interview with someone in the community using the JD you found in the previous exercise.
  • Record yourself using a computer camera if you are meeting online or a phone camera if you are meeting in person.
  • Watch the video and self-evaluate. Your community partner should give you feedback as well.
  • Write a short 200-word reflection based on the feedback and explain how you will apply that in the following interviews.
  • Pre-FP work

Estimated time in hours

3

What is the purpose of this assignment?

  • To practice job interviews.

How to submit

  • Upload the reflection as a link on this ticket for review. If you have written it in a Google docs, make sure it is open for comments.

Anything else?

  • πŸ• Priority Mandatory
  • πŸ‚ Size Medium
  • πŸ“… Week 3
[PD] Professional statement clinic πŸ”— Clone

Coursework content

Prepare a professional statement for your Linkedin profile (“About” section).

Estimated time in hours

1

What is the purpose of this assignment?

This assignment will help you to refine your professional statement on Linkedin.

How to submit

Share your professional statement with the group in Slack and help each other out to create the best, most impactful, honest, and exciting statement. Share the screenshot of your post on your coursework ticket.

  • πŸ• Priority Mandatory
  • πŸ‡ Size Small
  • πŸ“… Databases
  • πŸ“… Week 3
[TECH ED] Prepare for Saturday's class πŸ”— Clone

https://www.youtube.com/playlist?list=PLozA7cloMbPhJgWwncnb-N4yI07JpUcs5

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 3
[TECH ED] E-Commerce πŸ”— Clone

https://github.com/CodeYourFuture/Module-Databases/tree/main/E-Commerce

Why are we doing this?

This project is about really understanding your database by representing it in a diagram. How do the tables relate to each other? How do references work? What is the primary key? What is a foreign key? Drawing a simple schema will clear this all up.

Remember, simple is better. Use a pencil and paper.

Maximum time in hours

6

How to get help

Bring these to class and work on them in study time together.

How to submit

  1. Fork to your Github account.
  2. Make a branch named after the project.
  3. Make regular small commits 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: "e-commerce"
    branch e-commerce
    commit id: "List all socks"
    commit id: "List products cost >100"
    commit id: "5 most expensive products"

How to review

Bring your schemas to class and we’ll talk about them.

  • 🎯 Topic Communication
  • 🎯 Topic Structuring Data
  • πŸ• Priority Mandatory
  • πŸ¦‘ Size Large
  • πŸ“… Databases
  • πŸ“… Week 3
[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
  • πŸ• Priority Mandatory
  • πŸ‚ Size Medium
  • πŸ‡ Size Small
  • πŸ“… Databases
  • πŸ“… Week 3
[TECH ED] Module Project: Level 300 πŸ”— Clone

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

Why are we doing this?

Continue building your full stack project. You must reach level 300 by the end of this week and seek code review from a mentor.

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. Read the requirements carefully. 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.

Maximum time in hours

8

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 regular small commits with clear messages.
  3. 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
  • 🎯 Topic Code Review
  • 🎯 Topic Delivery
  • 🎯 Topic Iteration
  • πŸ• Priority Mandatory
  • πŸ‹ Size X-Large
  • πŸ”‘ Priority Key
  • πŸ“… Databases
  • πŸ“… Week 3