The origin story of my first button to shutdown a system.
Written by @sghill, who works on build, automated change, and continuous integration systems.
How support questions turn into high-leverage features.
Can our systems build confidence from config alone?
What is it like to get paged?
Build ashtrays when you cannot prevent or fully support uses of your platform.
Do our plans pass a quick time check when considering implicit commitments?
A walkthrough of our Jenkins 2.332.x upgrade, including plugin risk assessment and mitigation.
When plans fail repeatedly there are often better bets to make.
By designing development workflows for the work, we can make the output high-quality by default.
The story of Jenkins Plugin Skew. Observe reliably to make consistent progress with big problems.
Deciding against work that aligns with your values is difficult, but blindly saying yes is worse.