...he was a duct tape programmer! He always got it done by the deadline, but then he spent 75% of his time maintaining... in some cases we just tossed the exisiting work and started from scratch
Maintainability costs money. The article would have been much better if it just linked to the KISS principle as a reminder that needless complexity is bad. Instead there's this apparent (unintended?) emphasis on lower quality with the use of the "duct tape" metaphor as well as an out of context reference to Gabriel's "Worse is Better" essay*. The hard problem in software is maintainability, which is usually the result of hack-n-slash code that appears "done" because it "works" (just don't ever change it).
* There is a big difference between not developing the "perfect product" (i.e. every ideal feature) vs. code quality. The latter has a direct correlation to maintainability costs and future development velocity.
Here are some Test Driven Development studies.
Anecdotally, my 13 year career is split almost exactly 50/50 TDD/!TDD. While I kicked and screamed initially, I'm confident that TDD has had the most positive impact on my effectiveness as a software developer.
Unlike homeowner's insurance, where you ARE playing against the house. Or car insurance. Or the state lottery. Or mutual funds. Or health insurance.
We manage risk all the time, and happily pay people for the privilege. I've never understood why poker got such a bad rep.
Ignorance.
Hackers of the world, unite!