Book: Test Driven Development: By Example - Kent Beck




Problem: dependency
Symptom: duplication

  1. Write failing test BEFORE writing any code
  2. Remove duplication

get to green ASAP, quick&dirty:

tests driving code:

Results:
  • organic design
    • vs over-engineered code
  • courage
    • vs fear
    • rest between
  • self testing code

Split up
  • design
  • getting code to work
because they are conflicting activities



comments powered by Disqus