HN Hall of Fame Weekly email

Why It Is Important That Software Projects Fail (2008)

www.berglas.org Essays & writing Essays & articles Software engineering Candidate
Screenshot of www.berglas.org captured 2026-07-20
Page preview · captured 2026-07-20

Resurfaced independently across 6 calendar years, with breakout response in 2 of them.

submissions
6
submitters
6
observed span
2009–2023
peak thread · 72 comments
139 pts
latest 20+ return · 2020-09-06
119 pts

Submission timeline

2007–2026

One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.

First comments on top threads

HN comment order

> As the primary net effect of software is to facilitate bureaucratic complexity it is therefor essential that software projects fail I love this conceptualization of what software is for. But I have the complete opposite moral interpretation. Unstated is the presumption that bureaucratic complexity is bad. I think increasing it is the goal of society, and ethics constantly demand us to increase it. For example, it’s easy for banks to simply reject loan applicants who were convicted of felonies…

> As the primary net effect of software is to facilitate bureaucratic complexity it is therefor essential that software projects fail if society is to function effectively. This is a short-sighted and overly pessimistic view of the role of software. Let's bring in some sorely needed optimism that's especially relevant to the current pandemic: https://blog.cleancoder.com/uncle-bob/2020/04/05/ANewHope.ht... Another area where software is actually good for the world is accessibility. Lots of people with disabilities…

The author argues that failed software projects are nonetheless beneficial: Their development employs many bureaucrats, consultants and contractors and their expenditure supports an even larger number of people throughout society. ... by the same argument I should stroll around the city and burn some cars, thereby offering employment to many firefighters, car producers, actuaries and all their suppliers. The point about ever-expanding bureaucracies is well noted however. Perhaps it is our duty to design really bad…

The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.

Breakout years
2

100+ points or 50+ comments

Total points
317

reference only — not used in Hall rules or ranking

Total comments
116

reference only — not used in Hall rules or ranking

Every submission

DateTitle as submittedByPointsComments
2009-11-10Why it is Important that Software Projects Failfogus5426
2011-11-16Complexity is bad, software failures limit complexityartsrc20
2016-08-10Why It Is Important That Software Projects Fail (2008)haihaibye10
2019-06-05Why It Is Important That Software Projects Fail (2008)First breakout · Best threadperfunctory13918
2020-09-06Why it is important that software projects fail (2008)Latest 20+ point returnkwhitefoot11972
2023-11-26Why It Is Important That Software Projects Fail (2008)metadat20