Modern software is full of illusions — pages that feel instant, apps that seem to have unlimited memory, recommendations that feel like mind-reading. Each of those is a separate trick. This one is about undo: how an app can remember not just the current state of your document, but every state it's ever been in, in the right order, ready to reverse on demand. The mechanism is called the command pattern, and once you see it, you'll notice it everywhere.

The naive assumption is that undo works by saving snapshots — that every time you type a word, the app photographs the entire document and stores it. That would work, technically. It would also be catastrophic. A 50-page document saved after every keystroke would consume gigabytes of memory in minutes. Nobody does this.

Instead of saving the document, the app saves the action. Not 'here is what the document looked like,' but 'the user typed the letter E at position 47.' More importantly, it also saves the reverse: 'to undo this, delete the letter at position 47.' Every action — typing, deleting, formatting, moving — gets wrapped into a small object that knows both how to execute itself and how to undo itself. Programmers call this a command object. The app keeps a running list of these objects in the order they happened. That list is the undo stack. When you hit Ctrl+Z, the app doesn't search through history. It just looks at the top of the stack, grabs the most recent command object, runs its undo instruction, and pops it off. Hit Ctrl+Z again and it does the same thing with the next one down. The whole operation takes microseconds regardless of how long your document is, because it's not touching the document at all — it's just executing a tiny pre-written reversal.

This is also why undo breaks in predictable ways. If you close the document, the stack is gone — there's nothing to undo because the command objects were only kept in memory. Some apps persist the stack to disk, which is why a few tools let you undo across sessions. And when an app tells you 'can't undo this action,' it usually means one of two things: the action wasn't wrapped in a command object (someone skipped the plumbing), or the action had side effects that can't be reversed — like sending an email or writing to a database. You can't un-send. The command pattern only works when every action has a clean inverse, and some actions don't.