Comments by "Ton Bong" (@tongobong1) on "Synchronous vs Asynchronous Programming" video.

  1.  @PavelHenkin  but you can develop outside-in/top-down with classical unit tests too and the end result are easy to understand tests without mocks and easy to change implementation of existing functionality without breaking the unit test. Unit tests should only fail when functionality changes and not when internal implementation changes while functionality stays the same.
    3
  2.  @PavelHenkin  Then don't mock interactions between objects unless they go outside the process like calls to IO, database, network...
    2
  3. STOP WRITING LONDON STYLE UNIT TESTS because they are terrible for projects!
    1
  4.  @thatoneuser8600  I am trying to save Europe from London style unit test. We are losing billions because of bad tests.
    1
  5.  @PavelHenkin  London style unit tests are actually class tests. Every call outside the class under tests is mocked.
    1
  6.  @ContinuousDelivery  I watched and commented on the video 4 months ago. You should make another video condemning London style. If you really think why we need unit tests and what is a good unit test then you will find out how bad are London style unit tests.
    1
  7.  @PavelHenkin  ​ You got it! It is interesting how many smart developers just don't get it. It seems like Dave Farley is one of them.
    1