Tag: #incident
Writing on GPUs, LLMs, MLOps, Kubernetes — and mindset · 4 posts
The Order of Operations After a Mistake — Contain, Report, Record, Prevent
The cost of a mistake is set not by the mistake itself but by the four stages that follow it, and people invert that order in almost exactly the same way every time: hunting for the cause instead of stopping the bleeding
2026-08-16 · 13 min read #career#workplace#mistakes#incident#accountabilityKorean Dev Blog Curation 2 — Incident Retrospectives and Troubleshooting, 12 Posts I Opened and Checked
The genre Korean developers write best is the incident retrospective. Twelve posts: p6spy silently defeating read/write datasource routing, why an HTTP timeout does not cover DNS resolution, a TCP half-close disguised as
2026-08-12 · 12 min read #curation#큐레이션#troubleshooting#postmortem#incidentIncident Communication: Talking Through an Outage
When an outage hits, the technical fix is only half the job. This post covers the Incident Commander role and role separation, the status-update drumbeat you keep even when there is no news, the three questions every upd
2026-06-24 · 13 min read #incident#oncall#communication#sreMigration Incident Case Studies and Checklists — Learning from Others Failures
Migrations are among the most common and most painful sources of outages. This article walks through typical failure modes like lock storms, replication lag, data loss, and irreversible changes, derives causes and lesson
2026-06-16 · 14 min read #database#migration#postmortem#incident#reliability