Great summary on how to take TDD just seriously enough for it to be very useful without being too costly.
I've been using TDD "lite edition" for about ten years or so - I write just enough tests for the hard bits where I either don't know what I'm doing and/or am not sure I did it right (which is often).
I started out worrying about code coverage, but that seems like it adds more stress than is useful.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.