The Art of Not Knowing
There’s a strange paradox in engineering. The more you learn, the more you realise how little you know. And that’s not a bug — it’s a feature.
The comfort of certainty
Early in my career, I wanted answers. Clean, definitive, absolute answers. I wanted to know the right way to build things. The correct architecture. The best language.
Years later, I’ve come to appreciate that the most honest answer to most hard questions is: it depends.
Why “I don’t know” is powerful
Saying “I don’t know” does three things:
- It opens the door to learning instead of defending
- It creates space for collaboration instead of authority
- It forces you to think instead of react
The engineers I admire most aren’t the ones with all the answers. They’re the ones who ask the best questions.
Embracing the fog
Building distributed systems taught me this viscerally. You can’t know the state of every node. You can’t predict every failure mode. You design for uncertainty — you embrace it.
Maybe that’s the real lesson. Not just in systems, but in life. The fog isn’t something to fight. It’s something to navigate.