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.
Archive
Every older note, newest first.
23 notes in all
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.
Folding a conversational search selection into a basket
Saving an option from a conversational flight search into a booking basket needed a new route: a partial update that has to merge a selection into whatever is already there. Plus privacy-aware MCP observability, Copilot context hooks and a naming cleanup.
Three race conditions in a shared release workflow
Time spent fixing a flaky release pipeline sounds like infrastructure work. Its effect on how a team works is easy to undercount.
Granular Dependabot groups and getting error attribution right
Repos got granular Dependabot grouping and a shared error library got a missing origin type.