💡 Purpose

Currently, you’re using the 🎮 VSCode interface to interact with Git. However, we can often use different interfaces to carry out the same tasks.

In this workshop, you will use the Git CLI - Command Line Interface to interact with Git. In addition, you will:

• Consolidate existing knowledge of Git
• Develop your mental model of the working tree and the staging area
• Learn to use basic Git CLI commands

📝 Learning objectives

During this session, with the Git CLI, you will:

• Research essential git commands commands for creating a commit
• Inspect the status of the working directory and staging area
• Checkout a new branch
• Add changes from the working tree to the staging area
• Commit changes from the staging area

🧰 Setup

Work in pairs:

• Assign one person to be driver (the driver will control the keyboard and do the typing)
• Assign another person to be navigator (the navigator will read out the questions and explain how to tackle the problems).

The driver must ensure they have a clone of this repo on their local machine.

📜 Instructions

Follow the link to the readmes for further instructions:

Head to the Starting point for more instructions

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

📝 Learning objectives

During this session, you will:

• Play computer with a few short programs to work out what happens when they run
• Keep track of your place in a running program using frames
• Describe what happens when a function is called during runtime
• Check your understanding using an application like the Python visualiser

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

JS1 week 1 evaluation

🎓 Instructions

This workshop aims to check your understanding.

Each task will explain whether or not you should run the code.

• For each task, you can use JS1 week 1 prep to help you with the questions.
• You can also use documentation to look up any functions that are unfamiliar.
• Don’t use ChatGPT or any other AI tool to help you.

🧰 Setup

👉 This workshop lives on CYF-Workshops on GitHub

1. Get into pairs or groups of up to three.
2. Make sure you have a clone of the CYF-Workshops repository on your local machine

Each file contains a different problem at a particular level. Start this project at Level 100 and then move up through the levels: level 200, 300 …

🏁 Go to Level 100