What Does “Proficient” at TDD Look Like?
These also apply to test-last developers.<p>Eg, suppose I write all the code and don&#x27;t write the tests until the end. Then I spend 5 weeks writing tests.<p>I can easily write dozens of tests in an 8 hour day, and refactor code to make it more testable. I&#x27;m still writing tests, so bristle at the suggestion that I should. I&#x27;m using coverage to help figure out which tests to write, so I&#x27;m easily going to get 80% or better.<p>My own style is much closer to &quot;Spike and Stabilize&quot;, and not TDD, yet all the things you wrote also apply to me.<p>FWIW, I almost never use the debugger, even without doing TDD, as I use print statements. Even with TDD, for some people the debugger is used as a way to understand&#x2F;explore the interface to other libraries.<p>BTW, I see no mention of &quot;mantra&quot; of &quot;red&#x2F;green&#x2F;refactor&quot;.