From merged pull requests to a performance review
Merged pull requests already record what you did. Turning them into a work log with an LLM is easy; the hard part is the defensive rules that stop it corrupting the vault.
Engineering
26 notes filed here
On console warnings and the things we don't remove
Removing unused documentation tooling and fixing prop type warnings: small changes that don't ship features but keep the console's warnings meaningful.
Three kinds of drift: currency, ghost flags and passenger types
A currency display bug, a feature flag that never existed in the flagging service, and a passenger type code nobody resolved: three kinds of drift that fail silently.
The shape of shared libraries
A shared library is defined by the shape it presents to its dependents. Two cases make that concrete: an icon component used through an undeclared path, and a one-line logging change that broke a numeric assumption.
Three bugs hiding in a cross-service feature
Building a feature across four services meant coordinating an AI backend, a fare search service, and two frontend components. Along the way: a silent configuration bug, a duplicate event contract, and an HTML injection path.
The scaffolding tax: getting a new service properly bootstrapped
Bootstrapping a new service from a template isn't just renaming things; it's wiring it into the deployment pipeline, getting dependency management right, and building the scaffolding that makes all future work faster.