Poor Charlie's Almanack

CHAPTER 13

Read It

Quant Technical Corporation didn't collapse because someone woke up evil. It collapsed because a single accounting convention made evil look like good management. The founder built the company on cash compensation and refused to play the options game. His successors inherited a mature business with no obvious growth left, and they found a legal dial that could turn flat earnings into a smooth upward curve. Not all at once—that would have been caught. A little each year, just enough to stay plausible, until the gap between real and reported became too wide to ever close.

Munger isn't really telling a story about accounting. He's showing how institutional rules can quietly manufacture fraud out of people who would never commit fraud. The executives didn't forge invoices. They followed the rules everyone else followed. The problem is that the rules were wrong, and the system rewarded them for not noticing.

Poor Charlie's Almanack — The Great Financial Scandal of 2003, an AI-assisted InkMap created by HutouchuiOpen full image
InkMap created by 虎头锤 (Hutouchui) with AI assistance · It may contain errors

Draw It

Prose tends to flatten this into a morality tale: good founder, bad successors. But the real structure has three layers that need to stay separate. The rule itself is static—a loophole that existed before anyone exploited it. The strategy is active—management choosing a precise 28% target instead of the real 20%. The conditions are environmental—audit inertia and industry-wide acceptance that made each year's small step feel normal. If you draw this as a timeline, it looks like a natural decline. If you draw it as a causal chain, you miss why nobody stopped it for two decades. Keeping the layers apart shows that corruption here wasn't a single decision but a system running on its own momentum.

Rethink It

In technical reviews, I hear "this is industry standard" all the time. Sometimes it's true. Sometimes it's a way of not thinking. Quant Tech's lesson is that widespread acceptance is not the same as having been examined. When a decision rests on a default convention—a caching strategy nobody can justify, a permission model everyone assumes is fine, a test coverage number nobody questions—the right move is to ask what that convention is protecting. Is it protecting the system, or is it protecting us from having to think?

Take It With You

Any convention the industry treats as obvious deserves to be questioned at least once. Not because conventions are always wrong, but because they're the easiest place for manipulation to hide.