The launch month. It opened with five pieces.
What went out
| Date | Track | |
|---|---|---|
| 01-08 | Horizon | The Age of Install-less Apps |
| 01-09 | Build | A First Screen in Ten Lines |
| 01-15 | Build | An LCD Maker Builds an HMI in 30 Minutes |
| 01-20 | Field | The Little Thing Made on a Weekend |
| 01-23 | Build | Handling State |
It opened with one sentence
Do not burn the screen into the device; define it on the server. That was the whole of the launch proposition, and the other four pieces were that sentence handled by hand.
In the ten-lines piece the screen definition came in at nine lines, 848 bytes. The point is that those nine lines live on the server, not in the client — you do not build or install to change a font size.
The state piece took the next question. Who holds the number on the screen? If the screen holds it, two panels show different numbers. The counter has to hold it.
This month's finding
One thing confirmed while building the first-screen piece. If the host builds the screen itself and the text claims it came from the server, a capture cannot tell them apart. So verification looks for widgets in the host code. One occurrence and it fails.
Still open
- "Say it and it becomes a screen" — the conversion from a person's words into a definition. In all five pieces that step was done by hand
- Offline and caching — behaviour while the connection is down is untouched
- Elapsed time — "thirty minutes" and "a weekend afternoon" differ by whoever builds it. From next month we count lines instead of hours
Next month
On to what compiling freezes, and whether removing that ice from the screen layer alone lets more people touch things — on a chip and in a field.
makemind.dev "Signal" — the 2026-01 close.