BeyondChess™ CS Bridge
Week 2: What Changes vs. What Stays
Body Concept: Firmware (constants) vs. Flow (variables) — the physics of a body
Name:
Date:
Coach Lamont says: "Your pawn's position? That changes every move — that's a variable, the flow of the body. The rule that pawns can't go backward? That NEVER changes — that's a constant, the firmware. Every body has things that flow (change) and things that are fixed (stay). You already know the difference. Now let's see how computers use the same idea."
Part 1: The Big Idea — Every Body Has Flow and Firmware
In chess AND in code, some things change (flow/variables) and some things stay the same (firmware/constants):
| Chess (The Body) | Flow or Firmware? | Code Example |
|---|
| A pawn's position on the board | Flow / Variable (changes every move) | let pawnPosition = "e4" |
| The rule: pawns move forward only | Firmware / Constant (never changes) | const PAWN_DIRECTION = "forward" |
| Your current chess rating | Flow / Variable (goes up and down) | let playerRating = 800 |
| The board has 64 cells | Firmware / Constant (always 64) | const BOARD_SIZE = 64 |
| Which piece is on e4 | Flow / Variable (could be anything) | let pieceOnE4 = "Knight" |
| The King is the still center | Firmware / Constant (always true) | const KING_IS_VITAL = true |
Part 2: CS Vocabulary (The Physics of Bodies)
- Variable (Flow)
- A named container that holds data which can change. Like a cell on the board — the name stays the same but the piece on it changes. In code:
let score = 0
- CHIMERA: variables are the MEDIUM flowing through the body. The flow changes. The channels stay.
- Constant (Firmware)
- A named container that holds data which never changes. Once set, it's locked forever. Like the rule "pawns go forward." In code:
const BOARD_SIZE = 64
- CHIMERA: constants are the body's firmware. The compiled rules that define the body's physics. Change them and the body breaks.
- Data Type
- The KIND of information stored: numbers (42), text ("hello"), or true/false (boolean). Every variable and constant has a type — just like every piece has a type (pawn, knight, etc.).
- Assignment
- Putting a value into a variable. Like placing a piece on a cell:
score = 100
- Update
- Changing a variable's value. Like moving a pawn to a new cell:
score = score + 10
Part 3: See the Code — A Chess Game Has Firmware and Flow
const BOARD_SIZE = 64
const PAWN_VALUE = 1
const KING_VALUE = "priceless"
const PAWNS_PER_PLAYER = 8
let pawnPosition = "e2"
let moveCount = 0
let isGameOver = false
pawnPosition = "e4"
moveCount = moveCount + 1
Body Check: Every app on your phone uses flow and firmware. Your username? A variable — the flow (you could change it). The app's name? A constant — firmware (it's always "Instagram"). Your game score? Flow. The rule that you need 100 coins for a level? Firmware.
Part 4: Practice Exercises
Before each answer: LOOK → THINK → CHECK → MOVE → RESET
Exercise A: Sort It! — Flow (V) or Firmware (C)?
| Item | V or C? |
|---|
| Your age | |
| Your birthday | |
| The temperature outside | |
| The number of hours in a day (24) | |
| Your chess rating | |
| The number of cells on a chessboard (64) | |
| How many pieces you've captured this game | |
| The rule that the King moves one square at a time | |
| The score of a basketball game | |
| The number of players on a basketball team (5) | |
Exercise B: Write the Code
Turn these chess facts into code. Use let for flow (variables) and const for firmware (constants):
1. A pawn is worth 1 point (firmware — this never changes):
2. The player's current rating is 800 (flow — this can change):
3. A knight is currently on cell f3 (flow — this changes when it moves):
4. Each player starts with 16 pieces (firmware — this is always true):
Exercise C: The King = The CPU (Still Center = Processor)
Big Idea: The King is like the CPU (processor) — the still center of your computer. If the King is trapped (checkmate), the entire body shuts down. If the CPU stops, everything stops. Same pattern. Different body.
5. Why is the King like a computer's processor (CPU)?
- a) Because it's the fastest piece
- b) Because if it stops working, the whole body stops — game over
- c) Because it's the biggest piece
- d) Because it can move in all directions
6. In a video game, which of these is FLOW (a variable)?
- a) The name of the game (firmware)
- b) The player's current health points (changes!)
- c) The maximum number of levels — 50 (firmware)
- d) The color of the sky in the game (firmware)
7. What happens if you try to change FIRMWARE (a constant) in code?
- a) It changes normally
- b) The computer gives you an error — you broke the body's physics!
- c) Nothing happens
- d) The computer explodes
Part 5: Think Like an Engineer
8. List 3 "flow" (variables) and 3 "firmware" (constants) from your daily life:
Flow (things that change): 1. 2. 3.
Firmware (things that stay): 1. 2. 3.
9. A pawn starts small (firmware — just goes forward). But it can compile (promote) into a Queen — the most powerful piece. How is this like learning a new skill? Can a "variable" in your life grow bigger over time? Can firmware upgrade?
10. If you were building a chess app, what flow (variables) and firmware (constants) would you need? List at least 3 of each.
Week 2 Takeaway: Every body has flow (what changes) and firmware (what stays the same). Variables change, constants don't. Every program — and every chess game — uses both. When you track your pawn's position (flow) while following the rules (firmware), you're already thinking like a programmer. The body has physics (constants) and the medium flows through it (variables). Same pattern. Every body. Every program. Every life.