Comments by "MrAbrazildo" (@MrAbrazildo) on "The 3 Types of Unit Test in TDD" video.

2:30, I think this is the weak point of TDD - I'm not used to it, though. To me, it seems to damage the flux of thinking the design, in trade of giving a solid ground at each step. But I do reckon that if the thinking is too foggy, TDD may help.
2
@antoruby You are talking about unity tests, which test results from an f(). TDD is meant to write a test before writing each line of code ! That's why it's supposed to help in developing anything. This may be true, if your boss wants you in front of computer all the time - leading to health issues, btw. I use to take a walk, and come back with the solution or the path straight to it, most of the time. Sometimes, when I'm inspired, I rather write directly something that I think is promising. It starts with a mess, but has a direction, and some unity tests can fix the route. TDD may slow any of these alternatives.
2
@antoruby The design of an f() has a bunch of lines that you are keeping in mind, for some time - the algorithm. TDD may damage this thinking, due to slowing the process and loosing focus, making you forget the idea, confuse some of them, and so on. I foresee this kind of issue - I may be wrong, though.
1