Blueprint Driven Development, or how I wrote code using TDD in the era of AI and didn't die [ukr]

In the era of artificial intelligence, writing code has become easier than ever. The milkman no longer delivers milk, and the baker no longer bakes bread — everyone is generating code. But what about the quality of that code? We used to write automated tests to ensure quality, but do we still need them if AI supposedly knows best? In my opinion, unit tests and similar automated checks have never been more important than they are now, because we need to control what is written not only by AI, but also by the milkman, the baker, and even your team lead.

I will demonstrate in practice how to effectively use TDD (Test-Driven Development), explain why most developers misunderstand this technique, and prove that tests themselves are not the main goal — you should focus on planning and architecture. And that’s just the beginning. You will also learn:

• The best practices for writing unit tests, how to distinguish a good unit test from a bad one, and why it’s important to review not only code, but also tests.
• How to make AI write code properly from the start.
• How discipline and common sense improve code quality, calm your nerves, and give you confidence in the future.