Nate Reuck

SRE and platform engineering practitioner. Writing about what actually works in production.

Measure tokens per completed task, account for retries and tool output, and preserve the evidence an operational assistant needs.

March 14, 20264 min read

Follow evidence through technical failure and incident response, then test whether the proposed correction changes the mechanism.

February 13, 20264 min read

Use a curated notebook to compare runbooks and incident evidence, while keeping citations, freshness, and operational authority in view.

February 12, 20264 min read

When inference slows without obvious application errors, test physical constraints alongside queueing, workload changes, and software regressions.

February 10, 20264 min read

Test evidence retrieval, long-session consistency, tool boundaries, and cost before letting a model influence production changes.

February 6, 20264 min read

Define inputs, permissions, idempotency, verification, and stop conditions for one operational capability before expanding its authority.

February 5, 20264 min read

Decide which workflow deserves an agent, where a fixed automation is sufficient, and how to measure the work left for responders.

February 4, 20264 min read

Connect on-call interruptions, specialist demand, and recovery work to a concrete capacity decision using an on-call workload worksheet.

January 29, 20265 min read

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