About this episode
Lean TDD is an attempt to reconcile some conflicting aspects of Test Driven Development and Lean Software Development.
I've mentioned Lean TDD on the podcast a few times and even tried to do a quick outline at the end of episode 162.
This episode is a more complete outline, or at least a first draft.
If you feel you've got a good understanding of TDD, and it's working awesome for you, that's great. Keep doing what you're doing. There are no problems.
For me, the normal way TDD is taught just doesn't work. So I'm trying to come up with a spin on some old ideas to make it work for me. I'm hoping it works for you as well.
I'm calling the new thing Lean TDD. It's inspired by decades of experience writing software and influence from dozens of sources, including Pragmatic Programmer, Lean Software Development, Test-Driven Development by Example, and many blog posts and wiki articles.
The main highlights, however, come from the collision of ideas between Lean and TDD and how I've tried to resolve the seemingly opposing processes.
Links:
- Lean TDD | pythontest.com
- episode 162: Flavors of TDD
- What is Test Driven Development (TDD)? | Agile Alliance
- Test First Programming / Test First Development | pythontest.com
- episode 7: The Waterfall Model and “Managing the Development of Large Software Systems”
- episode 51: Feature Testing
- The testing renaissance — Twitter Engineering blog post about Feature Testing
- Lean software development - Wikipedia
Get every episode summarized
Each time Test & Code publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.
Email me new episodesFree for 3 shows. No card needed.
Hosts & guests
No transcript yet
This episode has not been transcribed. Request it and it moves to the front of the queue.
More episodes
