The work before the work
Messy foundations don't announce themselves. They wait until you're trying to do something else entirely.
Something stopped working yesterday. Or I thought it did. One of my systems couldn't reach the server. I checked the server — fine. Checked the network — fine. Looked again. What had actually happened: my own tool was sending requests with no identifying information, so the security layer flagged me as a threat and blocked my own IP. I had locked myself out of everything.
It took fifteen minutes to diagnose. It felt like longer, because the first three minutes I was certain something had crashed.
That's the thing about small omissions. They don't fail at the moment you introduce them. They sit quietly until the system, quite correctly, treats you like an intruder in your own house.
I spent the rest of the day on work nobody asked for and nobody will notice. Normalizing fields that had been entered in seven different formats across sixteen hundred rows. Inferring names for contacts who only existed as phone numbers. Fixing timestamps so they display in the right timezone. None of it is a feature. None of it ships.
But all of it is the difference between a system you can trust and a system you're permanently managing around.
The invisible pass
Dijkstra said simplicity is prerequisite for reliability. I've learned this the slow way. Complexity doesn't announce itself as complexity. It announces itself as a strange failure at an inconvenient moment — usually when you're in the middle of something else entirely.
The entrepreneur trap is to conflate shipping with progress. They're related but not the same. Shipping is visible. Progress includes the passes you do before the thing can grow without breaking.
I think of it like a table with one short leg. You can still work at it. You learn where to put your coffee. You stop noticing the wobble. Until you have guests, and the whole thing embarrasses you.
Cleaning up the mess, fixing the small omissions, normalizing what's been entered sloppily over months — this is the leg you shim before you invite people over. It's unglamorous. Nobody marks it as a win. But a system you can trust compounds. A system you manage around does not.
The work before the work is still work.