TDD: Beyond the intro, part one - Romeu Moura - DDD Europe 2023

Domain-Driven Design Europe 2023
dddeurope.com - / ddd_eu - newsletter.ddd... / domain-driven-design-e...
Organised by Aardling (aardling.eu/)
Beyond the "red green refactor" loop of test-driven development: what is the fuss all about?"
In this session we'll cover why you should do TDD, even if you're doing a hackathon and throwing away the code. We'll look at the design goals behind the tool.
TDD as socratic dialogue;
TDD as mindfulness;
Testing as reasoning.
To do that I'll start by showing you how I teach TDD, slowing down in each part and doing techniques of lazy-naming, branch reduction, and purposeful-bad-faith.
Then we shall dive into the why.
About Romeu Moura
Endless conversation - with friends, compilers - on art, equivocacy, Symmathesy, methods, absurdism, dialectic, paradigm jumps, serendipity.
Watch part two here:
• TDD: Beyond the intro,...

[@Verber0n]

Romeu is a great speaker. Part two is also great.

[@PaulSebastianM]

I dare say, developers that understand what Romeu is saying here and people that don't understand, is how you can probably tell apart developers that write high quality code from those that don't, at least in 2/3rds of the cases. I've seen what developers that jump to coding first produce and what developers that first ask questions, ask for help, for discovery sessions, for design meetings, for feedback, produce. And it's miles apart.

[@PaulSebastianM]

A good reason to defer naming with TDD is that TDD is an exploratory process. The reason to do TDD is not to be left with a bunch of tests that assert the correctness of your code. That is something only business could engrain in you. The reason to do TDD is to explore ways to shape the code you want to write. It's like testing the materials you have, figuring our what you have to work with and how you might envision piecing the final parts together. There might be many ways, but you have to figure out one way that could possibly work well enough and that you would like to work on. In that process you are going to throw away a lot of things as you explore. Spending too much time on naming things correctly will then make TDD seem like a huge waste of time. Which is probably why so many devs think that TDD is a waste of time. Spending time on naming things is part of design. Naming a test is not part of design. An exploratory test is not part of the final system design. You spend time naming, e.g. your classes, not you tests. Don't spend design time on naming tests. You're not designing tests unless you're QA. But once your design solidifies and it's ready to be deployed, feel free to rename your tests so that other developers can more easily learn and understand the system as well as more easily understand your changes.

[@kashnigahbaruda]

Why talk so fast? Speak slower please.

[@Channelcustomization832]

You can adjust Playback speed to your needs