jjtang1

8 ms·

61.
by jjtang1 4y ago
I LOVE this. Ironically having good tooling is the least important element in a successful incident response program (but it does help). Motivated people and a good process far supersedes tooling. And yes so certainly see room for this. We
62.
by jjtang1 4y ago
Thank you! We built out our own Workflows engine that makes our life significantly easier. This way different customers can use the same integrations N number of ways without us needing to bake in a default configuration. Otherwise we'
63.
by jjtang1 4y ago
The messaging for "managing incidents on Slack" is a lot easier to understand and digest we found than something like "all-in-one incident management platform". We have an entire Web platform that performs the same funct
64.
by jjtang1 4y ago
Rootly would address that problem, we keep a database of all of your incidents and metadata (impact, timeline, participants, metrics, etc.) on our Web platform separate from Slack. You can customize a data retention policy with us if you wa
65.
by jjtang1 4y ago
One of my favourite sites! And that is great, we know plenty of happy Blameless customers, they're certainly one of the better ones in the market we compete against.
66.
by jjtang1 4y ago
Thank you for the feedback. Actually we did offer a free plan for up to 5 users and even 10 at one point. What we've found is the collaboration overhead during incidents at companies at that scale wasn't too useful and pivoted awa
67.
by jjtang1 4y ago
Totally agree, we do offer a 14-day free trial here if you want to give it a go: https://rootly.com/users/sign_up . This feedback is helpful, I think we can make that a bit more obvious on our website!
68.
by jjtang1 4y ago
Appreciate the feedback here. We'll look into what we can do to help you make a more informed decision around the financial cost structure and how that works before deciding to try us.
69.
by jjtang1 4y ago
Yup that is a very good point. We make Slack even stickier for their customers and ours alike.
70.
by jjtang1 4y ago
Indirectly, their automations are less incident management/process focused but more on remediation (e.g. run A to restart db). Whereas ours are more focused around e.g. updating status page automatically, inviting responders, posting r
71.
by jjtang1 4y ago
Oof, thank you for the feedback. We certainly don't want that happening. We'll look into adding greater transparency that works for our model so you can make a better informed decision upfront.
72.
by jjtang1 4y ago
Appreciate the kind words and agree on fit. Happy to compare notes and stay in touch if you'd like to connect of course jj@rootly.com.
73.
by jjtang1 4y ago
Appreciate the feedback! You could certainly go through a checklist/runbook that got attached to the incident. This is usually the setup most companies we speak with have. However, compliance, consistency, and speed on following that d
74.
by jjtang1 4y ago
Thank you! You're not alone, I've ran into quite a few cases where working from a thread will suffice (big and small companies). We are still team dedicated incident channel but there are a few things that threads do better. For e
75.
by jjtang1 4y ago
Thank you! And yes the space is heating up for sure. Really good awareness and attention developing as a result though. We are also noticing monitoring companies starting to snag up companies to developing into this space (e.g. Datadog htt
76.
by jjtang1 4y ago
Appreciate the feedback!
77.
by jjtang1 4y ago
Thank you for the feedback, a calculator is a good suggestion! We realize there are a fair number of people that will be turned away by this, we'll see what we can do for a better middle ground.
78.
by jjtang1 4y ago
Thank you for the kind words, Alex. The whole team over at Gemini has been such a treat to work with. The collaboration on building new features together is what really excites us. Appreciate you always pushing us to be better. I feel like
79.
SRE vs. Platform Engineering – Differences Explained(rootly.com)
3 points by jjtang1 4y ago|0 comments
80.
The Pros and Cons of Embedded SREs(rootly.com)
3 points by jjtang1 4y ago|0 comments
81.
Building an incident management company by ex-Instacart(rootly.com)
3 points by jjtang1 4y ago|0 comments
82.
Rootly (YC S21) Is Hiring for Developer Relations(ycombinator.com)
1 points by jjtang1 5y ago
83.
by jjtang1 5y ago
This is quite interesting, I didn't think of this type of approach. When I was at Instacart I could have seen this being really useful. I always had IC eng ask me "why does my work matter".