🧑🏽‍🤝‍🧑🏽 day-plan

🔖
  1. Energiser
  2. Welcome to Code Your Future 📼
  3. Goals and expectations
  4. Learning as Community
  5. Availability
  6. Google Sheet for pairing
  7. lunch
  8. Git workshop
  9. Next steps
  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.

SDC Goals and expectations 🔗

Learning Objectives

Preparation

Review the presentation before the class. Make sure a Word Cloud app is available. Everyone has to have their computers with internet and access to Slack.

Introduction

The Software Development Course of Code Your Future (CYF) has a particular goal: you get a job in tech! To achieve this, we have expectations of every trainee, and you will also have expectations about CYF. So we are now doing some exercises to align them.

Goals and expectations presentation and exercise

🎯 Goal: Agree with the goals and expectations of the Code Your Future Software Development Course (80 minutes)

Open this presentation and follow the slides.

Learning as a community 🏫

Learning Objectives

At Code Your Future, we learn as a community.

In this session, we’re going to describe how we harness our community to learn together.

Resources

The facilitator will use this presentation 👉 Learning as a community presentation

Preparation

  • Facilitator: Review this presentation before class.
  • Facilitator: Ensure everyone can access the Miro board presentation.
  • Facilitator: Split the class into groups of no more than 5.
  • Facilitator: Make sure every group has access to a laptop.
  • Facilitator: Make sure every group has access to a piece of paper and pen

Introduction

The facilitator will use the Miro board presentation to guide trainees and volunteers on a discussion about how we learn together as a community.

General Weekly Availability 🔗

Learning Objectives

Preparation

Copy this General Weekly Availability
Spreadsheet
for your cohort and share it with everyone. If no one has done this yet, take the initiative and do it.

  • Someone in your cohort needs to bookmark this spreadsheet on your cohort channel in Slack.
  • Someone in your cohort also needs to do a brief post on Slack linking people to this spreadsheet.

This is one file for the cohort, not one per person.

Introduction

Sharing our general availability means that you and your peers can identify roughly who is available and when.

Why is this important?

Because you can then identify pairs and groups that can help each other, and helping each other is good for the community and your relationship, and makes us feel good about ourselves.

Add your general availability

🎯 Goal: Share your weekly availability with your peers (10 minutes)

  1. Open to the cohort’s General Weekly Availability spreadsheet.
  2. Add your name to the next line that is available in column A.
  3. Use the same colour as the example to identify when you are available.
  4. Leave non-available slots in grey. (Examples of Non-available slots: school pick-up/drop-off times, eating times, individual studying, part-time job, resting time, exercising times, mental health focus, etc. You do not have to detail what you are doing, but consider these when adding your availability)

Tip: Copy and paste one of the current coloured cells to your cell, this way you don’t have to figure out what’s the correct colour to use.

Identify pairs per week 🔗

Learning Objectives

Preparation

One trainee must volunteer to create a new tab on the existing Google sheet.

Introduction

Looking into the General Weekly Availability that you filled in before the induction, we will use each other’s availability and identify the best pairs to work together.

To work together, you must be available at similar times - not for the whole week, but for the number of hours needed for prep or coursework in pairs.

PS: It’s important to pair with different people in your cohort. There is more diversity, there better your professional competencies will evolve.

Creating pairs for the coursework

🎯 Goal: Update the shared file in which trainees can organise teamwork rotas (5 minutes)

On the Fundamentals section of the course, you should have created a rota spreadsheet of the form “XXX X Rota”, replacing the “X”’s with the name of your region and cohort number. For example, “NW 6 Rota” for the cohort in North West and cohort 6.
Double check this rota spreadsheet is bookmarked to your cohort channel and post a link to the spreadsheet on Slack

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

  • Create a new tab on the spreadsheet called “Pairs Induction”
  • The new tab must have two columns, one with the title “Pair 1” and another for “Pair 2.”
  • Post a message on the cohort Slack with the shared spreadsheet and the instructions on what to do (see below)

This tab will be the rota of the coursework.

Create pairs considering trainees' availability

🎯 Goal: Connect the people’s availability defining the most effective pairs to work together (10 minutes)

Multiple tasks need to be done to make this exercise happen, but not all of them should be done by one person:

  1. How many hours of coursework has to be done in pairs? Double check the issues that have a 🫱🏿‍🫲🏽 Pairs label on this module’s backlog
  2. Open the “General Weekly Availability” spreadsheet.
  3. Identify who could pair together, considering their availability.
  4. Someone should add these pairs to the other spreadsheet (exercise 1).

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.

Git workshop 🔗

