Lectures

Tommy breeds 2048-final, final2, exactly-last folders — and drowns in them. We figure out why copying folders for safety leads to losing orientation, and how he himself gropes toward the idea of a “save for code.”

Why doesn’t code have a Save/Load button like games do? Alex explains to Tommy that code goes through a chain of states, you want to return to the good ones, and shows the three troubles with folder copies and the decomposition technique.

How do real developers store project versions? Alex introduces Tommy to git — a single history timeline instead of a warehouse of copies, explains git’s three abilities using Google Docs history as an example, and recommends what to use instead of git right now.

The /rewind command is a big Ctrl+Z for agent work. We walk through the rollback menu, what /rewind will not bring back, and get familiar with the slash-command control panel: /help, /clear, as well as continuing a session with --continue and --resume.

Tommy assembles Tetris step by step, goes through his first rewind with /rewind and Restore code, and feels the experiment detach from risk. Backup folders are no longer needed — one button has taken their place.

We live in the information age. We will figure out why the 20th industrial century gave way to the information revolution, how IT companies became the most expensive in the world, and why they are worth trillions of dollars.