Chasing the Flush
Walk a Michigan woodland, read the weather, and inspect what you find. Chase the morels through a short spring season, with a field notebook to record your discoveries. More seasons and species are planned.
Chase the flush →Small browser experiments documenting the movement from intuition, through conversation, into interactive form.
The small games began as experiments with the frontier AI models available when I made them. The code was entirely generated; I supplied prompts, guidance, and testing. I was the crash test dummy, curious to see what a few words could become. Read the field note →
Follow the signal. Challenge the proposal. Decide what counts as enough evidence.
Ten days of Michigan spring. A changing forest, a basket to fill, and a flush that won't wait.
Walk a Michigan woodland, read the weather, and inspect what you find. Chase the morels through a short spring season, with a field notebook to record your discoveries. More seasons and species are planned.
Chase the flush →Playable records of changing model capabilities — with known credits, later revisions, and field notes that explain what I noticed.
Ten days of spring morel season in a Michigan woodland. Read the weather, explore, inspect mushrooms, and fill your basket before the flush ends. More seasons and species are planned.
One boss, two employees, and a history that follows them into the next meeting. Shape the cast, introduce a situation, or take a seat yourself.
A gentle pixel terrarium: feed, play, rest, and grow a friendship. Your little world waits while you are away.
LoRa symbols, cyclic chirps, spreading factors, noise, and the shape of information in RF.
Reopen a question, follow a disagreement, and watch development double back on itself.
Entropy, Huffman coding, redundancy, noise, error recovery, and Shannon channel capacity.
Exploring neighborhood-owned communication and community tools.
Generation, critique, distributed roles, runtime evidence, and human direction.
A coordinate-driven cube state engine with legal turns, 25-move scrambles, an inspectable inverse-history solver, keyboard control, and explicit model provenance.
Mathematical visualization, rendering depth, navigation, and visual exploration.
Field notes from failures that became rules, decoy realities, empty rooms, and software fossils.
A river kingdom with seasonal orders, troop transfers, battle forecasts, persistent campaigns, and three paths to victory.
Game loops, particles, progression, sound, and iterative browser rendering.
The preserved Three.js version: lighting, camera controls, spatial interfaces, and an earlier generation of browser interaction.
Animation timing, state management, responsive controls, and persistent scores.
Side-scrolling motion, obstacle systems, pacing, collision, and parallax.
Not a requirement to publish. An invitation to notice something and give it a small form.
New: Repo Excavations II · I Was the Crash Test Dummy
A sentence, question, analogy, tension, or pattern that refuses to leave.
A diagram, SVG, movement, simulation, interface, or tiny system.
One idea. Self-contained. Enough code to let someone experience the thought.