Comments by "" (@brownhorsesoftware3605) on "Why Hasn't TDD Taken Over The World?" video.

  1. When I first heard the term test driven development my initial thought was OK but then don't I also need to write a test to test the test code? In other words,, why would the test be more trustworthy than the code I'm writing? Then I saw one of your videos and realized that the important part is not the test but the ability to test immediately - that is, having a way to test the code before you write it. So your test is not so much a test to prove correctness as a running context to providest immediate feedback. I cannot imagine writing code before you have a way to run/test it. I have spent most of my time on platform internals and prefer to find a test rather than write one both to avoid programmer bias and exercise other people's code. Now that I have returned to app development (UX and everything) implementation order by design takes care of providing the test context for coding. Then I let Google do their automated approval testing on my Android app for me: less code to maintain. I already do a lot of thinking and organizing on paper before coding - maybe because I started and have done lots of work in assembler. Maybe because I was an English major.
    4
  2.  @niuniuch  But you must write the test before you write what you are testing. And if you write the production code before the test it is no longer TDD...
    1
  3. Coding is not accounting.
    1