Comment

Comment by gshulegaard

Perhaps I am wrong here, but I got a much different message out of the post.

It's not about actually having ZERO bugs as it is about enforcing a strict and logical classification system.

I think this quote resonated with me the most:

> ...but much more so, the bugs were a result of incorrect specification or missing specifications.

The argument being made is that if you hand a developer a specification, the developer implements the specification _as specified_, then you discover the specification was incorrect or that in practice you want a change would you classify that as a _BUG_? No. But a lot of shops _do_, so they end up with _too_ many tasks classified as a "Bug" which makes it impossible to prioritize since being a "Bug" is a binary descriptor.

By enforcing a classification system means you have the ability to then enforce a prioritization system...and really the prioritization system is key for maintaining consistent output and forward progress.

At least that what I felt the argument of the post was...and I see some reasonability to it. Especially since, as the author mentioned, this is not a new idea.

parent gshulegaard 10 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton