Writing on software design, development, and more.

All of my thoughts on programming, product design, and more, collected in chronological order.

How I run production infrastructure as a one person consultancy

Anyone hiring one engineer has the same question and almost nobody asks it: what happens after he leaves? This is the honest answer. The two hosts, the checks that run on them, the tool I built to close the two gaps nothing else covered, and what 'supported after launch' actually means when one person is on the hook.

Building for environments you don't control

Hospital networks that allow nothing in, devices in the field you cannot brick, conformance requirements you cannot negotiate, and stakeholders who need it in plain English. What engineering discipline looks like when the environment sets the rules. From a clinical alerting platform used by NHS trusts and a fielded detection product.

Anatomy of a fixed-scope build

"Fixed scope, fixed price" sounds like a line from a brochure until you watch one run from start to finish. So here is one. Last September I built EventScope for Johnson & Johnson Medical: an engagement analytics platform that ran across their...