Skip to content
Tech News
← Back to articles

Software Drives People Insane

read original get Peopleware: Productive Projects and Teams (book) → more articles
Why This Matters

An opinion piece arguing that software's unique mix of speed, abstraction, money, and near-zero cost to change one's mind strips away the natural friction that keeps other industries grounded, leading teams to lose a sense of proportion. It matters because it reframes chronic scope churn and hype cycles as structural features of software work rather than individual failings, which is how most engineers and managers actually experience their jobs.

Key Takeaways
Worth a Look

Peopleware: Productive Projects and Teams (book) — DeMarco and Lister's classic argues exactly what this article does: the hard part of software isn't the code, it's the people and the conditions around them. It's a short, blunt read that helps explain why sane adults lose their sense of proportion on projects, and what managers can actually do about it.

See Peopleware: Productive Projects and Teams (book) on Amazon → Affiliate link — we may earn a commission on purchases, at no extra cost to you. Product picked by AI based on this article; it is not a tested recommendation.

Software Drives People Insane

10 Sep, 2026

I have a little pet theory that software drives people insane.

Not in the "wash your hands every thirty minutes like Howard Hughes" kind of way, but more so in how the conditions surrounding software seem remarkably effective at making otherwise normal people lose their sense of proportion.

I've watched this happen enough times from enough angles that I don't think it's entirely a personality problem.

Software combines speed, money, complexity, abstraction, and almost unlimited freedom to change your mind. On their own, those things are perfectly manageable, but put them together and you start to get some really bizarre side-effects.

Most software, when you strip away the branding and architecture diagrams, is remarkably boring. A form here, an API endpoint there, sprinkle in some permissions, calculations, workflows, and a database somewhere. Maybe a queue if you need to scale something (or you're feeling adventurous).

But, harsh as it may be: most software is still just a glorified spreadsheet.

And yet somehow the process of producing this stuff can turn perfectly ordinary adults into b-tier Bond villains. The project is never moving fast enough, the plan has to be ever-flexible to sudden change, and every new feature is the one that's going to be the one (but certainly not that one that was supposed to be the one during the previous sprint).

There is always some new concern about whether it will work, whether it will scale, whether we're moving fast enough, or whether we should be doing something else entirely.

... continue reading