I swear almost every critique of test driven development boils down to "I wrote a bad test".
Yet TDD has no opinion on how you design your tests. There are people who say "you must do DI if you do TDD" or "TDD must be done with unit tests" and they are wrong but that is a separate conversation.
The author seems to disagree arguing that TDD is "pressuring" him to write tests in a certain way. Bull. He made a choice.
Invariably the shitty test which you write before because you overdid low level unit testing or DI is going to be just as shitty written after the code. Maybe a hint that PEBKAC?
>It’s an intoxicating way to work, especially for someone who struggles with software engineering. It makes you feel like a good programmer
I think somebody needs to get allll the way over themselves.
Yet TDD has no opinion on how you design your tests. There are people who say "you must do DI if you do TDD" or "TDD must be done with unit tests" and they are wrong but that is a separate conversation.
The author seems to disagree arguing that TDD is "pressuring" him to write tests in a certain way. Bull. He made a choice.
Invariably the shitty test which you write before because you overdid low level unit testing or DI is going to be just as shitty written after the code. Maybe a hint that PEBKAC?
>It’s an intoxicating way to work, especially for someone who struggles with software engineering. It makes you feel like a good programmer
I think somebody needs to get allll the way over themselves.