Your Own Patterns

Your Own Patterns: When Repetition Becomes a Pattern: The Rule of Three, Writing a Pattern Card Your Team Will Read, A Team Pattern Catalog: Adding, Changing…

Updated

  1. When Repetition Becomes a Pattern: The Rule of Three (Journeyman): When the same solution turns up for the third time, each copy a little different, it's time to pull out its shared shape and give it a name; once is code, twice is a coincidence, and three times is a pattern worth naming, which is how every pattern in this course began.
  2. Writing a Pattern Card Your Team Will Read (Journeyman): A shared solution that nobody knows about, or knows when to use, gets copied around anyway; a pattern card says on one page what problem it solves, how to use it, when to skip it and where it's already used, so a teammate can pick it up without asking.
  3. A Team Pattern Catalog: Adding, Changing and Retiring (Freelancer): Once a team has a handful of pattern cards, they drift: two contradict, one describes how things used to be done, and new teammates copy whatever they find first; a catalog keeps every card in one place with a status, changes cards through review with a short decision record, and retires old patterns without deleting them.