HackerTrans
TopNewTrendsCommentsPastAskShowJobs

sylvainkalache

no profile record

Submissions

Small PR Rule Won't Survive AI

blog.quent.in
3 points·by sylvainkalache·vor 2 Monaten·0 comments

Stop trying to review AI's code faster: bet on rollback instead

rootly.com
1 points·by sylvainkalache·vor 2 Monaten·1 comments

Adding week-long deferrals to a pipeline that handles alerts

rootly.com
2 points·by sylvainkalache·vor 2 Monaten·0 comments

Quick thoughts on GitHub CTO's post on availability

surfingcomplexity.blog
2 points·by sylvainkalache·vor 3 Monaten·0 comments

The quiet disappearance of the free-range childhood

bigthink.com
259 points·by sylvainkalache·vor 3 Monaten·282 comments

Two Mornings a Day

blog.quent.in
1 points·by sylvainkalache·vor 3 Monaten·0 comments

AI agents are scrambling power users' brains

axios.com
5 points·by sylvainkalache·vor 3 Monaten·0 comments

RSA 2026: The Great Cooking

vibecoded.vc
1 points·by sylvainkalache·vor 3 Monaten·0 comments

Former Azure Engineer Alleges Manual Fixes, Firefighting Threaten Reliability

windowsnews.ai
1 points·by sylvainkalache·vor 3 Monaten·0 comments

Lots of AI SRE, no AI incident management

surfingcomplexity.blog
2 points·by sylvainkalache·vor 3 Monaten·1 comments

AI for software developers is in a 'dangerous state'

theregister.com
6 points·by sylvainkalache·vor 4 Monaten·0 comments

The Cost of "We'll Fix It Later"

thereliabilityengineering.substack.com
1 points·by sylvainkalache·vor 4 Monaten·0 comments

Disappointing People Early

log.andvari.net
2 points·by sylvainkalache·vor 4 Monaten·0 comments

Fixing Claude with Claude: Anthropic reports on AI site reliability engineering

theregister.com
2 points·by sylvainkalache·vor 4 Monaten·0 comments

What I'm Learning from Aviation About Incident Preparedness

uptimelabs.io
2 points·by sylvainkalache·vor 4 Monaten·0 comments

The Picture They Paint of You – AI SREs

ferd.ca
4 points·by sylvainkalache·vor 4 Monaten·0 comments

Watts, Water, and Carbon: What Your AI Prompts Cost

blog.quent.in
3 points·by sylvainkalache·vor 4 Monaten·0 comments

Honda is killing its EVs

techcrunch.com
374 points·by sylvainkalache·vor 4 Monaten·880 comments

One More Prompt: The Dopamine Trap of Agentic Coding

blog.quent.in
2 points·by sylvainkalache·vor 4 Monaten·0 comments

Show HN: On-Call Health – spot burnout before it hits your engineers

github.com
2 points·by sylvainkalache·vor 4 Monaten·0 comments

comments

sylvainkalache
·letzten Monat·discuss
Rootly | Design, Engineering, GTM, Legal, Product, Sales| Hybrid (Toronto), Remote (APAC) | Full-time

We provide an on-call, incident management, and AI SRE platform. We are used by companies like NVIDIA, LinkedIn, and Dropbox.

We are a YC S21 company with ~100 employees and are very fast-growing. We have 15+ open positions.

https://rootly.com/careers#open-roles
sylvainkalache
·vor 6 Monaten·discuss
If the future of software engineering is SRE, because GenAI is taking care of coding, a similar trend is coming for SRE-type work.

It's called AI SRE, and for now, it's mostly targeted at helping on-call engineers investigate and solve incidents. But of course, these agents can also be used proactively to improve reliability.
sylvainkalache
·vor 8 Monaten·discuss
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.

We offer both a hosted version (https://oncallburnout.com/) and a self-hosted one (https://github.com/Rootly-AI-Labs/On-Call-Burnout-Detector).
sylvainkalache
·vor 8 Monaten·discuss
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.
sylvainkalache
·vor 10 Monaten·discuss
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.

It's fully open-source, you can test it out locally https://github.com/Rootly-AI-Labs/rootly-burnout-detector-we...

Alternatively, we offer a hosted version with mock data, allowing you to play with it. https://www.oncallburnout.com/

If you have any feedback or ideas, shoot them my way :)
sylvainkalache
·vor 10 Monaten·discuss
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.