Intermediate. Assumes working knowledge.
192K views12 years ago2 recommendations
Tools and practiceSoftware designTestingSoftware architecture
Martin Fowler, Kent Beck, and David Heinemeier Hansson debate the tradeoffs, benefits, and design impacts of test-driven development.
"TDD as One True Way" versus "TDD as devil-spawned tempter" is not a productive contrast. Most of us have similar goals for development: confidence, impact, challenge, belonging. Test-driven development is one path toward these goals, but there are many other paths. This conversation in six parts explores tradeoffs in development, places TDD in those tradeoffs, and gives you perspective with which you can decide for yourself how you want to program. Speakers: Martin Fowler Kent Beck David Heinemeier Hansson (DHH)What people say. Recommended as a nuanced debate on when to use test-driven development and how to approach mocking.
ollysbon Hacker News • Recommends
On “Ask HN: How do I start with test driven development?”
szalanskyon Lobsters • Recommends
ChrisGaudreauon Hacker News • Mentions
On “The DHH Problem”
ailideexon Hacker News • Mentions
On “Ask HN: What prominent and high profile companies use TDD?”
dhzhzjsbevson Hacker News • Mentions
On “Unit Testing is Overrated (2020)”
MarquesMaon Hacker News • Mentions
On “Ask HN: In these uncertain times, how do you handle anxiousness”
u/sam-the-unsinkablein r/dotnet • Mentions
On “With Dependency Injection, does every single class in use need to be injected? How do we combine this with the Clean Code principle of many small classes?”
u/sliderhouserules42in r/dotnet • Mentions
On “Is Automapper the most hated library?”
u/sliderhouserules42in r/dotnet • Mentions
On “Is Automapper the most hated library?”
u/sam-the-unsinkablein r/dotnet • Mentions
On “Why shouldnt you use repository pattern”
