3 ms·
I read the post as stating that "Quality [of releases] is better than quantity", which is patently false IMO -- in fact, I would say that quantity of releases i
by cookiecaper 10y ago
I read the post as stating that "Quality [of releases] is better than quantity", which is patently false IMO -- in fact, I would say that quantity of releases is pre-requisite for quality. Software grows up best when it's submitted for user feedback frequently and iterative changes are made based on that feedback. Waiting until something's perfect, or even "high-quality engineering", means it never gets done. A strong shipping bias is necessary to get software that works and works well.
- webmaven 10y agoOkay, that's a reasonable interpretation. However, mine was "quality [of code] is better than quantity" or "quality [of features] is better than quantity". Like the way Lean defines "waste" (muda), the meaning of "quality" and "quantity" in the world of software are highly context specific (and should usually be tied to customer perception).