Pioneering

Notes from active builds: the design decisions, war stories and how-it-works of whatever I'm making right now.

A secret scanner failed a merge request over a test key and a documentation PEM that the change did not contain. Scoping a scan properly.

Building on your own framework means finding its gaps as a user rather than an author, and having to file the request against yourself.

A wedding photo culler that contains no machine learning at all, by deliberate choice. Blur, exposure and eyes, done with plain arithmetic.

A tool-failure log dumped a wall of Go stack frames where one line would have done. What a log record owes the person reading it.

Reviewing a scaffolder turned up a command name that quietly conflated two different things. A flag and a setting are not the same object.

An AI repair agent declared success the moment the code compiled. The linter disagreed, and the gap between those two is the whole story.

An audit found that a Cobra option had never been enabled, so the root command hooks had silently not run on any subcommand for months.

A generated nested command would not compile, and the cause was a scaffolder handing every call the same key regardless of depth.

Building an AI dungeon master to test a Go chat client, and the bug that kept resurrecting a goblin the player had definitively killed.

Generate an asymmetric RSA-4096 signing key inside AWS KMS with no export path, then sign releases by calling kms:Sign instead of holding the key.