Skip to content

Writing

Notes from seventeen years of building and running software

Long-form engineering notes — on designing software that is pleasant to operate, running Linux in production, and the decisions behind the products I build. Newest first.

Engineering

Designing software that strangers can upgrade

Anything a released version reads at runtime is a contract with the future. What Nibble taught me about upgrades — a release that can't know its own future address, why merging git history was the wrong model, and checksums that refuse to destroy your edits.

Read

Linux

A lock screen that cannot lock you out

Theming a login screen means writing to system directories as root; theming a lock screen means one bug can lock someone out of their own machine. How Darwan handles both — a supervised lock, and a root helper that trusts nothing it is given.

Read

Security

Security that lives in the browser is decoration

Nibble's Control Plane locked itself after fifteen idle minutes — and a page reload walked straight back in. Two humbling fixes, and the sysadmin's rule behind them - enforce where the state lives.

Read

Product

Why this site runs on a CMS I built

Every developer eventually writes a content management system. I did it on purpose, after years of installing, patching and rescuing other people's. These are the decisions that made Nibble — and the one I got wrong first.

Read

Engineering

Your own website is the best test suite

One evening of clicking around my own documentation produced seven patch releases of Nibble. Fixtures with three files never find what real content finds — and some bugs only show up when you actually run the thing.

Read

Engineering

SQLite is enough (for most of us)

For most of my career, "which database?" meant "which database server?" Today my default is a file. Here is how to run SQLite in production properly — WAL, backups, honest limits — and when to move on.

Read