Just a place to think out loud about building software.

  1. 4039007HEAD → main8 min

    A commit graph. The main line starts at a commit labelled postgres and passes four green commits: reads, scale, consistency and operations. From each, an amber branch rises to a label: key-value and wide-column, sharding, distributed SQL, and what you can run.

    Four questions before you pick a database

    Four questions, asked in order, three made-up systems walked through them, and a table of where the usual databases fit.

  2. 5ced4426 min

    A payment slip with its slip number and a barcode, stamped PAID in green twice, the two identical stamps side by side at different angles.

    The bill arrived twice. You should still pay it once.

    Duplicate messages are normal, even from a bank. Whoever moves the money has to catch them, and sometimes that's a vendor you can't see into.

  3. 42488605 min

    Two vendors drawn as commit lines, split into the pitch and the docs. The best pitch starts with three clean green commits, but its docs show two hollow squares, labeled missing and not ready. The hardest pitch starts as a tangled grey squiggle, labeled tiring to follow, but its docs show five solid amber squares with nothing missing.

    Being good at it is the entry fee

    Technical skill gets you in the room. How the other side feels working with you is what they remember.

  4. eafd5f95 min

    A git branch graph with seven commits on a main line, one green branch and one amber branch splitting off and merging back, and the last commit filled green.

    AI writes the code. Deciding what to build is still the job.

    In 1986 Fred Brooks split software work into essence and accident. AI is shrinking the accident to almost nothing, which makes the essence most of the job.