Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Why TDD is a dangerous sect

9e9c31ccda3071a0448aef383d16fcd3?s=47 sharnik
April 20, 2012

Why TDD is a dangerous sect

A presentation about that looks in a critical way on common TDD propaganda.

9e9c31ccda3071a0448aef383d16fcd3?s=128

sharnik

April 20, 2012
Tweet

Transcript

  1. Why TDD is a dangerous sect Friday, April 20, 12

  2. Why TDD is a dangerous sect Friday, April 20, 12

  3. TDD zealots Friday, April 20, 12

  4. @josevalim Friday, April 20, 12

  5. TDD ? BDD Friday, April 20, 12

  6. TDD ? BDD I don’t care Friday, April 20, 12

  7. Why TDD is a dangerous sect Friday, April 20, 12

  8. TDD is about writing tests Friday, April 20, 12

  9. TDD is about writing tests NOT Friday, April 20, 12

  10. TDD is about writing tests FIRST Friday, April 20, 12

  11. @fxn Friday, April 20, 12

  12. Programming, Motherfucker Friday, April 20, 12

  13. TDD speeds up development Friday, April 20, 12

  14. TDD speeds up development NOT Friday, April 20, 12

  15. TDD actually adds 30-50% time overhead Friday, April 20, 12

  16. TESTS are the best tool for bug removal Friday, April

    20, 12
  17. unit tests integration tests pair-programming code review Friday, April 20,

    12
  18. unit tests integration tests pair-programming code review Friday, April 20,

    12
  19. unit tests integration tests pair-programming code review Friday, April 20,

    12
  20. unit tests integration tests pair-programming code review Friday, April 20,

    12
  21. unit tests integration tests pair-programming code review Friday, April 20,

    12
  22. code review Friday, April 20, 12

  23. unit tests 35% integration tests 30% pair-programming 30% code review

    60% Friday, April 20, 12
  24. TDD is Agile Friday, April 20, 12

  25. TDD projects are NOT Agile Friday, April 20, 12

  26. Individuals and interactions over processes and tools. Working software over

    comprehensive documentation. Customer collaboration over contract negotiation. Responding to change over following a plan. Friday, April 20, 12
  27. Individuals and interactions over processes and tools. Working software over

    comprehensive documentation. Customer collaboration over contract negotiation. Responding to change over following a plan. Friday, April 20, 12
  28. TDD forces good code design Friday, April 20, 12

  29. TDD forces good code design NOT Friday, April 20, 12

  30. TDD forces a design Friday, April 20, 12

  31. Thinking causes good design Friday, April 20, 12

  32. One last thing Friday, April 20, 12

  33. Remember: Test code is just code Friday, April 20, 12

  34. Questions? Friday, April 20, 12