Comments by "Andrea Laforgia" (@andrealaforgia) on "Test Driven Development vs Behavior Driven Development" video.

  1.  @gillscramble  When you test-drive development, writing a code for the test and writing a code for its intended use case are the same activity. The purpose of TDD is not to prevent bad tests. It's to allow well-designed code. >As I said, design should not be for the test. And all of your design properties are good, and the are good on their own. That is not true at all. In general, when designing a system (not necessarily just software systems), the testability of that system is a design requirement. You want a system that allows to be "probed" to diagnose any problems. Any complex system caters for some sort of diagnostic mechanism. There is a reason you generate logs in a structured format, for example. Take dependency injection: one of the advantages of using it is that you can easily mock the collaborators of the system under test.
    1
  2. Wow... your tin foil hat really works!!
    1