Beyond Compiling
Compiling freezes the decision called "the screen" into the device. Take that ice out of the screen layer, and more people — on chips and in fields — can touch it.
Vol. 2
build
- The Screen as a Resource — a Document the Server Hands Out, Not CodeFourth in the mcp_server course. The server holds the screen as a file and hands it over. Edit the file and the next connection is different, with no rebuild and no reinstall — as long as it is read on every request.DEV
- A Tool That Refuses — a Schema Is a Promise, Not a GuaranteeThird in the mcp_server course. An input schema goes on, and a handler that does not trust it. Including why "admit 0" and "admit 99" are refused for two different reasons.DEV
- On a Chip — Firmware in C, the Screen as a DefinitionPutting a screen on an eval board usually means adding a graphics stack and reflashing. Instead the board hands over its capabilities as tools and its screen as a resource. Attached to an STM32H723 on the desk, turned the LED on, and rendered the 656-byte screen the board handed over.DEV
- One Tool — the Description Matters More Than the CodeSecond in the mcp_server course. One tool gets registered. It is four pieces — name, description, input schema, handler — and three of them are read not by us but by whoever calls. So writing the description well is worth more than writing the handler well.DEV