-
Case study #0001
The blueprint comes first, and the world is a layer over itHow a system begins as one page naming what it holds and what it needs from the world, and how declaring each need as a shape with a default lets the real thing be swapped in by one line, so a feature ships before the world is ready for it.
-
Case study #0002
State is a record of what happenedOne table of things that happened, the words the people and the code share, and the work of drawing the lines between the aggregates before the store makes them permanent.
-
Case study #0003
Every state is drawn, and the match is exhaustiveA screen cannot stand in a state it has not drawn. The kernel cuts the unions, a leaf renders each member, the wrapper is nothing but an exhaustive match, and an absence is a value rather than a null.
The other lessons are still being written up. Leave an address and each one comes to you the day it is out.