GuideAI in production
NotebookLM for SRE: build a source-backed incident dossier
Use a curated notebook to compare runbooks and incident evidence, while keeping citations, freshness, and operational authority in view.
Articles
In-depth explanations, practical guides and independent analysis. Choose a topic and format to find your next read.
Guides show how. Explainers unpack a concept. Commentary makes an argument. Explore Production notes.
GuideAI in production
Evaluate Claude Opus 4.6 for operational work
Test evidence retrieval, long-session consistency, tool boundaries, and cost before letting a model influence production changes.
GuideAI in production
Agent skills for SRE: write the execution contract
Define inputs, permissions, idempotency, verification, and stop conditions for one operational capability before expanding its authority.
Sustainable on-call: make workload relief change the plan
Connect on-call interruptions, specialist demand, and recovery work to a concrete capacity decision using an on-call workload worksheet.
GuideSLOs & reliability
Release gates that hold up under incident pressure
Turn reliability policy into a release decision with fresh evidence, limited exceptions, and a clear path to resuming normal changes.
GuideIncident response
Connect PagerDuty, Jira, and Slack without losing incident state
A design guide for an incident assistant that handles duplicate events, partial failures, and reviewed AI summaries across tools.
GuideObservability
Grafana dashboards for incident response
Build a view that answers who is affected, what changed, and where to investigate, then test its queries and missing-data behavior.
GuideAI in production
Prompt engineering for operators: make evidence and limits explicit
A reusable prompt pattern for incident analysis, with checks for missing facts, unsafe recommendations, and unsupported certainty.
GuideSLOs & reliability
Error-budget template: calculations and release-policy fields
Adapt a complete SLO record, worked budget examples, and an exception log without confusing bad requests with minutes of downtime.
GuidePlatform engineering
Linux filesystem hierarchy: find the state that is failing
Use directory purpose, mount boundaries, and read-only checks to investigate missing files, full disks, and unexpected runtime state.
GuidePlatform engineering
Linux performance tuning starts with a bottleneck
Measure a representative workload, identify the limiting resource, and test one reversible change instead of applying a universal sysctl recipe.
GuideIncident response
Slack for operations: keep coordination separate from authority
Design incident channels, bot actions, evidence links, and a fallback path that still works when the chat system is unavailable.