Engineering · Operations
Practical pieces on running on-call without burning out the team, picking an alerting tool without paying per seat, and writing escalation policies that survive contact with reality.
A practical sequence we walk customers through to leave PagerDuty without dropping a single alert — services, schedules, escalation policies, integrations and the dual-fire sanity window.
Six rules we landed on after running on-call for a 4-person ops team for two years — primary/secondary handoff, weekend rotation length, the «follow the sun» trap, and how to compensate for it.
Why a Telegram VoIP call is the cheapest reliable way to wake on-call without per-message carrier fees, what it costs at scale (spoiler: nothing) and the failure modes you have to wire around.