🏷️ backlog

Module-Databases 🔗

[PD] Tailor your CV for a specific JD 🔗 Clone

Coursework content

  • Choose one of the jobs you found during class
  • Tailor (adjust) your CV for that job vacancy considering the following:
    - identify the skills and competencies
    - what you learned about employers’ needs when making these changes
  • Review the CV with a tool like Grammarly. You should not make any mistakes.
  • Highlight changes, share the JD and tailored CV on the #cyf-profile-review Slack channel, and request a review.

Estimated time in hours

2

What is the purpose of this assignment?

To learn and practice how to tailor your CV for a specific job

How to submit

Screenshot the feedback you get on your CV and post it as a comment on this ticket for review.

  • 🏕 Priority Mandatory
  • 🐂 Size Medium
  • 📅 Databases
  • 📅 Week 4
🧑🏾‍⚖️ 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
  • 📅 Databases
  • 📅 Week 4
  • 📅 Week 1
[PD] Launch Project - Team canvas 🔗 Clone

Coursework content

Come together with your Launch project team and go through the team canvas slides. Prepare your own team canvas as the first step of your final projects work.

Estimated time in hours

2

What is the purpose of this assignment?

This assignment will support to build a strong foundation for your launch project team.

How to submit

Share the link to your team canvas on the ticket on your coursework board.

  • 🐂 Size Medium
  • 🔑 Priority Key
  • 📅 Databases
  • 📅 Week 4
[TECH ED] Prepare for Final Projects 🔗 Clone

https://curriculum.codeyourfuture.io/the-launch/

Why are we doing this?

If you want to graduate, you’ve got to join a cross functional Agile team building a full stack web application over four weeks.

Find the entry and exit criteria for the Launch module and review it.

To prepare:

  1. Read the curriculum! What does it tell you about Final Projects?
  2. Grab the starter kit and get a version deployed and running (there are guides on the curriculum to help you, and there’s a wiki on the starter kit with all the common problems.)
  3. Attend a Merge Conflicts workshop
  4. Read up on small scoped feature branching
  5. Take a look at some successful Final Projects; look at their project boards and especially notice velocity – you should be opening a small PR at least once a day during final projects, not one a week.

Maximum time in hours

3

How to get help

Share your blockers in your class channel.

Talk to CYF grads about their experiences.

Attend a demo day if you have the opportunity.

  • :brain: Prep work
  • 🏕 Priority Mandatory
  • 🐂 Size Medium
  • 📅 Databases
  • 📅 Week 4
[TECH ED] E-Commerce API 🔗 Clone

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

Why are we doing this?

Now you understand your database, how will this change how you design your API?

You should write this app in TDD style. This project will help you understand how to do this. The user stories are re-expressed as acceptance criteria, and then the acceptance criteria is re-expressed as tests. Look in the /tests folder to see the example.

When you go to Final Projects, you will save yourself a lot of time by writing your API in this way. You will also find it much easier to share the work, as each acceptance criteria could be met by a different team member, using the feature branch workflow.

Quality check!

In this project, you must write the test first.

It’s better to turn in a smaller set of user stories than to turn in untested features.

If you’re running out of time, scope down your application rather than commit untested code. Cut your scope, not your quality. Include a list of the stories you did, and didn’t, get to in your PR message.

Maximum time in hours

10

How to get help

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

If you’re struggling with the feature branch workflow, you won’t be alone. There are workshops available – do one together in class.

How to submit

  1. Fork to your Github account.
  2. Make a new branch named E-Commerce-API
  3. For each user story, make a feature branch like this feature/1-list-all-products
  4. Complete your user story, make sure the test is passing, then merge into your E-Commerce-API branch
  5. When you are ready, open a PR to the CYF repo, following the instructions in the PR template.
gitGraph commit id: "e-commerce-api" branch e-commerce-api branch feature/1-list-all-products commit id: "assert api should return list" commit id: "make api return list" checkout e-commerce-api merge feature/1-list-all-products branch feature/2-filter-product-list commit id: "assert api should filter list" commit id: "make api filter list" commit id: "check query works" checkout e-commerce-api merge feature/2-filter-product-list

How to review

For someone else to check out your code, they will need your .env file. Use https://onetimesecret.com/ to share this.

Anything else?

https://blog.gitguardian.com/secrets-api-management/
https://www.youtube.com/watch?v=JUpKDkb4Zhc

  • 🎯 Topic Iteration
  • 🎯 Topic Testing
  • 🎯 Topic Time Management
  • 🏕 Priority Mandatory
  • 🐋 Size X-Large
  • 🔑 Priority Key
  • 📅 Databases
  • 📅 Week 4
[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. To apply for the Launch you need a 5kyu. How will you achieve this?

You may be asked to pair programme at any time and re-do your logged solutions on your Codewars account, so make sure you understand your solutions and can explain them.

Maximum time in hours

1

How to get help

Collaborate with your peers in the #cyf-codewars channel. Ask for a study session or to join a Codewars club.

How to submit

Your Codewars progress is tracked automatically.

  • 🎯 Topic Problem-Solving
  • 🎯 Topic Programming Fundamentals
  • 🏕 Priority Mandatory
  • 🐇 Size Small
  • 📅 Databases
  • 📅 Week 4