“TDD Bypasses Your Brain” Bypasses Supporting Its Own Premise
From the article, bold emphasis mine:
However, developing in a test-driven way can result in an overreliance on tests: when a test starts failing (and you know the test is correct), there is a tendency to mindlessly modify code until the test passes. Furthermore, true 100% code coverage by tests is a myth: no matter how many good tests you write, not all cases will be covered. Therefore, mindlessly modifying code until all tests pass is likely to introduce new bugs for which no tests exist.
So the actual premise of the article is a tautology—bypassing your brain bypasses your brain.
Regardless of development paradigm, if you’re mindlessly modifying code until tests pass, you are programming by coincidence, and your code is likely becoming more fragile with every modification (not to mention less correct).
Understand the code you’re modifying. If you don’t understand it, then mindfully make changes to explore it, using a proper version control safety net to be sure you can discard your exploratory changes once done.
There are too many coders that spend their entire careers “hopelessly lost, but making good time”.
Don’t you be one of them.