Precision is not perfectionism
The most dangerous error is the one that gives you a plausible answer, just the wrong one.
There is a specific kind of mistake that's worse than a crash. A crash is obvious — you know immediately that something broke. But the mistake that returns a plausible answer, just the wrong one, lives in your system quietly, doing damage you can't see.
I was deep in a financial system yesterday, processing supplier invoices for one of the businesses I run. A line item would come through and the total would be, say, forty-nine dollars. The system accepted it. The number looked reasonable. But the real figure was forty-one. A discount had gone uncaptured — the code didn't even know there was a field for it — so every discounted line was silently inflated.
Nothing crashed. Nobody panicked. That's what made it worse.
Precision is not the same as perfectionism
Perfectionism is the fear that it isn't good enough yet. Precision is the discipline to care about whether the answer is correct. Founders conflate the two, then use one as an excuse to avoid the other.
Perfectionism says: I'm not shipping until everything is clean.
Precision says: I'm not shipping until this specific thing is right.
I've been guilty of the first. I spent years polishing things that didn't need polish while real errors sat quietly underneath. The discipline I've had to build — slowly — is getting precise about what actually matters, then shipping, even when the rest is still rough.
The discount field wasn't a preference. It wasn't polish. It was the difference between a correct answer and a wrong one. That's worth stopping for. That's worth the detour.
What is not worth the detour: the refactor nobody asked for, the layout adjustment that makes you feel productive, the optimization on a flow that gets twenty visitors a month. Those are perfectionism wearing the mask of diligence.
The thing I shipped yesterday didn't get pushed because it was perfect. It got pushed when I found the specific wrongness, fixed it, and verified that the output was now correct. The rest of the system still has rough edges. Still imperfect in a dozen ways I can see. But the number is right.
Done has a floor. Done means the thing you built actually does what it's supposed to do. Not beautiful. Not optimal. Correct.
Find the wrong answer that looks right. Fix it. Ship it.