August 7, 2026
Death by a thousand forms
Reverse Jevons Paradox
When red tape gets pricey, people stop fixing things at all
TLDR: The article argues that when changing software gets too expensive in time and paperwork, small but important improvements can disappear entirely. Commenters mostly said, “Yep, that’s bureaucracy,” though a few jumped in to fight over whether this is a real paradox or just basic economics.
A spicy little idea lit up the comments this week: what if making something harder and more expensive doesn’t just slow people down — it makes whole kinds of useful work vanish completely? That’s the pitch behind “Reverse Jevons Paradox,” a fancy label for a very relatable mess: pile on reviews, approvals, forms, and ticket drama, and suddenly nobody bothers with the tiny cleanups that keep projects healthy. The crowd instantly translated it into plain English: bureaucracy. Brutal, simple, devastating.
And the comments? Oh, they were ready. One camp basically said, “This isn’t some grand paradox, this is just how incentives work,” with one user arguing it’s really standard supply-and-demand logic, not a new law of the universe. Another group didn’t care what it’s called — they cared that it feels painfully real, comparing it to housing rules, bloated companies, and those rage-inducing online forms that get so long you just abandon them. The most deliciously cynical take was that small fixes don’t die — they get “smuggled through” inside unrelated work because the approval maze is too awful to face twice.
The humor was dark and deeply familiar: endless Jira arguments, too many sign-offs, and a theater of “return on investment” where people spend more time debating than doing. In other words, the community verdict was clear: call it a paradox, call it process rot, call it office cosplay — just don’t expect the code, the form, or the system to improve while everyone is stuck asking permission.
Key Points
- •The article defines Jevons paradox as lower unit cost leading to higher total spending on a resource because usage expands.
- •The gasoline example is used to show how lower operating costs can make additional activities economically viable.
- •The article applies Jevons paradox to software engineering by contrasting slow nightly builds with fast per-commit and local test runs.
- •It argues that this effect can work in reverse when higher costs reduce total use of a resource, potentially to zero.
- •As a software example, the article says heavy review and approval processes can eliminate small refactoring changes by making them not worth doing.