28 notes
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.
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.
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.
Time spent fixing a flaky release pipeline sounds like infrastructure work. Its effect on how a team works is easy to undercount.
Repos got granular Dependabot grouping and a shared error library got a missing origin type.
A booking interface was showing a queue warning banner after it should have disappeared. The fix was small; the pattern behind it, state nobody clears, turns up across long-lived interfaces.