Link Details

The title is misleading and isn't really the point of the article. In the art-related anecdote, quality was actually achieved through producing quantity and learning from it. Based on this example, it's not true that quantity trumps quality but rather that potentially learning from writing the same code multiple times can lead to a better (higher quality) result. Of course, this assumes that the person doing the programming is motivated and able to learn effectively from their mistakes. I agree that it's a good strategy to not get too hung up on analytical approaches to achieving quality. However, this article doesn't provide any real evidence that just slinging code without a focus on quality will reliably lead to better results. No trumps. Balance is better.