sjwhitworth

5 ms·

1.
Building On-call: Our observability strategy(incident.io)
2 points by sjwhitworth 2y ago|0 comments
2.
What a 2024 data stack looks like(incident.io)
2 points by sjwhitworth 2y ago|0 comments
3.
by sjwhitworth 3y ago
Hey, incident.io CEO here. I'm sorry to hear that. Can you explain a little bit more?
4.
by sjwhitworth 3y ago
Thank you: let us know what you think!
5.
by sjwhitworth 3y ago
Hello: incident.io CEO here. Thank you for the kind words, it's much appreciated. I countersign your last point around business value being in incident response. There's truth to this: as with all new product categories, there&#x2
6.
by sjwhitworth 3y ago
Hello Rootly CEO! Worth disclosing next time you post, I think
7.
by sjwhitworth 3y ago
incident.io CEO here! This is such a cool and unique usecase. Love it.
8.
by sjwhitworth 3y ago
Hey, incident.io CEO here! Thanks for mentioning us.
9.
Learning from incidents is not the goal(incident.io)
3 points by sjwhitworth 3y ago|0 comments
10.
Postmortem on downtime due to handling of Go panics(incident.io)
1 points by sjwhitworth 4y ago|0 comments
11.
by sjwhitworth 4y ago
Hey, incident.io CEO here. Glad to hear you’re happy with the product. The people at Grafana are great - congrats on the launch! Will have to take the product for a spin sometime :)
12.
by sjwhitworth 4y ago
Hey JJ. Appreciate the hustle, but please disclose that you're supporting your own product here (disclosure: I'm the incident.io CEO)
13.
How DORA will impact incident management at financial entities(incident.io)
2 points by sjwhitworth 4y ago|0 comments
14.
by sjwhitworth 4y ago
CEO here! Indeed we did :)
15.
Incident.io Raises $34M(incident.io)
5 points by sjwhitworth 4y ago|2 comments
16.
Handling third-party provider outages(incident.io)
1 points by sjwhitworth 4y ago|0 comments
17.
How to get everyone at the company to value writing(incident.io)
6 points by sjwhitworth 5y ago|1 comments
18.
The importance of clear writing in product development(incident.io)
1 points by sjwhitworth 5y ago|0 comments
19.
by sjwhitworth 5y ago
Hey. Author here. We thought we'd open source our interview process in the hope that it helps others. We've made a few deliberate tradeoffs here in terms of sharing questions, and the process up front with candidates. It's wo
20.
Our engineering interview process(incident.io)
4 points by sjwhitworth 5y ago|1 comments
21.
by sjwhitworth 5y ago
We use Goa at incident.io. It's excellent — provides a real boost to our speed, and allows us to skip a lot of non-differentiated work.
22.
The things we find hardest in incident response(incident.io)
20 points by sjwhitworth 5y ago|1 comments
23.
Now you see me, now you don't: feature-flagging with LaunchDarkly(incident.io)
4 points by sjwhitworth 5y ago|1 comments
24.
by sjwhitworth 5y ago
For now, yes. We'll be fixing this over the next month or so, but we've been focusing our engineering time on product and have kept our landing page since we launched.
25.
by sjwhitworth 5y ago
Hey, one of the co-founders here! Thanks for posting it. Feel free to sign up for a free trial, no credit card required at incident.io
26.
The things we find hardest in incident response(incident.io)
1 points by sjwhitworth 5y ago|0 comments
27.
by sjwhitworth 5y ago
I asked Tom for some of this advice earlier this year. Glad to see he wrote it up into a blog post — it's really useful!
28.
Tom (Monzo) thoughts on early stage fundraising(docs.google.com)
3 points by sjwhitworth 5y ago|0 comments
29.
Do I need an incident debrief?(incident.io)
1 points by sjwhitworth 5y ago|0 comments
30.
Postgres sequences can skip 32 unexpectedly(incident.io)
134 points by sjwhitworth 5y ago|79 comments

More ›