Journal

Notes from the work

We write when we've learned something worth passing on.

Build for the phone people have, not the one on your desk

Most performance advice assumes a fast device on a fast network. Here is what changes when you design for a mid-range Android on patchy data.

An honest account of what drives the cost of a build, written from the side of the table that produces the estimates.

Domains registered to a former developer, hosting nobody can log into, source code that was never handed over. This is more common than it should be.

What it means in practice to build software that expects the connection to disappear, and why the pattern is worth the extra work.

We're asked for rebuilds constantly. A fair share of the time, the honest recommendation is a much smaller piece of work.

Start here

Most of what we know doesn't make it into writing. Tell us what you're working on and we'll share what's relevant.