Pipeline as Code
The pipeline becomes reviewable, which is the point. It also becomes branch-specific, which is both the feature and the trap.
-
-
The File That Says What Exists: Infrastructure and Configuration as Code
Your code says what should exist. The state file says what the tool believes exists. The cloud knows what actually exists. Three answers, one system.
-
Secrets Management
Secrets have a lifecycle: creation, rotation, revocation, expiration. Most organizations implement creation and hope.
-
Infrastructure as Code
Every console edit is a promise broken to the next person who reads the repository and believes it.
-
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.
-
DataOps
Treating analytics as code, versioned and tested. The practices are borrowed from DevOps; the hard part — who owns which number — is not a tooling problem.