Stash

Loop lifted the lid. "Watch. I'll put a value in." She set a card marked 5 inside and closed it. On the little screen behind her, it showed: x = 5. "That's called assignment — putting the value 5 into a box labeled 'x.'" Then she opened the box and held up the 5 for everyone to see. "And this is reference — asking for whatever's in the box right now: print(x) — and out comes 5." She smiled. "A variable has two parts, and only two: a name (the label on the side) and a value (whatever's inside). That's it. Put in, take out."

"Now the part that surprises people," Loop said. She opened the box, took out the 5, and dropped in a card marked 10. The screen updated: x = 10. "Same box. Same label — still 'x.' But brand-new contents. That's reassignment — you can empty the box and refill it whenever you like. The label stays put; the value can change as often as you want." She held up different cards. "And lots of kinds of things can go in the box, not just numbers — a bit of text like "hello", or a whole list of things — depending on the language's rules. The box doesn't care much what you keep in it. It just holds it, steady, until you come back for it."

"Two more things, and they're about being kind to future-you," Loop said, tapping the label. "First — names matter. A good label tells you what's in the box: score, playerName, currentLevel. A lazy label like x or temp or data leaves you guessing later what you even stored." She pointed around the room to imaginary boxes. "Second — scope. Some boxes sit out where the whole program can reach them; others live only inside one little corner — one function's workbench — and vanish when that job is done. Knowing where a box can be reached keeps you from hunting for a value that isn't there." She closed Stash gently. "But under all of it — Stash is still just: box, label, value. Put in, take out, change the contents."