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

Astra and Opus 5.5 make me think AI acceptance in games is close: stronger tools are giving people with visual taste a shorter path to something worth playing.

Read the essay
A hand adjusts a brass spotlight over a miniature lighthouse and sailboat, with a second lamp and a small paint box nearby.
Illustration generated with GPT Image

Pages from the notebook

43 of 131 essays

43 essays found. Page 2 of 4.

  1. Let the easy fight live

    Simple encounters give players room to recognize, practice, recover, and feel strong, so complexity works best as paced escalation rather than a quota every room must satisfy.

  2. Please, sir. I’m tired.

    Codex usage limits have been reset for outages, launches, milestones, cache bugs, vibes, and literal RESET week until the exception became a public ritual.

  3. In defense of long hallways

    Quiet traversal, recovery rooms, and measured repetition give players time to predict, recover, and notice what the next burst of action will cost.

  4. Raise another bar

    When one game-development discipline outruns the rest, another week of polish buys less than a small pass on the weakest player-facing channel.

  5. Make the game answer

    A small indie scene can feel connected when one action produces immediate feedback, persistent state, a later world response, and enough quiet for the player to notice.

  6. Combos and conversations

    A game feels coherent when actions combine into readable consequences, the world answers back, and clarity and pacing give both enough room to land.

  7. Evidence belongs in the result

    Three programming-languages papers ask what inspectable evidence must accompany a bug report, a parallel-cost bound, or a generated test.

  8. The edge case has a derivation

    Reducing JavaScript’s [] == ![] produces a deterministic chain of coercion rules and identifies where code should reject the default conversion.

  9. Accessibility as creativity

    Three aggressive redesigns of one event page leave its accessibility tree untouched — which is exactly what frees them to be aggressive.

  10. A problem worth the tokens

    Agent work earns its cost when the system carries a case to an externally verified result or a precise escalation.

  11. A template can say no

    A useful design template records the audience, decision, hierarchy, and vetoes that make a polished output fit its task.

  12. The tree before the pixels

    An accessibility snapshot exposes the headings, labels, form, and button that a screenshot-matched checkout can lose before semantic HTML repairs them.

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.