πŸ§‘πŸ½β€πŸ€β€πŸ§‘πŸ½ day-plan

Energiser

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.

  1. Traffic Jam: re-order the cars to unblock yourself
  2. Telephone: draw the words and write the pictures
  3. 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.

JD Hunting and Mock Interview πŸ”—

Learning Objectives

Preparation

Bring the job description from prep to class.

Introduction

Hiring managers may sort through hundreds of resumes for a single job, meaning they often scan to find the most relevant details. The best way to get noticed as a candidate is to tailor your CV to the employer’s job description.

Review a job description for a software engineer role

🎯 Goal: Learn how to identify key elements of the job description that can be used to highlight relevant skills and experiences in your resume. (30 minutes)

Form groups of 4 or 5 people. Read the job description you read on the prep and together do the following activities:

1. Review the job description and discuss (20 minutes):Β 

  • Understand employers’ wants and the qualifications required to perform the job.Β 
  • Read its description and write down/highlight any significant keywords related to skills. These may be unique to the job or that repeat throughout the posting.Β 
  • Take note of specific requirements - necessary education or training and years of experience.
  • Look at the order of the responsibilities listed, as those mentioned first may be more of a priority for the employer.Β 
  • Mirror the employer’s priorities when organising your resume - the first items they mention should be some of the first items you each mention on your CV.

2. Write a resume summary (10 minutes):Β 

  • Review your general CV and start tailoring it to their needs - focus only on the summary.
  • It’s at the top of your resume, so it is one of the first things a hiring manager sees. Use it to showcase your most relevant skills and accomplishments based on the keywords you highlighted.Β 
  • Include the job title to which you are applying, proving that this is a personalised CV.

Mock interview: Competency-based interviews using the job description

🎯 Goal: Get prepared and comfortable with competency-based interviews. (30 minutes)

Trainees should pair up and practice interviewing each other. Use the job posting from the previous exercise and the notes you took to complete the following activity:

  • One individual will take the role of the interviewer, and the other the role of the candidate.

  • You both should be very familiar with the job posting, if not, review it carefully.

  • Make sure to cover these stages during the interview:

    • Introductions

    • Interviewer: go over the candidate’s CV, and ask at least 5 questions regarding the candidate’s skills and experience as well as the information found in the CV’s summary. Try using the format followed by the questions below and also feel free to use them:

      • Tell me about a time when you did more than what was expected.
      • Tell me about a time when you received harsh feedback.
      • Tell me about a time when you had to deliver results within a tight deadline.
      • Walk me through a time when requirements were not clear by the time development had to start. What did you do?
      • Talk me through one of the projects that you’re proud of.
      • What is the most (technically) challenging task that you’ve encountered?
    • The candidate should use the STAR method to answer these questions. The interviewer should allow the candidate to ask questions at the end. Remember to always keep in mind what you learned from the job description!Β 

  • Finally, discuss with each other how the interview went and then swap roles.

Morning Break

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

Placeholder Workshop πŸ”—

Workshop Name

Replace this readme with the requirements for your workshop

Learning Objectives

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

Community Lunch

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.

Study Group

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

Afternoon 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

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)

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.

  1. Set a timer for 5 minutes.
  2. Write down as many things as you can think of that you’d like to start, stop, and continue doing next sprint.
  3. Write one point per note and keep it short.
  4. When the timer goes off, one person should set a timer for 1 minute and group the notes into themes.
  5. 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.
  6. Finally, set a timer for 8 minutes and all discuss the top three themes.