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.
- 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.
Progress Check-in 🔗
Link to the coursework
https://curriculum.codeyourfuture.io/cloud/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 deploy infrastructure as code 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 track.
To join the Cloud employment pool, you will need to successfully complete this track. How will you as a cohort meet the success criteria? Discuss it in your 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 demo progress
🙅🏿 bad strategies
- opening empty PRs or pretending to do work
- 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 the penultimate sprint of your module you will need a representative to report to the organisation. Post your decision on Slack. 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 on target to complete this 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 1
- 📅 Week 4
Group Discussion
- 🎙️ Nominate a facilitator (trainee or volunteer)
- ⏰ Nominate a timekeeper (trainee or volunteer)
🎙️ Facilitator
Your role is make sure that everybody gets the chance to speak. Start the discussion by asking the group:
- What are the key ideas in this sprint that you want to discuss?
- What’s the biggest blocker you have right now?
Invite the group to spend ⏰ 5 minutes writing down key ideas and blockers on a board.
Use what works for your team
Vote on the focus
Give the group ⏰ 2 minutes to vote on what to discuss. +1 on the question is fine.
🐇 Begin with the most popular topic
Give the group ⏰ 10 minutes to discuss the most popular topic. Move the discussion on if it gets stuck. If the group is struggling to come up with ideas, ask them to think about:
- What documentation relates to this topic?
- What other problem is this problem like, that you have met before?
- Is there another way to solve this problem?
🕳️ Move on to the next topic
Keep the discussion moving and help the group to stay on track. Your job is to prevent “rabbit holing” on one topic.
⏰ Timekeeper
Keep the discussion on track by keeping an eye on the time. Use a stopwatch and give the group a 30 second warning before the end of the session.
-
00:00 - 02:00: Nominate a facilitator and timekeeper -
02:00 - 07:00: Write down key ideas and blockers -
07:00 - 10:00: Vote on the focus -
10:00 - 20:00: Topic 1 -
20:00 - 30:00: Topic 2 -
30:00 - 40:00: Topic 3 -
40:00 - 50:00: Topic 4 -
50:00 - 60:00: Topic 5
Morning Break
A quick break of fifteen minutes so we can all concentrate on the next piece of work.
Demo
At CYF we expect you to demo your work to the class. You must have many opportunities to practice how to clearly and simply explain your work to others. This is really important both for interviews and for getting promoted later on.
⏰ Timekeeper
The timekeeper will keep the groups on track.
Split into groups of no more than 5 people. Each person will have 2 minutes to demo their work to the group. After the demo, the group will give feedback for 10 minutes. Then the next person will demo their work.
🧑🏼🎓 Trainees
1. Demo
You will demo your work to the group. You will have 2 minutes to explain what you did and why. It’s ok to show broken code or code that doesn’t work yet. Just make sure your demo is interesting.
2. Feedback
After the demo, the group will give you feedback for up to 10 minutes. It’s smart to suggest what kind of feedback you want by asking some “generative” questions. For example:
- I wasn’t sure if it makes sense to try X. What do you think?
- I liked the way I did X, but I know there are other approaches, what did you do?
- I found X really confusing, did anyone else have the same problem?
💡 Tips:
- Practice your demo before class.
- Keep it simple. Don’t try to show everything you did. Just show one interesting thing.
- Keep it short. Two minutes is enough.
- Explain what you did and why.
- Show your code.
- Ask for feedback.
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
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.
Experts AMA
🧑🏼🎓 Trainees
(If you don’t have a guest expert, do study group instead.)
Share your questions in a Slack thread by Friday 10am. This is an
🦸🏾 Expert(s)
Read over the questions and prepare your answers before class if possible.
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.
- 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.