Test-driven development

I can propose some random thoughts:

1. If you ship, you will win; if you write tests too much, you will loose. "Ship the f...... thing!" - http://www.joelonsoftware.com/items/2009/09/23.html
2. Write code in such manner that allows you to make a release at arbitrary moment. Code always should work.
3. "Automated testing is only about 30-40% effective at finding defects" - http://blog.ircmaxell.com/2014/12/being-...loper.html It is more important in preventing degradation and TDD.

I thing, code quality depends on you, there is no a magic methodology to eliminate the subjective factor and there never will be. If you need to test some functionality, fine, but "100% coverage" is not justified economically.

Edit:
4. If it is possible, the author of the tested code != the author of the corresponding tests.