9 posts tagged with “Best Practices”
How to fix flaky tests: six root-cause classes, the diagnostic checklist per class, and the test-strategy fix most teams skip. Telltale log signatures for each.
Lead time for changes is simple until two managers disagree. The clock-start choice, the deployment rule, and what to do when the number is too high.
CI/CD cost per build is compute plus developer wait time. The formula, real numbers from 378 GitHub Actions runs, and why the invoice undercounts by 100×.
The real cost of flaky tests is compute reruns plus developer wait time. The maths on why every flake pays twice, what we observed, and where to start.
A CI/CD pipeline audit is a practitioner's health check, not a maturity model. The framework, what to look for, and the prioritised punch list teams act on.
Developer wait time is the biggest CI cost your team never invoices. The taxonomy, a worked example, and why it beats compute by two orders of magnitude.
Don't monitor everything that can be counted. Monitor the signals that show whether your CI, deploy, recovery, and economic feedback loops are closing.
CI/CD is not a pipeline. It is the discipline of short feedback loops from commit to customer: small batches, fast tests, real deployments that ship.
A practical guide to measuring the five DORA metrics in real CI/CD pipelines, including deployment rework rate (added in 2024). Covers the decisions to settle first, the data sources to use, and the traps to avoid for each metric.