You are probably right. The only hint that I give about that is: "Writing the test before the code".

TDD is strange. You can define it very quickly: 1) Write the test until it fails, 2) Write the code until it passes the test, 3) Clean both codes and repeat. But you need years of practice to really understand it.

If you are interested, I have several more stories about that. Including my latest one, Now TDD is More Important Now Than Ever, in which I explain how we can use it to make the AI (aka GitHub Copilot) to collaborate with us effectively.

But you are really right, I am avoiding doing a short introduction about what is TDD, because it would be a copy and paste in too many stories :/

I have to guess how to handle it.

Thanks for the feedback Robert!