Just write the code and then write the test. Or just write the test and then write the code. Or think about the test when writing the code. Or think about the c

Just write the code and then write the test. Or just write the test and then write the code. Or think about the test when writing the code. Or think about the code when writing the test. It doesn't really matter right. The thought process is going to occur anyways. Focusing on resuable patterns, consistency, and creating reliable and easy to read code is 10x more important than the TDD drivel that is out there. Honestly, honestly, The only reason we discuss this crap is because there are people who make off running around the country giving talks and writing books on all things developers (nothing wrong with that).