Comments by "" (@defeqel6537) on "TDD Is A BROKEN Practice" video.

  1. TDD works poorly for visuals, but it still works well for testing the ViewModel / Controller logic
    4
  2. When most professors misunderstand what a Unit Test is, often have no idea about SOLID principles (whatever your opinion on them are), etc., how do you expect them accurately convey TDD?
    2
  3. Personally, the thing I like the most about TDD is that I can have simple TODO list commented in the test code, and just pick the next thing to test and implement, and as I find new edge cases I just add them to the list instead of worrying about them (edit: that is to say, I feel like I accomplish something by taking stuff off the list, and I also feel like I accomplish something when discovering new requirements that I add to the list)
    2
  4. I guess BDD somewhat addresses that?
    1
  5. Do you need much actual logic behind the UI exploration? Just explore it separately, and when you've decided, add tests to control logic that the data, that is to be shown in UI, is loaded correctly. If your UI is dependent on the rest of your application existing, you have a design problem.
    1
  6. Nah, Scrum is better than Waterfall, and DOES have some useful concepts (though not unique to it), but I cannot say it is especially great "in full". The Story Point concept is especially harmful, since it is a waste of time beyond "tiny", "I can do this", "who knows", and easy to misuse (and yes, this is a problem of the process)
    1
  7.  @davetoms1  yeah, technically they aren't part of the modern Scrum, but in practice are always there, whether we are talking about abstract points, days, hours, whatever (edit: and to highlight why it is less of an issue in modern Scrum is that it recommends breaking the backlog into tasks taking one day or less, while before it just recommended estimating tasks and filling the sprint using those estimations)
    1
  8. I often do this with new code as well
    1