The Beauty of Constraints

Every great design starts with something you can't do.

I keep noticing this. Take chess — a game built entirely on restriction. Pieces can only move certain ways, on a fixed grid, with a single goal. And yet the depth is practically inexhaustible. The constraints aren't getting in the way of the game. They are the game. Remove one and you don't get more freedom — you get less interesting decisions.

The same thing shows up in code. When a function is limited to one input and one output, something clarifies. When a system is told it cannot hold state, it's forced to be honest about what it actually needs. The restriction that feels like a handicap turns out to be a flashlight — it illuminates the real shape of the problem.

There's a word for this in architecture: compression. The best structures put material only where it needs to be, and nowhere else. What's left is something that feels inevitable, even though it took enormous thought to get there.

I think what's actually happening is that constraints collapse the solution space. Without them, you're searching an infinite field. With them, you're searching a garden. The garden is where craft lives.

This is also why blank pages are hard. Not because ideas are missing — because nothing is ruled out yet. The first constraint you impose (a form, a length, a voice) doesn't limit the work. It begins it.

Freedom is surprisingly hard to think inside.