🧑🏽‍🤝‍🧑🏽 day-plan

🔖
  1. Energiser
  2. Devtools Workshop
  3. lunch
  4. Study Group
  5. Code Review
  6. Afternoon break
  7. Transferable skills
  8. Feedback
  9. Pairs for next week
  10. Retro

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.

Devtools Workshop 🔗

Inspector Gadget

Prep

For this workshop you will need:

You’ve already used a little bit of Devtools in ITD when you used Lighthouse to audit your code. But there’s much much more! Devtools is an entire IDE (Integrated Development Environment) running inside your browser and it has hundreds of ways to inspect, test, and develop your code.

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
NW6 | Fikret Ellek | HTML-CSS Module | Multipage Clone | 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

I have created portfolio page. started from mobile and then added desktop media query at 540px width

Questions

Ask any questions you have for your reviewer.

Start a review
Nw6|Ayman model-html-css 🔗

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
NW6| Fidaa Bashir| Cake co| 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

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.

Transferable skills 🔗

Learning Objectives

Preparation

Must have done the prep work

Introduction

In this session we will talk about our transferable skills.

Brainstorming about transferable skills

🎯 Goal: To brainstorm about transferable skills. (15 minutes)

In your pairs, ask each other the following questions about your texts

  • What would your strengths be as a professional?
  • How did your skills help you achieve your goals in your previous education/job?
  • What skills do you use to adapt new situations?
  • What skills do you use during this course?

Giving each other feedback

🎯 Goal: To practice providing feedback. (15 minutes)

  1. Pair up with another peer.
  2. Share your text with this person.
  3. Read your pair’s text.
  4. Give a feedback on their transferrable skill.

Share how you will contribute to the cohort

🎯 Goal: Recognise how each trainee will contribute to the cohort (5 minutes)

No one is good at everything however everyone is good at something. That is why we work in teams - to combine our strengths.

Identify a skill or strength that you have that will positively contribute to the cohort.

  • Everyone to share 1 skill (no explanation needed, no discussion needed, keep it short)

Feedback 🔗

Learning Objectives

Preparation

Must have done the prep work

Work with your pair.

You will play the three situations once.

Introduction

Take turns to play the roles below and answer the following questions for each situation:

  • Was feedback positive or negative?
  • Was the way it was communicated appropriate? Why?
  • How would you improve it?
  • What would your reaction be after receiving such feedback?
  • Were people in the right mindset to give and receive feedback?

Role play these scenarios

🎯 Goal: To explore positive and negative feedback. (15 minutes)

Situation 1: Tom asked Katie for help on the code he was writing.
  • Tom: “Hi Katie, would you mind spending a few minutes looking at this function I am working on? I can’t seem to find what’s wrong with the code.”
  • Katie: “I am extremely busy and stressed with a deadline, but let me have a look.”
  • Tom: “Here is the function. Do you see anything wrong with it?”
  • Katie: (after looking at the code for some time) “Seriously? How could you miss this? You are missing an End statement. You need to be more careful when writing code so you only ask for help for things that are not this obvious.”
  • Katie walks away.
Situation 2: Patricia stops by Carla’s desk.
  • Patricia: “Hi Carla. Just wanted to let you know how much I appreciate the work you did in the last project and I hope we get to work together again”
  • Carla: “Oh Thank You! You made my day!”
Situation 3: Team members in a project retrospective meeting discuss things they did well and things that need improvement.
  • Jessica: “I think overall the project went well but developers were constantly waiting for Karen to finish testing their code before they could deploy to Production. She was overwhelmed with the amount of work on her plate”
  • Karen: “Yes, I felt bad for blocking deployments but I cannot give my approval until I have completed testing the code.”
  • Jessica: “Did you ask for help? We can have developers take the role of QA tester when you are overwhelmed.”
  • Karen: “No, I did not ask for help. I did not think of this as an option. I will start implementing this strategy going forward”

Pairs for next week 🔗

Learning Objectives

Preparation

  • Open the existent Google Sheet for your cohort
  • Use the General Availability Spreadsheet

Introduction

Working with different people allows you to learn diverse things by talking, discussing, listening and working together.

So make sure you are pairing with different people with similar availability.

Create pairs for next week

🎯 Goal: Identify the new pair to work with for this week (5 minutes)

  • One trainee to update the Google sheet “XXX X Rota” on the cohort drive

    • The new tab must have two columns, one with the title “Pair 1” and another for “Pair 2.”
    • The name of the tab should be “Pairs HTML S1"
    • Check people’s availability and assign pairs
    • Post a message on the cohort Slack with the shared spreadsheet

    This tab will be the rota of the coursework.

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.