Live data from Hacker News

Viewing profile — evnsio

evnsio

HN member
Joined
Fri, May 03, 2019, 12:41 PM UTC
HN karma
25
Public activity
30 items

About evnsio

No profile information was provided.

Recent public activity

  1. comment
    Comment #47489475

    Just for completeness, both PagerDuty and incident.io offer EU hosting.

  2. comment
    Comment #42369000

    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. story
  4. comment
    Comment #42294040

    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 :)

  5. comment
    Comment #42192162

    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 …

  6. story
  7. comment
    Comment #42192141

    > 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 gr…

  8. comment
    Comment #40914344

    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 …

  9. comment
    Comment #40903463

    '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 signpos…

  10. story
  11. comment
    Comment #39608075

    So much lol.

  12. story
  13. comment
    Comment #34594176

    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.

  14. story
  15. comment
    Comment #33862726

    All our content lives at incident.io/blog, and is shared on Twitter, LinkedIn, etc.

  16. comment
    Comment #31789199

    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…

  17. comment
    Comment #31788791

    JJ, please :) I'm sure you folks have better things to contribute to the conversation than a sales pitch?!

  18. comment
    Comment #31788161

    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 th…

  19. comment
    Comment #31788054

    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 i…

  20. comment
    Comment #31788015

    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 differen…

  21. comment
    Comment #31764748

    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 …

  22. comment
    Comment #31655232

    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

  23. comment
    Comment #31655207

    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 differe…

  24. comment
    Comment #31290277

    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

  25. story