Skip to content
alzy.kr
Alzy Classic Games

Devlog

Notes on the decisions behind the games I build at Alzy, and why I made them. Less about what shipped, more about why it was built that way.

What this log keeps

What I write here isn't a changelog announcing what shipped. It's a record of the decisions I made and why I made them. Reverted work gets the same space as new features — a decision I undid usually comes with a reason I couldn't see while I was building it, and that reason is worth keeping for the next call.

Each entry names a date and, where relevant, a game, so you can tell exactly which point in the code a post is grounded in. I write from the actual commit and the actual code at that point, not from a memory of how it felt.

How this differs from the guides

The guides hand a player a ruler to hold up against the board in front of them — which move pays off, what to prioritize. This log covers the other side of that table: my own calls as the person building the game — what effect to add or cut, which number to tune, what to push to later.

So the same game ends up with two different readers. The guides are written for someone playing it; this log is written for someone building something like it, or thinking about it.