A tool that detects potential signs of overwork in incident responders, which could lead to burnout. To compute a per-responder risk score, it integrates with Rootly, PagerDuty, GitHub, and Slack.
In my experience as a former SRE currently working for an incident management SaaS (Rootly).
Two main reasons:
1) The status page update is not automated. It takes time for the incident management process to go through all the steps and updating the status page is generally not the first one. It's often an overlooked one.
2) The company would rather not communicate that they are/were down, or they are not yet sure of the impact, and therefore don't yet have the correct information to share.
Of course, all modern incident platforms will offer tools to update your page super easily/in real-time. But tooling is generally not the main issue; it's process/information.
A burnout detector for SREs. The goal is to help teams identify incident responders who may be overworked/getting burned out.
We are looking at:
-Objective data: signals from incident management tools (Rootly/PagerDuty), GitHub, and Slack
-Self-reported data: asking the engineers how they feel via short survey
From this, we generate a CBI score (Copenhagen Burnout Inventory). We're still in beta, but we've received positive feedback from our beta testers, especially from manager of large and distributed orgs.
Same here. They have a known bugs where entries will vanish from your contacts. Data loss is a big deal (or so I thought).
Support asked me to let them know when a contact vanishing did so they could gather logs from me phone.
Once I was finally able to see it happen, I reached out. Reported that it had just happened overnight. The customer support said it was too long of a time frame for engineers to investigate because "it generates a lot of logs and that's too much to go through". I could not believe their answer.
I just moved my contacts to Gmail and that was the end of it.
I live in Florida. Both my neighbor and I lost our hive q few weeks apart. It happened very quickly and what the article mentioned is most likely what they got. We knew about the sharp die-off across the U.S. so decided to hold off bee keeping until it is figured out.
I have experienced data loss with Apple and the support team telling me the knew about it but could not pinpoint the issue.
I had entries disappearing from my Contacts (iCloud). The customer support asked for me to get back when I notice the issue so they could get logs to debug. My best friend contact entry disappeared overnight. I called the representative the day of and told him that the contact disappeared between yesterday night and today morning. His answer was that I needed to pinpoint more accurately when the contact disappeared, because iPhone generates a lot of logs and and engineers don’t have time to go through them. Ah!
Needless to say I stopped storing my contacts with iCloud and my trust eroded. “Funny enough” I also had issues with my Health data, years of it disappeared. Support could not do anything. The data magically came back a month later or so.
AI-powered on-call and incident response. Beautiful, modern, and Slack-native incident management—from your first alert to retrospective. Trusted by 100s of leading companies, including NVIDIA, Squarespace, Canva, Grammarly, Elastic, Tripadvisor, and Figma.
The publishing industry is in big trouble; journalists are fired, and publications are closing.
Ads are not enough, and readers are fed up with ads, so they use adblockers, cutting publications' revenues. With AI chatbots, people browse these publications even less, further reducing revenues.
Paywall and licensing content is the next best option, if not what it is?
Just wanted to chime in and say that I think you are both right. I haven't thought of a way to square this circle yet. I find this issue to be the fundamental concern around generative AI. Of course the Courts could always end up saying its fair game and at that point, I could see OpenAI no longer paying. And then content producers are more likely to gate content in a myriad of ways and the cat and mouse game will continue. I could also see the US say scraping is allowed and EU saying otherwise.
It seems to me that half the closures happen after some wealthy ass hole that seems to hate journalists buys a publication then runs it into the ground.
publishing indstury maybe be in trouble, but publishing itself is not.
content creators are going direct to consumer with their content, and there is endless opportunity for actual content creators to thrive without publishing houses as middlemen
We offer both a hosted version (https://oncallburnout.com/) and a self-hosted one (https://github.com/Rootly-AI-Labs/On-Call-Burnout-Detector).