Pipeline as Code
The pipeline becomes reviewable, which is the point. It also becomes branch-specific, which is both the feature and the trap.
-
-
Build Agent
A build agent runs code written by whoever can open a pull request. That makes it a trust boundary, not a piece of capacity.
-
Infrastructure as Code
Every console edit is a promise broken to the next person who reads the repository and believes it.
-
Feature Flag
A release toggle that outlives its two weeks has stopped being a delivery tool. It is now a permanent branch in your code.
-
Reproducible Build
Timestamps, locale, build path, and map iteration order are enough to make two builds of one commit differ. None of them is in your code.
-
Environment Promotion
A promotion claims the only thing that changed was configuration. It is worth exactly as much as that claim is actually true.
-
Build Artifact
A version number can be issued twice. A content digest cannot, which is why deployments should refer to the digest.
-
Six Weeks of Waiting, Two Days of Work: Software Delivery as a Flow
The change took two days to write and six weeks to reach a user. Nobody was idle, and that is exactly the problem worth understanding.
-
Small Batches
If a release costs two days of coordination regardless of size, batching a quarter of work into it is the sensible choice. Fix the cost, not the habit.
-
Value Stream Mapping
Nobody in the organization can see the whole flow. That is not a failure of attention — it is why the map has to be drawn by a room, not a person.
-
DORA Metrics
Most dashboards still say four keys and MTTR. Both are out of date, and the replacement measures something slightly different.