It's horses for courses really. It all comes down to the cost of an escaped defect: Impact of failure; costs to rectify vs costs of writing bug free code. If fo

It's horses for courses really. It all comes down to the cost of an escaped defect: Impact of failure; costs to rectify vs costs of writing bug free code. If for instance you're writing code for a vertically integrated application that you manage yourself you can fix it any time with little cost then simply "move fast and break things" makes sense. If you're shipping software where usage and maintenance is out of your control you should be a little more circumspect. If your code does something critical like manages e.g. a space shuttle [0] then there should be a significant $/£/€ tag attached to failure such that justifying an overbearing process is a no brainer. [0] http://www.fastcompany.com/28121/they-write-right-stuff http://www.fastcompany.com/28121/they-write-right-stuff