SRE

Writing on SRE.

Evaluate AIOps grouping by detection coverage, investigation effort, and recoverable mistakes, not alert reduction alone.

January 27, 20264 min read

Turn reliability policy into a release decision with fresh evidence, limited exceptions, and a clear path to resuming normal changes.

January 27, 20264 min read

A design guide for an incident assistant that handles duplicate events, partial failures, and reviewed AI summaries across tools.

April 6, 20254 min read

Build a view that answers who is affected, what changed, and where to investigate, then test its queries and missing-data behavior.

April 3, 20253 min read

Read validated architectures as a starting point for workload, recovery, and support testing, not a promise of automatic reliability.

April 2, 20254 min read

Check market definitions, forecast periods, and growth arithmetic before turning a market estimate into an operational investment case.

April 1, 20253 min read

A reusable prompt pattern for incident analysis, with checks for missing facts, unsafe recommendations, and unsupported certainty.

March 31, 20253 min read

Connect an SLO’s allowance to planning and release behavior, with explicit ownership, exceptions, and treatment of measurement gaps.

March 30, 20253 min read

Adapt a complete SLO record, worked budget examples, and an exception log without confusing bad requests with minutes of downtime.

March 29, 20254 min read

Use directory purpose, mount boundaries, and read-only checks to investigate missing files, full disks, and unexpected runtime state.

March 28, 20254 min read

Measure a representative workload, identify the limiting resource, and test one reversible change instead of applying a universal sysctl recipe.

March 27, 20254 min read

Design incident channels, bot actions, evidence links, and a fallback path that still works when the chat system is unavailable.

March 25, 20253 min read