You clearly are unable to understand Test Driven Development.

Even though TDD uses very simple concepts, a lot of developers are unable to understand what TDD is. And this is the biggest critic to TDD.

In my opinion it is a psychological limitation, definitely not a limitation on the ability to understand things.

This also means that not every company can afford TDD.

The fact that you first write 1 (and only one) test before writing any production code, it is because you want to reason on how the code should look like from a user point of view. The question you answer is "If the code were already written, how do I expect to use it?"

When we use a library we expect it to be simple and effective. The same concept is applied in TDD but in details and not just to the public interfaces exposed to the users.

Finally, there is another important concept: Test Driven Development is NOT ABOUT TESTING! It is about WRITING CODE.

After all for senior programmers implementation is , most of the time, just a detail.

Many people speak about K.I.S.S. principle... but they fail to understand that simple refers to how you use the code, not how you write it. T.D.D. is about writing K.I.S.S. code.

But some programmers are unable to move from details to the above picture. This is not necessarily bad, because after all when need a lot of programmers able to understand every detail.