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.
How do you get people to see the light?
Imagine a world where it was easy to convince everyone that your new insight was great. We'd never get anything done.
Adventures in DevOps 121: Reducing On-Call Engineer Burnout with a Volunteer Management InfrastructureDave Mangot
Brian Scanlan explains how Intercom increases efficiency of on-call engineers and reduces the disruptive nature of the job.
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.
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.
Don't hire until you've identified your actual bottleneck
There many ways to identify bottlenecks, some more formal than others. Here are a few simple patterns to watch for.
New hires means more overhead
Lines of communication go up as team size increases, but that's not all. Consider merge conflicts.
Why hiring more devs can hurt, instead of help
"Ramp up" time means we always pay an onboarding "tax" when adding a team member, which hurts productivity before it helps it.
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.