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 1 of 4.

  1. The menu owns the clock

    Weapon wheels, command menus, quick swaps, and live inventories change how much time the player has to choose, so selection UI belongs in combat pacing rather than outside it.

  2. Defense should buy something

    A successful block, parry, dodge, or dash should change the next moment by buying time, space, position, posture damage, or initiative instead of only postponing the same pressure.

  3. The attack starts before the hit

    Startup, contact, and recovery form one readable action; animation, sound, and effects should tell the player what is coming before damage asks for an answer.

  4. Keep the threat where you left it

    When enemies leave the frame, predictable positioning and layered cues preserve the player's mental map; a warning arrow cannot repair a threat that moves in ways the camera hides.

  5. Lock-on schedules the crowd

    Target lock changes movement, framing, and how aggressively untargeted enemies can behave, so encounter design has to decide what the lock means before tuning the crowd.

  6. The bug queue needs provenance

    SQLite fixed enough AI-discovered bugs to headline patch releases while moving machine reports into their own forum, because maintainer attention became the scarce part of bug finding.

  7. A waypoint is part of the level

    Navigation markers change what players have to read in the world, so guidance belongs in level design instead of arriving afterward as a neutral HUD layer.

  8. Camera control costs a thumb

    A player-controlled camera consumes input and attention, so 3D games should decide what that extra verb contributes before treating free look as a default.

  9. Failure needs a short commute

    When a game expects repeated failure, retry boundaries should return players to the skill they are learning unless the wider reset changes enough to make the next attempt new.

  10. Recovery sets the rhythm

    Recovery mechanics teach players when to press, retreat, or reset, so health and ammo systems have to reinforce the tempo a combat game claims to want.

  11. Give the enemy one job

    Readable enemy roles let encounter designers build complexity through composition instead of packing every possible pressure into every unit.

  12. A gazillion tokens later

    Prompting becomes productive when a vague idea collapses into a small building block with a chosen quality, a reference point, a harness, and a finish line.

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.