I Broke Production at 2 AM: How AI Agents are Fixing Post-Mortems

I Broke Production at 2 AM: How AI Agents are Fixing Post-Mortems

Source: YouTube · AI Native Dev · published Mar 11, 2026 · 22:45

Incident Response
No ratings yet Log in to rate
Transcript Available
Description

This video focuses on improving incident response through process-oriented post-mortems rather than blaming individuals 0:09-0:16.

Key Takeaways:
• Things go wrong in production environments, but the focus should be on processes that enable these situations rather than individual mistakes 0:01-0:16
• The speaker built a rich text editor specifically designed for writing incident post-mortems 0:28-0:35
• Merlin, the presenter, comes from a design background and is a front-end leaning product engineer who co-founded Mode at Work 0:44-1:01

The presentation emphasizes how proper incident analysis tools can help teams learn from failures without assigning blame to individuals.

Sources:

  • 0:01-0:16 Introduction to incident response philosophy
  • 0:28-0:35 Building a rich text editor for post-mortems
  • 0:44-1:01 Speaker background and expertise

Generate CPE Credits

Generate a professional CPE document from this video's transcript.

Estimated credit: 0.5 CPE hours

Estimate uses the video runtime (1 hour ≈ 1 CPE, rounded to the nearest 0.5, minimum 0.5, maximum 2.0). The final amount can be lower after review, never higher.

Topic: Incident Response. Commonly maps to: Security Operations, Security Assessment and Testing. Exact CISSP domains are assigned during generation.

CISSP Domain Mapping
Learning Objectives
Self-Assessment Questions
PDF Export Ready

Free account. One generation at a time, with a daily limit.

CPEBuddy is independent and not affiliated with or endorsed by ISC2, ISACA, or any certification body. Exports are formatted for common CPE submissions; acceptance is at your certification body's discretion.

Watch on YouTube

Transcript Preview

First 800 characters of the transcript

yeah, I don't know if anyone noticed, but things go wrong all the time. Anyone ever broken production? instead of kind of identifying things
that individuals did wrong. we focus on processes
that allow these situations to arise in the first place. Oh, no. Oh! So I'm going to be discussing how we built a rich text editor incident,
for writing post-mortems. But before I kind of get into that,
I'll, add some context about what instant IO does, what postmortems are, and how all
these things kind of relate to each other. So, yeah, a bit about me.
My name's Merlin. I actually come from a design background
originally and accidentally found my way into tech. Some sort of a front end
leaning product engineer. Some career highlights for me. Co-founded and led engineering,
mode at work, which was rec…