Comments by "Nick" (@NicodemusT) on "Do People HATE Test Driven Development (TDD)?" video.

  1.  @uome2k7  Do people purposely avoid acknowledging the huge gaping holes in this theocracy? A lot of bugs are unexpected user input/data. What you just wrote is that –– the source of the majority of bugs can't be tested in a way that prevents a bug. This is what my whole point is. What is the point in writing a test, if it doesn't cover the real world. As I mentioned before, video games written in the 80s/90s had very little bugs –– games made today have untold bugs. Guess what generation leaned on TDD? I think TDD is a crutch that people use to justify other bad practices. TDD isn't hard, it feels like meaningless data entry work – something to do on sleepy Mondays. I might as well be writing "A = 1, B = 2, C = 3". Front end user testing – I'll do that all day, every day because it's actually results-driven, and reflects what a user is actually doing.
    4
  2. When mocks resemble actual data, then TDD is worthwhile, otherwise, I’m just testing hope. This is the problem with these conversations that no one addresses. So far anyone going off about TDD never have to consider actual data. Saying if you don’t like TDD that means you must not know it - is in itself ignorance. TDD pretends that decades of software development doesn’t exist prior to its existence. Nintendo games in the 80s/90s were made with ZERO TDD, today games are made with TDD. Guess which generation has way more bugs? This is true in most computing. What if you were to say, videos created for YouTube needed to be encoded in a very specific way - to save power consumption and to improve the viewability for colour deficient people, you need to use a different colouring for your video. Or else, don’t publish videos. Would you have improved engagement? Yes. Would you have improved accessibility? Yes. Is everyone going to have the time to do that, even if it «  saved more time in the future »? No. With AI, we’re just hammering on an old rock here. Learning TDD is a dead art in short time.
    3
  3.  @andrealaforgia7699  I've used it. Complex production code? Sure. The vast majority of projects are not that, though, and TDD becomes something you do just virtue signal to others that you "do TDD." Pacman and Call of Duty? Could you possibly pick a bigger straw man? Try programming an NES game in C, and compare that to building something in Unity or Unreal Engine. Christ. What a straw. This is a dishonest conversation to begin with. I've been to plenty of dev shops and tech companies. This idea that everyone uses TDD all the time is easily disproven by just walking the floor of any tech company. You'll be surprised that some people just write software and get deadlines done. This idea that bugs are more time than updating hundreds of tests is crazy, delusional nonsense that isn't backed up by what people actually do.
    3
  4.  @c00ckiez  You said it better.
    3
  5.  @varshard0 then why even bother with TDD if you’re admitting the coverage is loose?
    2