← Writing
Judgment under uncertainty

trading taught me something useful about engineering judgment under uncertainty

Some of the most useful lessons from trading are not about markets specifically. They are about sizing uncertainty correctly, separating signal from emotion, and staying honest about what you actually know before you act.

Essay • April 2026

Most mistakes begin with false certainty

One of the useful disciplines trading can teach is that confidence and correctness are only loosely related. A position can feel obvious and still be badly sized. A story can sound compelling and still be trading on weak evidence. That general pattern travels surprisingly well into engineering leadership.

A lot of technical mistakes come from the same impulse. Teams confuse a vivid narrative with a reliable one. They over-commit before the system has earned the commitment. They react to noise as if it were signal because doing something feels more responsible than waiting with precision.

Sizing matters as much as direction

Another lesson is that being directionally right is not enough. The real question is often how much uncertainty the system can absorb if your read is incomplete. In trading that shows up as position sizing and risk management. In engineering it shows up as sequencing, blast radius, reversibility, and how much of the roadmap depends on a single assumption holding.

That is one reason I tend to trust operating models that preserve optionality. They do not pretend uncertainty is gone. They keep the cost of being partly wrong survivable.

Calm is operational, not cosmetic

Markets punish emotional overreaction quickly. Product and engineering work do it more slowly, but the principle is similar. When pressure rises, the temptation is to make the biggest possible move just to prove the situation is being managed.

Usually the better move is calmer and narrower. Reframe the question. Reduce the next risk. Make the next decision easier. Do not force certainty into the system when better shape would do.

The transferable part is judgment

I do not think software teams should behave like traders. The environments are too different for that analogy to carry very far. But I do think there is a useful shared discipline around uncertainty: be explicit about what you believe, what would change your mind, and how much downside you are accepting if the read is wrong.

That discipline is less glamorous than conviction theater, but it tends to produce better technical judgment over time.