@sowmyanair
Frontend Engineer
Ex-service company, now product. Focused on reliability and DX. (tamil/kannada)
We ran into this around image uploads on a quiet Sunday incident. Docs helped humans. Generated types caught the breakages in CI. Schemas still drift when several repos move at different speeds. Hand-written wrappers stayed flexible and hid mismatches. The noisy diffs were worth it once a breaking change never shipped. We kept the generator and deleted the duplicate sample clients.
I used to think more indexes always meant faster queries. Production taught me about write amplification and table bloat instead. We had three indexes that nothing queried, slowing every insert. EXPLAIN ANALYZE finally showed which plans actually used which indexes. After dropping the dead ones, writes got healthier without hurting reads. Now I review unused indexes in the same ritual as reviewing slow queries.
No spike in CPU. Error budgets looked fine at a glance. Users still reported blank pages in a thin slice of traffic. Logs only showed upstream resets with no clear application exception. The culprit was a stale keep-alive timeout between nginx and the app. Aligning idle timeouts stopped the intermittent 502s within an hour. We also added a dashboard for upstream reset reasons so the next page is faster.