Ok beyond the "test first, then test guiding then Red green refactor" stuff : what is the fuss all about?"

In this hands-on we'll cover that, we'll cover why to do TDD even if you're doing a hackathon and throwing away the code: TDD as socratic dialogue, tdd as mindfulness, the design goals behind the tool.

To do that I'll start by showing you how I teach TDD to people (so, if you are a beginner you are also welcome), slowing down in each part and doing techniques of lazy-naming, branch reduction, purposeful-bad-faith, etc

Then we shall dive into the why.