Dev log
Blending
Eleven days, one designer and one AI coding assistant, a tile game built in small steps and logged as it went. This page is made from the git history and the AI research note.
931commits
131deploys
11days
16test files
Day by day
1 OctA paper game becomes a tile builder
- A 2018 paper game (Dragon's Lair) is rebuilt as a browser tile builder and deployed to Cloudflare the same day.
- Spec Kit, a heavy specification framework, is set up. It was later removed: too rigid for a prototype that kept changing.
- Headless bots and a simulator are written to play the rules by number.
2 to 5 OctMultiplayer, bots and triangles
- A full multiplayer game with heroes, bots, personas and a command line.
- Square tiles become triangles: each tile carries three lands, one per edge.
- A style picker is added, and the neo-brutalist look of this site becomes the default.
6 OctThe designer deletes the game
- The whole multiplayer layer, with its rules, bots and play page, is removed. Only the tile builder stays.
- It was a working game. The designer judged the small builder to be the real one.
- New tile art (Natural v3) and a pan tool for the canvas.
7 OctWater, thick tiles, a performance hunt
- A water shader, flat thick tiles, and place-anywhere rules.
- A sprite atlas benchmarked at 60 frames a second and was "a lot worse" in the designer's real window. It was reverted: measure, then believe.
- The first animals and a score.
8 OctThe builder becomes a one-player game
- A deck, 66 clicks, a combo multiplier, wild colours, and seeds so everyone can play the same game.
- A high score table on Cloudflare D1 and the hardening for a public launch.
9 OctOne rules module, replayed by the server
- The game becomes a single module that the page, a command-line player and the server all run.
- The server replays every submitted score, so a score cannot be faked. Replays and a demo play back saved games.
- Stats rows, full screen, and replay speeds.
10 OctThe map, the double game, music
- The top-ten demo, a pirate-map ending, install as an app, and a double game with its own board.
- Music on the beat: a jukebox, a MIDI reader and a song player. The AI cannot hear, so the designer judged every sound.
- WebGL hardened against a lost context, and the AI research note begins.
11 OctGlass
- The map's fade tuned by feel, then new ways out: a fold, a roll, a slide, a spin, a drop.
- The double game goes public, the leaderboard keeps its top three each day, and the demo gets a VCR with speed dots and a record button.
- The glass look of the VCR becomes the theme for the leaderboard and the menu. A "?" opens the three steps, then the mission.
- The mission is rewritten in the designer's words: the interface is an open lie, an experiment in using addictive design for good. All text becomes OpenDyslexic, with a slight shadow.
- A slip: a deploy from a copy of this home page overwrote the real one, because both shared a worker name. It was found from a screenshot, restored, and the real project was renamed to stevebassoli.com so there is one source.
- This dev log.
What the AI research found
- A command-line player running the same rules as the page and the server let the AI explore the game from the inside, and made server-side checking of every score possible.
- Photographs of the paper game were a fast way to prototype.
- A heavy specification framework cost many tokens and made a changing prototype too rigid. It was removed.
- Measure before believing: a benchmark said 60 frames a second, the real window said otherwise.
- The designer decided every balance question and what to cut. The AI typed and checked.
- Every claim was labelled checked or unchecked. The most useful sentence in the AI's replies was where its checking stopped.
- A human gate on deploys, plus a rollback log, made fast shipping safe.
- Small, atomic requests, checked on the page while the designer watched, beat any plan.
How it works
- The designer asks for one small change. The AI makes it in the most direct way and shows it on the real page.
- The designer looks, and says "confirm" or what is wrong. Then "harden" adds one check. Then "deploy".
- Every deploy adds an entry to the research note, with the designer's words and what stayed unchecked.