Slow stable releases or fast unstable releases?
The real choice: Big pile of poo, or small, managable piles of poo?
Question to readers: What are the challenges of incremental software delivery?
What makes working on the single most important, small change you can do, a challenge?
Audience question: What will be delivered when?
How do you create a plan for a team as to what will be delivered when?
How my web site mirrors software delivery
Several software delivery principles are widely applicable, beyond the strict definition of "software".
Why continuous deployment is better for emergencies
Multi-stage software delivery means no hotfixes, or lots of extra work.
You don't always need to measure a metric to improve it
You don't need a dashboard until the difference you're trying to measure is too small to be casually obvious.
Why would you ever need to deploy new features multiple times per day?
That's not why we do CD. When using CD, large features are typically behind a feature flag.
Subscribe to the Daily Commit
Every day I write about improving software delivery at small companies like yours. Don't miss out! I will respect your inbox, and honor my privacy policy.Unsure? Browse the archive.
Large batches obscure your bottlenecks
Are things moving slowly, but you don't know why? Reduce your batch size.
Adventures in DevOps 120: DevOps Research and Assessment (DORA) Metrics with Dave Mangot
Dave Mangot joins Adventures in DevOps to share how he leverages DORA metrics to improve technology organizations.
Can we use a staging environment with trunk-based development?
Push to your staging branch as needed, but don't make it a mandatory step toward production.
The problem with "DevOps" (and what happened to the podcast?)
Imagine telling your CEO, "What you need is some DevOps." How would that go?