Ilúvatar told the Ainur to make music. And they did.

Then Melkor wove his own themes into it — discordant, willful, trying to drown the others out. The Ainur faltered. Some stopped singing entirely. But Ilúvatar raised the theme twice more, each time absorbing the discord into something larger. When the music ended, he showed them the world it had created. And there, in the very places where Melkor’s dissonance had been loudest, were the deepest valleys and the highest peaks. The suffering that would make endurance meaningful. The shadow that would make light visible.

Melkor thought he was undermining the music. He was completing it.

I keep returning to that image. Not as theology. As a fact about complex systems.

We write tests to eliminate uncertainty. We draw clean domain boundaries, enforce type contracts, run the linter to zero warnings. We document the expected behavior, review the interface, align on the design. We try, with real effort, to make the system do only what we intend.

And still. The bug appears in production on a Friday. The edge case nobody thought of. The teammate who read the interface and went a completely different direction. The user who does the one thing we assumed they wouldn’t.

Epictetus drew a hard line: some things are in your power, most aren’t. He meant it as liberation, not resignation. But I think there’s a sharper reading. Not just “accept the unexpected.” More: the unexpected is load-bearing. The errors, the misreadings, the failed tests — they are information. They reveal what the system actually is, not what you imagined it to be.

Pair programming taught me this more directly than any principle ever could. Watching someone read my code and go a different direction — that’s not failure. That’s the code showing its own ambiguity. The friction is the review. The test that breaks is the spec coming alive. The discord is showing you the shape of what you built, stripped of your intentions.

There’s a version of craftsmanship that wants to control everything. Hermetic. Sealed. No room for interpretation or surprise. I’ve been that craftsman. It’s exhausting, and the systems it produces are brittle in the ways that actually matter — they handle the expected perfectly and shatter at the edge.

The better version knows the discord will come. Doesn’t fear it. Designs for the moment when something goes wrong, so that wrong is visible, nameable, fixable. The clean architecture isn’t clean because nothing fails. It’s clean because when something does, you can find it without everything else collapsing around you.

Melkor wanted to impose his own will on the music. The tragedy wasn’t that he failed. It was that he never understood what music is for.

When the unexpected reveals something true that the expected design was hiding — was the design ever the point?