This looks more like an argument against unit testing than TDD itself. In any case, given the power of modern mocking tools and/or following the Chicago school of TDD, the potentially negative impact that you are talking about can be very small or even non-existent.
I am glad to hear Chicago is winning. I would agree that my arguments have little to do with TDD and apply equally to writing unit tests. This is because I focus mostly on making readable code not comments or tests.
You're balancing pros and cons all day, the TDD approach (or any approach) shouldn't be followed without consideration to what you are giving up.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This looks more like an argument against unit testing than TDD itself. In any case, given the power of modern mocking tools and/or following the Chicago school of TDD, the potentially negative impact that you are talking about can be very small or even non-existent.
I am glad to hear Chicago is winning. I would agree that my arguments have little to do with TDD and apply equally to writing unit tests. This is because I focus mostly on making readable code not comments or tests.
You're balancing pros and cons all day, the TDD approach (or any approach) shouldn't be followed without consideration to what you are giving up.