👣 Steps

If you haven’t done so already, choose someone (volunteer or trainee) to be the facilitator for this morning orientation block. Choose another to be the timekeeper.

This sprint you have read about programming language concepts in How Computers Really Work.

In groups of no more than 6, have a discussion trying to answer the following questions. Everyone in the group should contribute at least one idea to each discussion topic.

Volunteers should avoid speaking as much as possible - the trainees should be answering these questions as much as possible.

Topic: variables and memory

What is main memory? What is a variable?

How does a variable relate to a memory location?

How is a string laid out in memory?

How does main memory (RAM) relate to secondary storage (a hard drive)? Why do we have both?

Topic: CPUs

What does a CPU do?

What benefits are there to having multiple CPU cores?

Topic: Functions

What happens when you call a function? Can you draw this?

What are parameters/arguments? Return values? Scope?

How does “the next line of code to run” move around when using functions?

Topic: Classes

What is a class? How would you explain a class to someone who doesn’t know what code is?

Make sure to discuss at least two real-world examples.

Make sure you describe the relationship between a class and an instance of a class (often called an object).

Topic: Objects

Instances of classes are often called objects.

This kind of “object” is similar to, but slightly different from what we call an “object” in JavaScript.

What are the similarities and differences between these two meanings of the word object?

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

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

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. Set: a game of visual perception
4. Mastermind: a game of deduction
5. Sudoku: a game of logic
6. Mancala: a game of strategy

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.

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 randomly 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 5 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 5 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?
• I wasn’t sure if I explained what an X was very clearly, how could I have explained it better?

💡 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.

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

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.

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