Skip to content

Still Brook.

Observations & other curiosities

Notes on software
and the things
we make.

Open the notebook
An engraved computer on spindly legs beside a brook, with a bird, a leafy twig, and a curling paper tape.
Fig. 01 — A machine for wandering thoughts.

Latest essay

A couture show has two customers for each camera frame. The archive wants every stitch. The backstage monitor wants whatever just happened. Jai and Goose put a very different price on that handoff.

Read the essay
A model in a pleated red coat turns on top of a film camera.
Illustration generated with GPT Image

Pages from the notebook

107 of 133 essays

107 essays found. Page 7 of 9.

  1. The backend developer costume

    Programmers turn languages and job titles into moral ranks because managed cloud primitives have made ordinary application backends embarrassingly small, and the resulting status theater distorts hiring, reviews, and architecture.

  2. The mercy merge

    Pity merging substitutes sympathy for evidence, moving an exhausted pull request into main before its known defects have earned approval.

  3. Following the wire

    Bend becomes understandable once its HVM output is read as an interaction-calculus wiring diagram whose independent active pairs can reduce in parallel.

  4. The proof budget

    Types are useful proofs when they encode stable, expensive invariants at compositional boundaries, while stronger proof languages trade automation and ergonomics for richer claims.

  5. Print the path

    Temporary print statements solve many bugs because they capture a rerunnable chronology with less setup than an interactive debugger.

  6. Friction where damage starts

    Developer tools prevent predictable errors when the safe path stays easy, damaging actions demand explicit intent, and escape hatches still expose the model programmers need to learn.

  7. Functions need spaces

    Snake case makes function names readable verb phrases by writing word boundaries explicitly instead of asking capitalization to impersonate punctuation.

  8. Leave the scar visible

    Workarounds need angry comments, ugly names, and explicit exit conditions so later maintainers recognize debt instead of inheriting it as design.

  9. The locker at the corner

    Poland’s parcel-locker ecosystem beats Amazon’s captive delivery model by separating where you buy from where and when you receive.

  10. Poland in cat ears

    The Polish catgirl-programmer stereotype comes from overlapping internet visibilities rather than evidence that Poland produces unusually many gender-nonconforming developers.

  11. Types considered harmful

    TypeScript becomes dangerous when you silence honest absence with plausible defaults that satisfy the shape and corrupt the meaning.

  12. The guild and the commons

    Programming-language communities place the cost of learning either on entrants or on stewards, and each choice can harden into a status system.

A note in the margin

A little curiosity goes a long way.

Still Brook is an independent journal about software, systems, and the quiet decisions that shape what we make.