Going nano with software updates
My latest
DirectorPlus column interviews Chainguard VP Dustin Kirkland on why software upgrades should be microscopic.
What does it mean to go nano with your software updates — to "carve with a scalpel" instead of swinging a hammer? For my latest DirectorPlus piece, I caught up with Chainguard VP Dustin Kirkland to dig into that idea.
In general, software stacks really varied these days, each relying on a mix of different major and minor versions of open-source languages, frameworks, and OS-level infrastructure. And, these components are releasing new versions at a fast rate.
Doing one one-size-fits-all, major version upgrades all at once is a quick way to break things. "Breakages are inevitable," says Kirkland. "I’d rather stub my toe than break my leg."
Dustin and I had a great conversation about the benefits of microscopic updates, the downsides of large-scale batch upgrades, and how teams can actually put this approach to work. (Including the leadership mindset required to do it well).
If you're an engineering leader, definitely consider
signing up for DirectorPlus for a monthly check-in with an experienced director, VP, or CTO on a new subject!
Other Blog Posts
