When to Trust Your Gut (and When It's Lying to You)

"Trust your gut" is either the best advice in engineering or the worst, and the only thing that decides which is who you say it to.

Your gut is not magic. It's compressed experience: thousands of hours of pattern, filed somewhere you can't consciously reach, returning a verdict before you've finished reading the ticket. For someone who actually paid for those hours, that verdict is the most valuable instrument they own. For someone who hasn't, "trust your gut" is just permission to be confident and wrong. Same three words, opposite advice, and most people hand them out without checking which person is standing in front of them.

So the question was never "should I trust my gut." It's "is this gut trained on this problem."

A gut is domain-specific, and it expires. I haven't shipped production code since around 2015, the tail end of a long run in Scala. My instinct for where a distributed system will bite, which queue backs up first, which "temporary" fix is quietly load-bearing, which 2am page is already on its way, is still sharp, because I spent fifteen years buying it and the physics haven't moved. My instinct for whether some framework that shipped last year is the right pick is worth nothing. From the inside it feels like the exact same gut. It is not. One is trained and current; the other is a director with an opinion and no reps. Knowing where that line falls, and refusing to let the title smudge it, is most of the job.

The hard part is that the time your gut saved you and the time it sank you feel identical while they're happening. Intuition is right when the situation genuinely rhymes with ones you've lived: same shape, same mechanics, your pattern-matcher firing on real patterns. It betrays you when the surface looks familiar but the ground underneath has shifted, and you match on the surface anyway. The new system that resembles the old one. The candidate who reminds you of someone great. The design that was rock solid at a tenth of the load.

There is a clean test for which one you're in: can you say why. Real intuition unpacks in hindsight. You felt it in a second, but afterward you can reconstruct the reasoning and it holds up. If you cannot explain it even after the fact, it was never intuition. It was a preference, or a bias, or the answer you already wanted, and it just arrived fast enough to pass for instinct.

None of this is a case for slowing every call down to a spreadsheet. A senior who needs data for everything is as broken as a junior who needs it for nothing, usually someone who built a good instrument and then got scared off it by one bad call. Spend your gut where it's calibrated. Reach for data where it isn't. And say which is which out loud: "my gut says ship it, but I haven't been close to this layer in two years, so push back on me" is the most senior sentence you can say in a room. It trusts the gut and audits it in the same breath.

So by all means, trust your gut. Just make sure it's actually yours, actually on this, and not the loudest voice in your head doing an impression of experience.