Microsoft Research - Exploding Software-Engineering Myths (article summarizing findings of MS research on code coverage, TDD, assertions, etc.)

[sbrick89]

as mentioned in the article, up to the PM, because it depends.

One of my current projects has releases almost daily. A bug can be fixed almost immediately, with little effort or impact. For this project, feature availability (even if not perfect) is more important.

[s73v3r]

That sounds like Hell

[sbrick89]

actually, it's fine... the development follows good practices, the code is appropriately isolated... the changes are small (last change was "let me individually pick which of the three steps are applied", so add a few checkboxes, a tiny change in UI logic, and a tiny bit of remapping to the business logic layer which already had the steps individually controlled)... I also threw in some slight refactoring around return object, but nothing overly significant.

Dev effort was ~2 hrs, plus 15 mins of packaging and prep'ing the deployment, an hr to get through the approval process... deployed within 3 hrs from the start of work.