Puzzles, Mysteries, and the Work of Front-End Development
Bob Hoffman relays a distinction from Malcolm Gladwell: puzzles are problems defined by a lack of information. A puzzle has an answer, and more data moves you closer to it. Take the question of where Jimmy Hoffa is buried. "New Jersey" narrows the field; "northern New Jersey" narrows it further; "the Meadowlands" resolves it. Each additional detail is progress.
Mysteries work the other way around. They are problems we have plenty of information about but no accurate analysis for. Gladwell's example is the failure of inner-city schools. Thousands of studies exist, every university education department has produced one, every congressional committee has issued a report, and every pundit and editorial writer has a theory — yet no definitive answer has emerged. The problem isn't insufficient evidence. It's that the evidence doesn't yield a clean conclusion.
Why the Distinction Matters for Engineering
Hoffman maps the two categories onto front-end work. While coding, each problem we encounter is a puzzle: gather the missing information and the path forward becomes clear. Design behaves that way sometimes too — better information can produce better design decisions.
But success in design has a nebulous quality that makes it feel more like a mystery.
Hoffman adds a handful of other domains to the mystery column: business, marketing, and love. And on the coding side, he carves out one exception to the puzzle rule — CORS, which he files under mystery.



