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.
3 notes filed here
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.
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.
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.