Every CYF session begins with an energiser. Usually there’s a rota showing who will lead the energiser. We have some CYF favourite games you can play if you are stuck.

Traffic Jam: re-order the cars to unblock yourself
Telephone: draw the words and write the pictures
Popcorn show and tell: popcorn around the room and show one nearby object or something in your pocket or bag and explain what it means to you.

Learning Objectives

Find 2 suitable jobs applying search filters and techniques looking for a job opportunities on LinkedIn Job Search
Explain the potential advantages and disadvantages of hiring junior developers from the perspective of an Engineering Manager

Introduction

Job hunting is stressful, but you are not alone in this. It’s important to have a community of people around you to whom you can turn if you need help or support. You can do that when it comes to job hunting as well. Look for jobs together and make it less stressful by doing so.

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

Learning Objectives

Explain employers' needs for jobs applications

Preparation

Bring the notes you made during prep.

Introduction

Understanding employers’ needs gives you a different perspective on how to apply for a certain job position and how to prepare for the interview. Seeing their side allows you to assess your compatibility with the company. Adjust your CV and cover letter and prepare for the interview.

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 answer the following scenario questions and compare your answers.
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?
Come to a conclusion
The last 10 minutes should be dedicated to each group presenting their conclusions to the class

A quick break of fifteen minutes so we can all concentrate on the next piece of work.

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
📅 Week 4
📅 Week 1

Workshop Name

Replace this readme with the requirements for your workshop

Learning Objectives

Use the Teach Tech Together guide to construct your objectives
Limit the objectives to 3-5 items
Write objectives you can measure

Requirements

Explain the requirements of the workshop. You might want to talk about goals here. You might want to use formal specifications like Given/When/Then. It’s ok for requirements to be in different formats. We want trainees to learn to interpret requirements in many settings and expressions. Just make sure your workshop is active and not a lecture.

Always write your workshop in a readme.md in a folder with the same name as the workshop. This makes it easy to find and easy to show on the curriculum website.

Acceptance Criteria

I have provided clear success criteria
These might be related to the objectives and the requirements
I have given some simple, clear ways for trainees to evaluate their work
I have run Lighthouse and my Accessibility score is 100

Every Saturday at CYF 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.

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.

LONDON_10 | Yulia - Hospodar | MODULE_DATABASES| Big Spender 🔗

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 review

LONDON_10 | ANDRIUS_ISIN | MODULE_DATABASES| 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 review

London10_Jan_Softa_Module_Databases_Week1-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 review

London 10 | Abubakar-Meigag | SQL WK 4 | E commerce api 🔗

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 review

Glasgow Class 6 - Appolin Semegni Fotso - Module-Databases - 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 review

See more pull requests

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.

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 (20 minutes)

A retro is a chance to reflect on this past sprint. You can do this on a Jamboard (make sure someone clicks “Make a copy” before you start, and you work on that together) or on sticky notes on a wall.

Set a timer for 5 minutes.
Write down as many things as you can think of that you’d like to start, stop, and continue doing next sprint.
Write one point per note and keep it short.
When the timer goes off, one person should set a timer for 1 minute and group the notes into themes.
Next, set a timer for 2 minutes and all vote on the most important themes by adding a dot or a +1 to the note.
Finally, set a timer for 8 minutes and all discuss the top three themes.