Book: Test Driven Development: By Example - Kent Beck
September 30th, 2015

Problem: dependency
Symptom: duplication
Write failing test BEFORE writing any code
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
Pattern: Make the change easy. Then make the easy change. copy
This post was referenced in:
- Journal: Object Calisthenics + TDD + Advent of Code - day 1
- Journal: Object Calisthenics + TDD + Advent of Code - day 1
- Pattern: Make the change easy. Then make the easy change.
- Pattern: put a bad feeling into a test
- Pattern: Triangulation
- Pattern: Obvious Implementation
- Pattern: Fake it until you make it
- Practice: Object Calisthenics + TDD + Advent of Code
- Video: TDD, Where Did It All Go Wrong - Ian Cooper
- Journal: Object Calisthenics + TDD + Advent of Code - day 2