βπ½ Register
π‘ Morning orientation
Learning Objectives
Planning during the week
π£ Steps
If you haven’t done so already, choose someone (volunteer or trainee) to be the facilitator for this morning orientation block. Choose another to be the timekeeper.
ποΈ The Facilitator will:
- Assemble the entire group (all volunteers & all trainees) in a circle
- Briefly welcome everyone with an announcement, like this:
π¬ “Morning everyone, Welcome to CYF {REGION}, this week we are working on {MODULE} {SPRINT} and we’re currently working on {SUMMARISE THE TOPICS OF THE WEEK}”
- Ask any newcomers to introduce themselves to the group, and welcome them.
- Now check: is it the start of a new module? Is it sprint 1? If so, read out the success criteria for the new module.
- Next go through the morning day plan only (typically on the curriculum website) - and check the following things:
Facilitator Checklist
- Check the number of volunteers you have for the morning
- Check someone is leading each session
- Describe how any new activities works for the group
- Decide how best to allocate trainees and volunteers for a given block - most blocks will make this clear
β° The Timekeeper will:
- Announce the start of an activity and how long it will take (check everyone is listening)
- Manage any whole class timers that are used in an activity
- Give people a 10-minute wrap-up warning before the end of an activity
- Announce the end of an activity and what happens next
Collective job hunt
π€π½ FeedbackLearning Objectives
Introduction
Collective job hunt
π― Goal: To look for jobs collectively and understand why helping each other is important. (30 minutes)
In groups of 3-4 people, find at least two job opportunities
- Use the LinkedIn Job Search
- Search for titles that aren’t too generic but not too narrow. For example, software engineering or software developer
- Filter down your search using the location you want the job to be in, which is probably where your cohort is.
- The next filter could be the seniority of the role. Entry-level is most likely what you are looking for, but a mid-level might also be suitable in some cases. Explore.
- Agency or Company: focus on finding job opportunities directly from a company instead of an agency. Especially if you have a third or second relationship with the hiring person or anyone in that company.
- From the outcome, each person should choose one job description, read it and decide, in the group, if and why they should add (or not) this job opportunity.
Add them to the form of your cohort location: South Africa, Glasgow, North West, London, West Midlands
- Filling in the spreadsheet correctly is very important. You can do it via the form linked above or directly in the spreadsheet
- Add the company name, not the agency
- The company link and the job link should be from the company website, not from LinkedIn
- Good quality data will mean everyone has a good overview of what is going on
Discuss the needs of employers
π€π½ FeedbackLearning Objectives
Preparation
Introduction
Understanding the needs of employers
π― Goal: To understand employersβ needs and how that can benefit you. (30 minutes)
Work in groups of 4-5 people.
Take 20 minutes to discuss the following scenario. Write at least 2 ideas about the advantages of hiring junior developers and 2 ideas about the disadvantages.
Everyone should answer them and state their view and opinion
Imagine you are an Engineering manager at a (small/medium/large) company and planning your headcount for the next year. You are hiring a lead and two midlevel developers but are unsure about hiring more juniors. What are the advantages and disadvantages of hiring a junior?
In the last 10 minutes, first each group reads aloud the disadvantages of hiring a junior developer, then each group reads aloud the advantages.
Morning Break
A quick break of fifteen minutes so we can all concentrate on the next piece of work.
Progress check-in π
Link to the coursework
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
Merge Conflict Workshop π
DOM Merge Conflicts
This workshop contains a collection of DOM components. For this workshop, you will be creating branches for refactoring and updating the components and then resolving the merge conflicts that arise. You’ll be working in pairs, learning how to handle branching, refactoring, and creating pull requests.
Overview
Objective: Learn to resolve merge conflicts that arise during software development
Activity: Update and refactor DOM components in two different Git branches
Duration: 1 hour
Describe how merge conflicts can occur in a development setting
Interpret a merge conflict message
Resolve a merge conflict while preserving changes to the code
Prerequisites
- JS DOM syntax
- Access to documentation
- Some knowledge of how to run tests using Jest
Setup
- Get into pairs
- Before starting, ensure you create a fork of this repository on Github to use as a pair. Each person in the pair must clone down the fork of this repository from Github and navigate to the project directory
Instructions
1. Start Branching from main
Each pair will need to branch off from main
. Firstly, make sure you both start on the main branch and it’s up to date:
git switch main
git pull origin main
2. Choose a task
As a pair, choose one task from tasks that you will both follow.
3. Follow the task instructions until the end
Choose who will be Person 1 and who will be Person 2 and then follow the instructions in your task’s directory. Once finished, continue the instructions on this page.
Some tasks will ask you to unskip tests, remove the skip before from the appropriate describe block in this case.
4. Test your changes
Use the provided test suite to ensure your app works correctly. Run the tests according to the task’s testing instructions.
5. Raise a pull request
Once you have tested your changes and are satisfied with the changes, commit your changes and push your branch to the remote repository:
git add <files-you-changed>
git commit -m "<description of change>"
git push origin [your-branch-name]
You should raise a pull request on your pair’s fork of this repository.
6. Handling merge conflicts
Once you have both raised your pull requests, choose one Pull Request to review first and then merge it.
Now you will need to handle the second pull request. For this pull request, you should now have a merge conflict in the remaining pull request.
On the branch to be merged run:
git pull origin main
So that you can resolve the changes locally using Git.
Use this guide from GitHub to resolve the conflict using Git.
When you come to resolve the merge conflict, you need to make sure to keep the updates and refactors. Make sure to test that your app still works.
Once you’ve resolved the conflict, you should be ready to merge the second PR. Discuss with your partner whether the tasks assigned have been completed after both merges.
Community Lunch
Every Saturday we cook and eat together. We share our food and our stories. We learn about each other and the world. We build community.
This is everyone’s responsibility, so help with what is needed to make this happen, for example, organising the food, setting up the table, washing up, tidying up, etc. You can do something different every week. You don’t need to be constantly responsible for the same task.
Study Group
Learning Objectives
What are we doing now?
You’re going to use this time to work through coursework. Your cohort will collectively self-organise to work through the coursework together in your own way. Sort yourselves into groups that work for you.
Use this time wisely
You will have study time in almost every class day. Don’t waste it. Use it to:
- work through the coursework
- ask questions and get unblocked
- give and receive code review
- work on your portfolio
- develop your own projects
ποΈ Code waiting for review π
Below are trainee coursework Pull Requests that need to be reviewed by volunteers.
NW6 | Fathi Kahin | Module-Database | E-commerce -API-| Week 4 π
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.
Start a reviewWM5 | AISHA_ATHMAN_LALI | MODULE_DATABASES | WEEK_3 | CYF_E-COMMERCE π
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
This is a PR on CYF E-COMMERCE.
Questions
Are there better ways I could have written the queries?
Start a reviewWM5 | AISHA_ATHMAN_LALI| MODULE_DATABASES | WEEK_2 | BIG-SPENDER π
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
This is a PR for the big-spender database project.
Questions
Is there a better way I could have written the queries?
Start a reviewNW6 | Pedro Ricciardi | Databases Module | [TECH ED] E-Commerce API | Sprint 4 π
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes meet the requirements of this task
Changelist
All routes and tests implemented following the user stories in readme.md:
- As a user, I want to view a list of all products with their prices and supplier names.
- As a user, I want to search for products by name.
- As a user, I want to view a single customer by their ID.
- As a user, I want to create a new customer with their name, address, city, and country.
- As a user, I want to create a new product.
- As a user, I want to create a new product availability with a price and supplier ID, and get an error if the price is not a positive integer or if either the product or supplier ID does not exist.
- As a user, I want to create a new order for a customer with an order date and reference number, and get an error if the customer ID is invalid.
- As a user, I want to update an existing customer’s information with their name, address, city, and country.
- As a user, I want to delete an existing order and all associated order items.
- As a user, I want to delete an existing customer only if they do not have any orders.
- As a user, I want to view all orders with their items for a specific customer, including order references, dates, product names, unit prices, suppliers, and quantities.
Issue
Note
Due to a lack of time, I could not create my own acceptance criteria. I focused on the most important aspect, which is the correct implementation and testing for each route.
Start a reviewNW6 | Rabia Avci | Databases Module | [TECH ED] E-Commerce | Week 3 π
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
I have written SQL queries to retrieve specific data from a database with different tables with relations between them.
Questions
Ask any questions you have for your reviewer.
Start a reviewAfternoon Break
Please feel comfortable and welcome to pray at this time if this is part of your religion.
If you are breastfeeding and would like a private space, please let us know.
Study Group
Learning Objectives
What are we doing now?
You’re going to use this time to work through coursework. Your cohort will collectively self-organise to work through the coursework together in your own way. Sort yourselves into groups that work for you.
Use this time wisely
You will have study time in almost every class day. Don’t waste it. Use it to:
- work through the coursework
- ask questions and get unblocked
- give and receive code review
- work on your portfolio
- develop your own projects
Retro: Start / Stop / Continue
Retro (20 minutes)</span>