run
4.2.2 - Decide What Reaches You Before Everything Does - Decide which work runs unattended, what hands itself back to a person and what that person actually receives when it does.
reducing risk :: Spotting what could go wrong and shrinking the size of the bet.
run
4.1.2 - If the Secret Only Exists on Your Machine, You Are the Single Point of Failure - Decide where secrets live and how they are set per environment, with every name the code reads written down and no real value anywhere near it.
run
4.1.1 - You Haven't Finished a Deploy Until You've Practised Undoing It - Decide what triggers a deploy to each environment, how you confirm it landed and the exact route back to the previous version.
blog
Reviewing AI-Assisted Code Changes - When AI changes a lot of code quickly, review is no longer about reading lines. It’s about making sure you still understand what will happen in production.
launch
3.3.2 - Name the Risks Yourself Before Users Find Them in Production - Name the launch risk: say what might break, what would trigger it and what response reduces the damage.
build
2.2.3 - Understanding the Shape of the System Before You Change It - Map the system shape: say which part owns what, what each part depends on and where the important handoff happens.
shape
1.2.3 - The Risks You're Avoiding Naming Are the Ones That Bite You - Name the named risk: say what might fail, who or what it would affect and what action will reduce the damage.