Operations

Structures on-call work: timeline, blast radius, mitigations, and customer comms—so fixes stay coordinated instead of chaotic thread hopping.

Finds real bottlenecks using traces, flame graphs, and system metrics before rewriting code—so optimizations target measured latency, not guesses.

Uses extra worktrees so parallel experiments or long-running tasks do not thrash your main working tree or stash pile.

Replaces guesswork with hypotheses, tight reproductions, and evidence—so you fix root causes in production incidents, flaky builds, and confusing regressions.

Closes the loop on a branch: green tests, clean commits, push hygiene, and a deliberate choice between merge, squash, or follow-up tickets.

Runs the right checks—tests, builds, or manual steps—before claiming completion so “done” always means verified in the real environment.