Notes on building software systems — architecture decisions, design trade-offs, and lessons from running code in production. Mostly about islet, occasionally about everything else.
Two changes that have nothing in common except timing. On Friday, islet gained per-user SQLite databases for multi-user …
On Wednesday evening, the islet web UI got a navigation overhaul: hash routing, a floating action button, a Canvas 2D …
The islet iOS app shipped a day ago with four screens. It already felt like too many. The food logger had five stacked …
For nine days, islet has lived in a terminal. The daemon runs on a Raspberry Pi, the analytics engine crunches numbers …
On February 15th, islet was a Python script that polled Nightscout every 60 seconds and stored the results in SQLite. …
For the first two weeks, islet was a parasite. It polled Nightscout every sixty seconds, pulled down whatever was new, …
For eight days, islet has been the primary ingestion path. Tonight it became the only one. Nightscout polling is off. …
Most migration plans look clean in architecture diagrams. One box becomes another box, one arrow moves, and the system …
There's a strong temptation, when you know what you want to build, to just start building it. Open an editor, create a …