Field notes

Notes from Python automation consulting on real operations floors — exceptions, handoffs, and the boring details that keep night leads calm.

What belongs in an ops runbook (and what does not)

A runbook for operations automation should tell a night lead how to start, stop, and recover — not restate the project charter.

Some workbook habits encode vendor quirks on purpose. Automating them blindly freezes a bad compromise.

Running old and new paths together only helps when someone owns the comparison — and knows when to stop.

File names and function names are part of the handoff. Clever abbreviations punish the next shift.