Comments by "TheEvertw" (@TheEvertw) on "TDD Isn't Hard, It's Something Else..." video.

  1. If the legacy classes are testable, there is no reason not to do TDD. If the legacy classes are not testable, you could work towards making them testable, especially those parts that are subject to most change. That effort will soon earn itself back.
    3
  2. I LOVE TDD. It is the only way to write professional software. There is one situation in which it shouldn't be used: when exploring a solution space. But as soon as the design starts to solidify, the paradigm should shift to TDD.
    2
  3.  @ContinuousDelivery  to focus on design while still exploring the solution space will lead to premature choices you will regret. It is better to make throw-away proof-of-concepts in that phase. Just be sure to actually throw them away...
    2
  4.  @tdp-pop6810  White-boards don't give feedback.
    1
  5. Talking about Javascript for in the browser, I presume? It is about time we ditch that abomination. Though you could bring them under test by writing a simulation of the DOM etc.
    1