The obvious is the hardest thing to find.

Every time I use software that is really well made, I think the same thing: of course, that is how it should be. It feels self-evident, as if there was never any other way to do it.

And then everyone copies it. Why wouldn’t they? When a solution is obviously right, there is no reason to build it any other way. It becomes the standard, and after a while no one can imagine it was ever different.

That is exactly where the catch is. The obvious looks easy in hindsight. Finding it is the hardest part of the whole thing.

Because at the start, nothing is obvious. At the start there is the first draft, and it is almost never the right one. So the second one comes. You build something, use it yourself, notice where it snags, and throw it away again. You argue it out in the team until someone has the one thought that makes everything simpler. You keep taking things out until only what is really needed is left.

That takes time. And time is exactly what there is least of in a project. The easy path would be to take the first usable draft and move on. It works, after all. But “works” and “self-evident” are two different things, and the distance between them is the actual work.

You rarely get there alone. The best solutions come when several people pull on the same problem, each from their own corner, until the penny drops. One sees the tech, another the user. And someone sees the edge where it will all break later. Together you find the obvious thing that no one saw on their own.

And once you are there, you can no longer see the work in the result. The whole detour disappears. What is left is something that feels like it was always there. That is the best moment in this job for me. Not the launch, not the praise. The moment something becomes so simple that no one notices it anymore.

You don’t notice good software. That is no accident. It is the work that, in the end, no one sees.