Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
evnsio
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
evnsio
6mo ago
Just for completeness, both PagerDuty and incident.io offer EU hosting.
2.
▲
by
evnsio
2y ago
Took the time to read the 84 page report that was published last month, and write up a summary. Pretty interesting bug, with a pretty significant impact.
3.
▲
by
evnsio
2y ago
Definitely reads like it. And FWIW, I do think incident.io is unique(ly great), but it has nothing to do with it functioning entirely within Slack :)
4.
▲
by
evnsio
2y ago
It sounds like marketing, I know, but this was written by engineers and practitioners, and is a pretty comprehensive overview how modern tech orgs are dealing with incidents these days.
5.
▲
by
evnsio
2y ago
> Humans aren't great at incident response, and we all hate waking up at 2am to resolve an issue. Agree that most people hate being woken at 2am, but disagree that humans aren't great at incident response. Speaking generally, I
6.
▲
by
evnsio
2y ago
As the person who originally wrote the Monzo Response project ( https://github.com/monzo/response ), I expect you'll find some traction in smaller orgs, but when folks start doing things at scale they'll hit an
7.
▲
by
evnsio
2y ago
'Fun' is a little strong, but I really wish more companies adopted this kind of workflow for TF. Being forced into a world of full-TF or fully-manual sucks, and the lack of signposting when you're in a blended world of manual
8.
▲
Shifting left on incident management
(incident.io)
3 points
by
evnsio
2y ago
|
0 comments
9.
▲
by
evnsio
3y ago
So much lol.
10.
▲
by
evnsio
4y ago
Tweet author here, and founder of a startup. I know this is isn't revolutionary, but I've iterated towards this state and now find it a critical part of my daily process.
11.
▲
My system for staying on top of to-dos
(twitter.com)
1 points
by
evnsio
4y ago
|
1 comments
12.
▲
by
evnsio
4y ago
All our content lives at incident.io/blog, and is shared on Twitter, LinkedIn, etc.
13.
▲
by
evnsio
4y ago
This is something we spoke about in https://incident.io/blog/on-call-at-incident-io . Specifically: > On-call payment is not expected to cover any time you spend working outside of hours. If you're paged and end
14.
▲
by
evnsio
4y ago
JJ, please :) I'm sure you folks have better things to contribute to the conversation than a sales pitch?!
15.
▲
by
evnsio
4y ago
When you say there's 2-3 devs who can actually fix issues, is that because there are only 2-3 devs, or do you have more people available but they don't know how to fix? Assuming the latter, my suggestion would be: 1) Setup a weekl
16.
▲
by
evnsio
4y ago
It's hard to assess on-call comp without the context of pager load, stage of company and a myriad of other factors. We've done some research from the market though, and have some interesting results we'll be sharing soon! (se
17.
▲
by
evnsio
4y ago
I don't disagree with your points, and having worked at both massive IT organisations, tiny startups and scale-ups in-between, it's clear that different organisations need different levels of rigour and process! I see the guide le
18.
▲
by
evnsio
4y ago
Hey folks! One of the founders of incident.io here, and the one who's face is on the front cover :) I've written this content so many times at companies I've worked at in the past (though not to this quality!) so it's re
19.
▲
by
evnsio
4y ago
Oh and if you're not in the market to buy something, I open sourced the tool I originally wrote at Monzo: https://github.com/monzo/response
20.
▲
by
evnsio
4y ago
Hey folks. Co-founder of incident.io here. Firstly, thanks for the kind words Quentin – appreciate it, and congrats on your progress so far. incident.io is pitched slightly differently to Rootly, insomuch as we're not building an engin
21.
▲
by
evnsio
4y ago
One day locked in my home office to record a sub-ten minute demo, and it wasn't without it's challenges as you can see
22.
▲
Recording product demos is hard
(twitter.com)
2 points
by
evnsio
4y ago
|
1 comments
23.
▲
by
evnsio
5y ago
Hey folks, author here. I work in the field of incident management and get to work with a lot of startups who are looking to put good practices in place early on. There's been a common theme across them of over complicating things, rel
24.
▲
The startup guide to sensible incident management
(incident.io)
3 points
by
evnsio
5y ago
|
2 comments
25.
▲
Five steps to better customer communication
(incident.io)
2 points
by
evnsio
5y ago
|
0 comments
26.
▲
Learning from incidents in Formula 1
(incident.io)
2 points
by
evnsio
5y ago
|
0 comments
27.
▲
Response – Monzo's incident response and reporting tool
(github.com)
2 points
by
evnsio
7y ago
|
0 comments