Day plan
A scheduled plan of activities for a class day with times and breaks.
This view builds an agenda for class days. We built this because we used to spend a lot of time making spreadsheets every single week and class days could get chaotic and disruptive to learning. Now everyone knows what to do when. Learners can plan things like prayers or medication. Volunteers can see when they’re needed. Everyone can see when they can take a break.
The day plan will create a schedule from the time (in minutes) stored on each block using the time-stamper web component. You can override this time on your day plan by adding a time parameter as shown in the front matter.
This view doesn’t expect any content in the .Content section, but it exists in case you need to put a temporary notice up that everyone will see. It’s for temporary content only. If you just want to add a description of the day, add it to a .Description parameter in the front matter.
We also now can find out who is in class with a simple register. By default, a register will show at the top of the agenda. This register is an auto-detected Netlify form. If you don’t want this, add noRegister=true to the front matter, as this example does.
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.
- 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.
🔗 Placeholder Workshop
Learning Objectives
Workshop Name
Replace this readme with the requirements for your workshop
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
Review
Look back over the objectives of this activity - check you've met them all. If you haven't, make sure you have a plan for how to achieve them - maybe checking in with a volunteer or a fellow trainee could help?Community Lunch
Every Saturday 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
Learning Objectives
Trainees
This is time for you to get help with whatever you need help with.
If you didn’t understand something in the prep, ask about it.
If you were struggling with a backlog exercise, get help with it.
If you weren’t quite sure of something in a workshop, discuss it.
If you don’t have any problems, keep working through the backlog until you need help.
It can be useful to get into groups with others facing the same problem, or working on the same backlog item.
Volunteers
Don’t be scared to approach people and ask what they’re working on - see if you can help them out, or stretch their understanding.
If lots of people have the same problems, maybe you can put together a demonstration or a workshop to help them understand.
If absolutely no one needs help, consider reviewing some PRs using the process and guidelines in the #cyf-code-review-volunteer-team Slack channel canvas.
Breaks
No one can work solidly forever! Make sure to take breaks when you need.
Finished everything?
If you have finished everything in the backlog you can use this time to practice some other skills which will be useful in your future careers. We have some suggestions below:
Pair programming
Pair programming is very common in industry so it’s good to practice it now! Find a partner and choose a problem to work on, for example a Codewars kata. One person will be the “driver” and the other will be the “navigator”. Both of you will use the same laptop to complete the activity.
- The “driver” is the person typing on the keyboard, just thinking about what needs to be written
- The “navigator” reviews what the driver is doing and is thinking about to write next
- Switch between driver and navigator roles after
- Don’t dominate - this is teamwork
Code review
You will receive regular reviews of your work from volunteers when you submit a PR, but how comfortable are you giving a review? Find a partner and give each other feedback on one of the PRs you submitted this week. After you have given your feedback you should consider:
- How did you understand what the goal of the PR is? Did you read the title and description, look at the coursework exercises, etc.
- How did you use the different tabs in the PR:
Conversation,Commits,Files changed. - What made a PR easy or hard to review:
- Where unrelated files/lines changed?
- Was code consistently formatted? Did indentation help or hurt understanding?
- How did you review the code? Did you read top-to-bottom? Did you jump around into and out-of functions? Did you look at tests? Did you clone the code locally and try running it?
Prepare for your next demo
You need to give regular demos to complete the course. Use this time to work on your next one. You could:
- Prepare your slides
- Discuss topics
- Practice presenting
Share resources you have found
The Docs aren’t the only resource available to you! If you have discovered a new book, YouTube channel or anything else you are using to help you learn this is an excellent time to share it with your cohort.
🛎️ 0 PRs available. Open some 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
Learning Objectives
Trainees
This is time for you to get help with whatever you need help with.
If you didn’t understand something in the prep, ask about it.
If you were struggling with a backlog exercise, get help with it.
If you weren’t quite sure of something in a workshop, discuss it.
If you don’t have any problems, keep working through the backlog until you need help.
It can be useful to get into groups with others facing the same problem, or working on the same backlog item.
Volunteers
Don’t be scared to approach people and ask what they’re working on - see if you can help them out, or stretch their understanding.
If lots of people have the same problems, maybe you can put together a demonstration or a workshop to help them understand.
If absolutely no one needs help, consider reviewing some PRs using the process and guidelines in the #cyf-code-review-volunteer-team Slack channel canvas.
Breaks
No one can work solidly forever! Make sure to take breaks when you need.
Finished everything?
If you have finished everything in the backlog you can use this time to practice some other skills which will be useful in your future careers. We have some suggestions below:
Pair programming
Pair programming is very common in industry so it’s good to practice it now! Find a partner and choose a problem to work on, for example a Codewars kata. One person will be the “driver” and the other will be the “navigator”. Both of you will use the same laptop to complete the activity.
- The “driver” is the person typing on the keyboard, just thinking about what needs to be written
- The “navigator” reviews what the driver is doing and is thinking about to write next
- Switch between driver and navigator roles after
- Don’t dominate - this is teamwork
Code review
You will receive regular reviews of your work from volunteers when you submit a PR, but how comfortable are you giving a review? Find a partner and give each other feedback on one of the PRs you submitted this week. After you have given your feedback you should consider:
- How did you understand what the goal of the PR is? Did you read the title and description, look at the coursework exercises, etc.
- How did you use the different tabs in the PR:
Conversation,Commits,Files changed. - What made a PR easy or hard to review:
- Where unrelated files/lines changed?
- Was code consistently formatted? Did indentation help or hurt understanding?
- How did you review the code? Did you read top-to-bottom? Did you jump around into and out-of functions? Did you look at tests? Did you clone the code locally and try running it?
Prepare for your next demo
You need to give regular demos to complete the course. Use this time to work on your next one. You could:
- Prepare your slides
- Discuss topics
- Practice presenting
Share resources you have found
The Docs aren’t the only resource available to you! If you have discovered a new book, YouTube channel or anything else you are using to help you learn this is an excellent time to share it with your cohort.
Retro: Start / Stop / Continue
🕹️Retro (20 minutes)
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.
- Set a timer for 5 minutes. There’s one on the RetroTool too.
- 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.