๐Ÿง‘๐Ÿฝโ€๐Ÿคโ€๐Ÿง‘๐Ÿฝ day-plan

โœ๐Ÿฝ Register

Energiser

Every session begins with an energiser. Usually there’s a rota showing who will lead the energiser. We have some 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.

Roles in the tech industry

Learning Objectives

Preparation

Prep work must have been completed.
Trainee must have their list of roles available.

Introduction

Tech teams have many different roles because each role contributes to the overall success of the team and the development of a product or solution.

Letโ€™s talk about roles in tech

๐ŸŽฏ Goal: Demonstrate your knowledge about the roles in tech (30 minutes)

  1. In your groups of 4-5, one trainee volunteers to briefly present a role and another trainee to be the timekeeper
  2. The trainee has 1 minute to say the name of the role they would like to present, what this role does, and why it is essential.
  3. Everyone in the same group can ask 1 question and/or add 1 important piece of information to what was shared (2 minutes)
  4. The trainee chooses someone else in the group to present a different role and chooses a new timekeeper.ย 
  5. Repeat steps 2, 3 and 4 until no one has a different role to talk about OR you run out of time.

Roles complement each other

๐ŸŽฏ Goal: Use the different roles to solve a problem (20 minutes)

  1. Separate the class in groups of 5. Each person takes up one of these roles:

    • Product Owner
    • Scrum Master
    • Developer
    • Tester
    • UI/UX Designer
  2. The group should share their understanding about what each role is responsible for and how they contribute to the team.

  3. Each team has 10 minutes to find a solution to one of the below problems:

    • The main page of our product is down
    • The Director asked for a new feature in our app. They would like it to be done in 2 weeks.
    • The release we did yesterday is not working.
    • We have a brainstorming session about the next 3 features for our webapp.
  4. Define in 1 phrase what was the main learning of the group. The Tester will present back to the wider group.

Share your learning

๐ŸŽฏ Goal: Recognise what your learned in this session (10 minutes)

  1. The Tester of each team will tell the wider group the phrase about the main learning

Morning Break

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

Playing computer ๐Ÿ”—

Learning Objectives

๐ŸŽฎ Playing computer

๐Ÿ’ก Purpose

This workshop is designed to develop your understanding of playing computer. Playing computer means simulating how the computer executes our code. We “step through” the code, line by line, and work out what the computer does when it follows each instruction. Once we develop a better intuition for how our code runs it becomes easier to debug code, reason about it and write more complex programs.

During this session, you will:

Resources

You will need:

  • A piece of paper saying “memory” - where we store variables
  • A piece of paper saying “console” - where we print to the console
  • Some example programs like the ones here ๐Ÿ‘‰ Playing computer workshop
  • [Optional] A set of functions in envelopes ( this isn’t essential but a nice thing to have to reinforce the idea of instructions being “opened” up when a function is called )

( If you don’t have any paper/pens you can create plain text files for “memory” and “console” and write your work out in there! )

๐Ÿงฐ Setup

  1. Split up into groups of 2 or 3 at most.
  2. Start with the first example ( e.g. example-0.js )
  3. Each person will need to take responsibility for a particular frame. One person will be assigned the role of global frame, for example. If there are other function declarations, someone else will “play” that frame too.

๐Ÿฒ Warm-up

Start with the program in example-0.js. There is only one frame to play here - the global frame, as there are no other function declarations and calls in the file.

  • One person will “play” the Global frame
  • This person will step through the code in example-0.js using the rules of execution below.
  • Other members of the group can watch and provide support as they go through the code.
  • Once you’ve finished you can change some of the values/variables and then someone else can play the global frame too
  • โ— After you’ve finished playing computer with the program, you should check your memory sheet and console sheet by using the Python visualiser

Rules of execution

Rule 0

Only one person can be sat at the table at a time ( where we write to the memory sheet/console sheet)

Rule 1

Start reading code from top to bottom, one line at a time

Rule 2

Write and update variables in memory as you go along
For example, if the program says:

let a = 32;

You would write down “a : 32” on your piece of paper saying “memory”

Rule 3

If a function is called the person “playing” this frame takes the seat and we jump to the instructions in that function, using Rules 1 and 2.

Rule 4

When a function returns or finishes execution this person leaves their seat and the previous person sits down again.

You may need to play computer like this a few times before you get used to this way of thinking about the code. Make sure you swap roles so others get the chance to play a particular frame.

๐Ÿ“ Check your understanding

Doing this activity by hand is a great way to start thinking about how your code runs.
Once you’ve gone through this activity and played computer with pen and paper, you can check what you’ve got on your piece of paper by playing computer with the Python Tutor code visualiser

Lunch

Take your lunch break and be back in an hour!

MWT Workshop

Most Wanted Topics ๐Ÿ”ฅ

Great news! After gathering your feedback from past retros, weโ€™re officially incorporating a new element into the curriculum!

Your instructor will soon share a link to the RetroTool board. There, you can post stickers on topics youโ€™re finding challenging. The topic with the most votes will be the focus of our workshop! If time allows, weโ€™ll dive into the 2nd, 3rd and even more voted topics.

Donโ€™t forget to take short break ๐Ÿง˜โ€โ™‚๏ธ during the session happy coding!

Use this time wisely ๐ŸŽฏ

To make the most out of this workshop and ensure you’re getting the best value, here are a few tips to keep in mind that will help you stay focused, collaborate effectively, and leave with actionable insights:

  • Come Prepared: Come Prepared beforehand and gather your thoughts on the specific areas where you need clarification or support. This ensures you ask targeted questions during the workshop.

  • Engage Actively: Donโ€™t just observe ask questions, share your experiences, and participate in discussions. Workshops are most valuable when everyone collaborates.

  • Collaborate with Peers: If you see a fellow participant struggling with a topic youโ€™re comfortable with, offer your help. Peer learning enhances the overall experience for everyone.

  • Apply Immediately: After the workshop, try to implement what youโ€™ve learned in your course work or personal projects. Practical application reinforces your learning.

  • Follow-Up: If a topic wasnโ€™t fully covered or you still have doubts, follow up with your instructor or peers after the session. This ensures no questions are left unanswered.

๐Ÿ›Ž๏ธ Code waiting for review ๐Ÿ”—

Below are trainee coursework Pull Requests that need to be reviewed by volunteers.

| Deborah GAMEDZE| Module1 | Week3 ๐Ÿ”—

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
dg | Deborah Gamedze |Module-Js1 | Week4 ๐Ÿ”—

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

Take your short afternoon break and be back in 15 minutes!

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.

| Deborah GAMEDZE| Module1 | Week3 ๐Ÿ”—

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
dg | Deborah Gamedze |Module-Js1 | Week4 ๐Ÿ”—

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

Retro: Start / Stop / Continue

  Retro (20 minutes)</span>

A retro is a chance to reflect. You can do this on RetroTool (create a free anonymous retro and share the link with the class) or on sticky notes on a wall.

  1. Set a timer for 5 minutes. There’s one on the RetroTool too.
  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.