Journal
Field notes
Short pieces from application analytics work — how we read latency, set timeout budgets, and prepare for reliability assessments.
How to read p95 latency without panicking every spike
A short field guide to separating noisy percentile bumps from genuine integration degradation when you watch API latency day to day.
Read note
Setting timeout budgets for partner APIs you do not control
When a third-party API is slow, your timeout policy decides whether users wait, fail fast, or retry into a worse outage.
Read note
Error budgets that integration teams will actually follow
Availability targets only help if product, platform, and partner owners share the same burn-rate language.
Read note
What to prepare before an API reliability assessment
A practical checklist so the measurement window starts on day one instead of week two.
Read note