Design decisions that leave a paper trail
Record why a choice won, and when it should stop winning.
Open field noteTHE FIELD GUIDES
Less magic prompting. More knowing what things are called. Explore examples, compare your options, and give AI a brief worth building.
12 field notes
Record why a choice won, and when it should stop winning.
Open field noteUse SOLID and GRASP to reason about change, not to win acronym bingo.
Open field noteArray012Mapkey → ValueSetABOrder, lookup, and uniqueness are different jobs.
Open field noteHeader, sidebar, grid, dialog: give your feedback coordinates.
Open field noteModel behavior and ownership before drawing a forest of classes.
Open field noteA payment button is the beginning of the paperwork.
Open field noteMatch the bill to the value. The pricing page cannot rescue the product.
Open field note‘Deploy it’ is not a complete address.
Open field noteAdd the same book twice
Turn a wish into requirements someone can actually test.
Open field notePick for authoring and maintenance, not a benchmark trophy.
Open field noteUse shared tokens so one decision stays one decision.
Open field noteStop comparing tools that do different jobs.
Open field note