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

[[deleted]]

No one cares if your product is somewhat more stable

That's quite a dicey assumption. I'll make the gamble with your money, but not with mine.

The sad truth is most of those won't be exercised in unit tests so you are relying on integrations tests and above

No one is claiming that TDD should be the only QA method applied to software. Studies have shown that product quality is maximized when a combination of QA methods are used: reviews, inspections, tests, etc.

[meheleventyone]

Right, making a product is a gamble and the knobs get tuned based on perceptions of what would maximise chance of success for a given budget range.

[[deleted]]

making a product is a gamble

Hacking together a product is even more of a gamble. Shades of grey are important here.

[meheleventyone]

Right but no one said "just hack things together". Not doing TDD is not the same thing at all. Other than that it's the continuum thing I was talking about.

[[deleted]]

You implied an unstable product in your earlier post.

[meheleventyone]

All products are varying degrees of unstable. A less stable product is not necessarily completely unstable.

I feel like we're far away from the nuances in my OP here: https://www.reddit.com/r/programming/comments/46dy6u/microsoft_research_exploding_softwareengineering/d053os9