Part 1

Setup

  • Break out into groups of 5/6 ( depending on volunteer and trainee numbers )
  • Use these instructions as a guide to check your understanding, resolve misconceptions and develop your understanding

This workshop starts with a recap based on this week’s prep material…

Exploring GitHub repositories

Recap activity 🕹️

  • Trainees do this section in pairs
  • ⏲️ 10 mins

Let’s recap some of the things from earlier in the week.

Visit the following repository on GitHub: https://github.com/CodeYourFuture/cyf-demo-repo

Answer the following questions:

a) How many commits are there in the cyf-demo-repo project?

b) Who committed on Oct 31, 2020?

c) What changes did illictonion make in the commit titled “Revert changes accidentally pushed in the past”?

d) How many files were added in the first commit? What were the names of the files?

e) What is the hash for the first commit in the history?

f) What is Claire Bickley’s favourite food?

🧵🗣️ group discussion

  • Group discussion
  • ⏲️ 10 mins
  • A volunteer will need to facilitate this section

A volunteer can facilitate this group discussion by going through the questions above and asking pairs for their feedback. If pairs are unsure / not quite accurate then spend a small amount of time addressing misconceptions.
Remember to ask around for feedback.

Creating a fork 🍴

🕹️ Recap activity

  • Trainees do this section in pairs
  • ⏲️ 5 mins

Use the guidelines from the prep section of this week to create a fork.

  1. On one person’s computer, fork this repo: https://github.com/CodeYourFuture/cyf-demo-repo
  2. 📝 Double-check the URL of your forked repo. How can you tell the fork was successfully created?

Group discussion/demo 🧵 🗣️

  • Groups discussion
  • ⏲️ 5 mins
  • A volunteer will need to facilitate this section

A volunteer will need to navigate and let the group guide them in creating a fork as per the steps in the previous section.

🌀 Cloning a repository

🕹️ Recap activity

  • Trainees do this section in pairs
  • ⏲️ 5 mins

📋 Check your understanding

Before continuing, try answering the following:

❓ what is the difference between a fork and a clone.

Remember to check your answer before continuing.

  1. Clone your fork of cyf-demo-repo to your local machine.
  2. Open this local repository using VSCode.
  3. Use pwd in your terminal to check you’re in the right place.

Group discussion/demo 🧵 🗣️

  • Group discussion/demo
  • ⏲️ 5 mins
  • A volunteer will need to facilitate this section

A volunteer will need to navigate and let the group guide them in following through the steps in the previous recap activity.

🌳 Creating a branch

🕹️ Recap activity

  • Trainees do this section in pairs
  • ⏲️ 10 mins

Next, create a local branch called week-1-workshop

Group discussion/demo 🧵 🗣️

  • Group discussion/demo
  • ⏲️ 10 mins
  • A volunteer will need to facilitate this section

Take a break for 10 mins… 🍫

Part 2 - New skills 🧰 - Committing and pushing 📸

Learning objectives

🕹️ Activity - Figure it out 🔍

🎯 Goal: Make some local changes and create a local commit on our branch.

  • Do this section in pairs
  • ⏲️ 15 mins

Follow these instructions carefully.

Our Git timeline starts off with some commits like this:

main-and-feature-in-sync

We’re going to figure out how to

  • make local changes and commit them to our branch “week-1-workshop”,

so our history looks something like this:

feature-branch-ahead

where the most recent commits contain our changes.

To create a commit, we can use the following steps (explained more below):

  1. Make a change to a file
  2. View the local changes
  3. Stage the changes
  4. Creating the commit

🗄️ 1. Make a change to a file

  1. Open up your local repo cyf-demo-repo in VSCode.
  2. Go to the Explorer section of VSCode ( look for a 🔍 icon ).
  3. Find file.txt and edit the file with the answer to the questions.
  4. Remember to save the changes to file.txt.

Tip:

  • You can use Cmd + S on a Mac to save changes to a file in VSCode.
  • You can use Ctrl + S on a Linux OS to save changes to a file in VSCode.

🔬 2. View the local changes

We want to view the changes we’ve just made to our working directory.

  1. Locate the Source Control tab in VSCode.
    source-control-tab
  2. Go to the Changes section and click on the file you changed - this should now show the changes for the file.
  3. Try editing the file again in the Explorer tab and check to see the update is visible in the Source Control panel

🟢 3. Stage the changes

We need to tell Git which changes we want to be part of our next commit.

Each commit is a checkpoint we’ve decided to save. When making a commit, we can decide to not include all of our changes in the checkpoint, but just include some of them.

