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

One open file, a tray of half-made thumbnails, and two names for the same pixels. Three things programming languages can now help us keep straight.

Read the essay
Three photographs of a diving kingfisher hang above a developing tray.
Illustration generated with GPT Image

Pages from the notebook

43 of 132 essays

43 essays found. Page 3 of 4.

  1. The page before CSS

    A billing-page inventory becomes a usable hierarchy by grouping related facts, promoting the routine action, and separating destructive account changes before CSS adds polish.

  2. The catalog dreams in i32

    Guarded While reveals how a hundred distinct grammars are constrained by one small expression language and an i32 WebAssembly result.

  3. 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.

  4. The mercy merge

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

  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. 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.

  8. 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.

  9. 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.

  10. Advice after the warning

    Accessibility guidance becomes useful when reviewers separate requirements from design judgment and leave developers with a next action instead of a vague veto.

  11. The future has plaque

    Technological progress keeps expanding what we can do, but living systems still demand the same repetitive care every day, because maintenance is a permanent condition of the body rather than a bug waiting to be patched.

  12. Polish does not compile

    Polish makes a terrible programming language because too much of each sentence lives outside the text, in the speaker and the conversation.

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.