sjwhitworth
What a 2024 data stack looks like
There's truth to this: as with all new product categories, there's some education that needs to go along with the sale, and budget that needs to be found, that doesn't currently exist. On the whole, we haven't found this to be a large challenge so far. Most people look at our product, see a very fair exchange of value, and are happy to pay.
However, that isn't why we built On-call. We built it - along with many other reasons - because it's part of the trifecta that we think you need to do incident response well:
1. A way to alert people that something is wrong 2. A way for them to respond, resolve and learn from the incident 3. A way for them to communicate to their customers about it
We have built all of these respectively in On-call, Response and Status Pages. Consolidating all of these into one cohesive product makes obvious sense, to us at least. We'll see what the market says!
Learning from incidents is not the goal
Postmortem on downtime due to handling of Go panics
How DORA will impact incident management at financial entities
Incident.io Raises $34M
Handling third-party provider outages
How to get everyone at the company to value writing
The importance of clear writing in product development
We've made a few deliberate tradeoffs here in terms of sharing questions, and the process up front with candidates. It's worked well so far, but we'll see how it goes.
Our engineering interview process
The things we find hardest in incident response
Now you see me, now you don't: feature-flagging with LaunchDarkly
Feel free to sign up for a free trial, no credit card required at incident.io