We choose which changes we want to include in a commit by staging our changes.

In the Source Control tab again…

  1. Go to the file file.txt and click on the +.

👓 Notice what happens when you carry out step 1.

  1. View the Staged Changes area in your Source Control panel.

📸 4. Create the commit

Once we’ve staged our changes, then we can commit these changes.

Before we do, we should make sure we’re on the correct branch. Check that you’re on the week-1-workshop branch.

Your VSCode window should look like this:

check-current-branch-week-1-workshop

and not like this:

check-current-branch-is-main

If you’re sure you’re on the right branch:

  1. Enter a commit message describing briefly what you did in your commit.
  2. Click Commit to create the Git commit.

📝 Now figure out how many commits you have on your local machine.

🧠 Explain what you think would have happened if you didn’t stage anything in your working directory when you made your commit.

When you’re finished…

❗ Once you’ve completed this commit, swap roles in your pair.
Choose another file and then go through the steps in the Creating a commit section

Group discussion/demo 🧵 🗣️

  • Group discussion/demo
  • ⏲️ 10 mins
  • A volunteer will need to facilitate this section

A volunteer will now need to navigate with directions from the group. Go through the git commit steps together.
Also use this time for clarifying questions.

🫸 Pushing

🎯 Goal: Push a branch to a remote repository

🕹️ Activity - Figure it out 🔍

  • Trainees work in pairs
  • ⏲️ 5 mins

After committing your work on your machine, you’ll have a local branch that looks like this

---
title: cyf-demo-repo
---
gitGraph
   commit
   commit
   branch "week-1-workshop"
   commit
   commit

📋 Double-check you’ve been committing to your branch week-1-workshop branch and not your main branch.

However, our remote fork only has a main branch:

---
title: cyf-demo-repo
---
gitGraph
   commit
   commit

In other words, we have not added our local branch onto the remote fork on GitHub.

To do this, we must push our branch onto GitHub.

push means adding local work to a remote GitHub repository.

🔍 Figure out how to push your local branch to the GitHub repository using the Source Control interface in VSCode.
🔍 Figure out how to check the week-1-workshop branch is on the remote fork.

Group discussion

  • Group discussion/demo
  • ⏲️ 5 mins
  • A volunteer will need to facilitate this section

A volunteer will need to navigate and let the group guide them in following through the steps in the previous recap activity.

🧵 Tying things up

Now is some time to wrap up and try and discuss some of the key concepts from this week.

🗣️ Discussion in pairs

  • Trainees discuss in pairs
  • ⏲️ 10 mins

In your pair, discuss the following questions/tasks:

  1. what is a commit? explain why need to make commits when we’re developing a project?
  2. explain why we store repositories on GitHub
  3. describe the purpose of VSCode
  4. explain the difference between Git and GitHub
  5. explain why developers use branches
  6. explain the difference between a fork and a clone?
  7. what does the branch name origin/main mean instead of just main
  8. Check out the following git repository diagram below:

How many commits are in common between week-1-feature and main?

---
title: cyf-demo-repo
---
gitGraph
   commit
   commit
   commit
   branch "week-1-feature"
   commit
   commit

🗣️ Group discussion

  • Discuss the questions together as a group. Go round and get feedback from each person in the group.

Next steps 👣

Learning Objectives

For trainees

In this section, we’re going to go through a set of questions/tasks to clarify what we’re going to do in the next part of the course.

Get into pairs with somebody you’ve not paired up with today and try figuring out the answers/solutions to the following questions/tasks:

  1. Using the curriculum, locate the page setup page for the upcoming module.
  2. Using the curriculum website, locate the page with the prep material for the first week of the next module
  3. List the things you need to install ( if anything ) for the upcoming module.
  4. Check you can find the backlog page for the Induction sprint. Double check you’ve copied all the issues from the backlog over to your Course Planner.
  5. Identify all the issues with 🔑 icon that are marked as Priority. What does the Priority icon 🔑 mean?
  6. Go to your group Slack channel and start a thread 🧵 outlining times you’re free to meet up to discuss the prep work during the week
  7. Which day ⏰ should you start the prep work for the upcoming HTML module?
  8. Experiment with your project planner: can you filter by Size, Week 1, Tech ed, PD etc.?

For volunteers

  1. Locate the classroom planning board for your region ( if one exists )
  2. Locate the day-plan for the next week/module
  3. Check the instructions and links on the Priority 🔑 issues for the upcoming week ( both Tech Ed and PD )
  4. In the day-plan for the upcoming week identify the instructions for any workshops and visit the repository containing that readme. Check the instructions make sense.

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.