I will write sops, standard operating procedures, runbooks and process documentation

At three in the morning nobody reads a wiki page. They follow steps, or they improvise, and improvising is how a small incident becomes a long one.

I am a software engineer. I write the procedure the person on call can follow without knowing the system.

WHAT YOU GET

When to run this, and when not to

Pre-checks: what to confirm before touching anything

Numbered steps with the real commands, not a description of them

Verification: how you know it worked

Rollback, or an honest statement that there is none

Escalation: who to wake, and when

WORKS FOR

Failovers, restores and restarts

Deploys, releases and rollbacks

Onboarding and offboarding

Backups, certificate renewals, scheduled maintenance

Any process that today lives in one person's head

HOW IT WORKS

1. Tell me the process, or walk me through it on a call

2. I write it, then hand it back as a dry run you can test

3. We fix the steps that turned out to be ambiguous

If a step only works because someone knows a trick, that trick goes in the document.

Scrivimi pure in italiano.