>Read any advocacy of TDD and it will always boil down to an argument for testing itself, which nobody argues against. It never makes a case for writing tests before implementation.

It seems the author hasn't read many cases about TDD, which could be evidence they haven't learned much about it.

For example, from Martin Fowler[1]: "The second benefit is that thinking about the test first forces you to think about the interface to the code first. This focus on interface and how you use a class helps you separate interface from implementation."

[1]https://www.martinfowler.com/bliki/TestDrivenDevelopment.htm...