1 min read
1 min01 · 1 MIN READ
Where systems break
A component exists twice: once in the design file and once in the code. The moment those two drift, every downstream decision has to guess which one is authoritative.
02 · 1 MIN READ
Components in practice
- Name the component identically in both places
- Ship states, not just the happy path
- Make the accessible version the default one
- Delete anything nobody has used in two quarters
