on-call reimagined
Joey Parsons
Apr 19, 2024
If you look at the day-to-day of a typical software engineer in 2024 and compare it to ten years ago, it’s amazing to see how exponentially better things have become. From writing, testing and building code to deploying and observing in production, it’s significantly easier to build and ship products.
But there’s one glaring area that simply has not improved: on-call.
It’s still the same arcane process, dominated by anxiety and fear. Driven by ritualistic processes that take engineers away from building products for their customers. Sure, there’s been little improvements along the way and incident management has gained structure and meaning, but it’s still not good enough and we’re tired of waiting for someone to lead that evolution.
That’s why we’re building beeps.
What if you could build an on-call schedule in minutes and not the hours and days of the past? What if you had all of the context from all of your tools before you even need it? What if you only needed to handle the novel incidents and not the noise?
What if you never had to write another postmortem?
In the days, weeks and months ahead, we’ll be sharing and releasing more of what we believe will help you and your teams manage, understand, and resolve incidents faster for folks building on React-based stacks.
Naturally, we can’t do this alone and if we haven’t chatted yet, we’d love to hear your unfiltered feedback on how we’re approaching these problems and listen to your thoughts on what you’ve always hoped for when going on-call.