Stupid questions

Feynman, a $65 million rocket and an alert I nearly built for nobody. Most stupid questions are someone refusing to take a pattern second-hand.

Published: ·4 min read·First on Substack

A junior engineer on my team saved me a week of work with one question. We were designing alerts for production downtime, and they asked, "Why are we building this alert again?"

(They're fresh out of university, though they'd been at the company slightly longer than me, so "junior" is doing some heavy lifting there.)

I started explaining from scratch and the explanation fell apart about three sentences in. We were copying an alerting pattern we'd seen at other banks. Nobody had asked what our own SREs actually needed. If that question hadn't been asked, I'd have spent a week building something that added roughly nothing for the production support team it was meant for.

A stupid question is only stupid when you already know the answer. Most of the time it's someone refusing to take a pattern second-hand. And the more senior you get, the fewer of them you ask, which is exactly when you're carrying the most borrowed patterns around.

Richard Feynman made a career out of this. By his own account, people thought he was slow at first, because he'd stop a discussion to ask things like "Is a cathode plus or minus?" Then, an hour into someone's equations, he'd be the one who spotted the mistake. He never pretended to understand something he didn't, so every answer he held was one he'd built himself.

The best version of this is a story from Caltech. A colleague asked Feynman to explain why spin one-half particles obey Fermi-Dirac statistics. Feynman said he'd prepare a freshman lecture on it. A few days later he came back and said he couldn't do it: he couldn't reduce it to the freshman level, which meant nobody really understood it. A Nobel winner, admitting he didn't understand something because he couldn't make it simple. That's the test. If you can't take an idea back down to the basics, you're holding a borrowed answer.

Elon Musk's rocket question is the same move with a price tag on it. In 2002 a rocket cost $65 million, and the sensible response was that rockets are expensive, so either raise the money or give up. He asked something that sounded too basic to say out loud: what is a rocket actually made of? Aluminium, titanium, copper, carbon fibre. Then an even dumber one: what do those materials cost on the commodity market? About 2% of the price.

The other 98% was layers everyone had stopped questioning.

The other 98% was contractors, markups and inefficiencies that everyone in the industry had inherited and stopped looking at. A few years later SpaceX was launching for about a tenth of the old cost. Not because its engineers were smarter than NASA's. Because somebody asked the question that felt beneath them.

So why doesn't everyone do this? Because it's scary. Ozan Varol, in Think Like a Rocket Scientist, calls the default "reasoning by analogy": we do what worked somewhere similar, because that's cheaper than thinking. And once you've built some credibility, a basic question feels like gambling with it. The junior has nothing to lose. You, the senior person in the room nodding along, have a reputation you'd rather not spend on "sorry, what's a cathode?"

But the trade is lopsided. Looking stupid for five minutes is cheap. Being wrong for five months is not, and the second one is what borrowed patterns usually cost you.

I ran into this from the other side when I started Sportscanner. The question I kept asking was embarrassingly simple: why do you need ten different websites to book a badminton court in London? The smart answer, the one I kept giving myself, was that if this were a real problem someone would have solved it already. Google would have done it, or one of the booking platforms. The market must be too small. People must be fine with the tabs.

That answer is a borrowed pattern too. It assumes someone else already did the thinking. So I asked "why not?" instead, scraped 10,000+ URLs and built one search over all of it. Around 400 players had signed up by the time I first wrote this (purely word of mouth, plus some shameless Reddit posting). It's over 800 now.

But you can't question everything, can you? True. You'd never ship anything. You only need to do it for the thing you're about to spend a week on, which is a much shorter list, and it's usually the one everyone in the meeting is nodding at.

A word of caution, though. A stupid question asked to look clever is just a question. The useful kind is the one you're slightly embarrassed to ask, because you genuinely don't know the answer.