February set up one metaphor — compiling freezes the decision called "the screen" into the device.
What went out
| Date | Track | |
|---|---|---|
| 02-05 | Horizon | Why We Gave Up Compiling |
| 02-12 | Build | On the Chip |
| 02-19 | Field | Thirty Years of Farming Onto One Screen |
What has to stay frozen
The point of the metaphor is not "thaw it all." The real-time loop, the drivers and the safety clamps all have to stay frozen. What thaws is one layer: the screen.
The chip piece showed that boundary in hardware. An eval board hands over two tools (led.set, sys.info) and one screen definition, and the drawing happens outside. The other things the board can do — erase flash, change the clock, drop into the bootloader — are not on the list, and what is not on the list has no name to call.
This month's finding
From the field side: while attaching growing records to a screen, values like averages were made computed rather than stored. A stored average starts being wrong the moment one record is corrected, and nobody notices.
Still open
- Real hardware — this month's chip piece ran on a simulator. Attaching a board on the desk is still ahead
- Swapping parts — whether the rules survive a sensor being replaced with another model was not tested
Next month
On to equipment that already knows how to talk — instruments speaking SCPI — and to the claim that eight tenths of a tool is already in your hands.
makemind.dev "Signal" — the 2026-02 close.