2 ms·
I think there really needs to be a separate acronym from CD to better distinguish deployment from delivery (similar to authn v. authz in security nomenclature).
by devonkim 9y ago
I think there really needs to be a separate acronym from CD to better distinguish deployment from delivery (similar to authn v. authz in security nomenclature). Nobody with the right mindshare seems to have made this a priority though because automated deployments are probably not cost-effective in many organizations but delivering a change, however, is something that has solid value everywhere. Coming up with a change ticket with the impact of a change and what’s typically paperwork in many places absolutely has value and will help people move faster with lower risk while making management feel like they have control (because most continuous code based controls of delivery mechanics tend to be more democratic in practices, not manager-oriented). Maybe it could be CDD (continuous delivery description) vs CDE (continuous delivery deployment)?
- hinkley 9y agoI hold that on a well functioning team the mid level developers are delivering most the the code. The senior people are dealing with clearing roadblocks and cross cutting concerns like stability, security or performance. This is not a blame the victim structure. It’s more like a pedestrian version of NASA’s incident system. To do this the process needs to be self service. You can find mid level people pretty easily. Anyone who wants a promotion or become an SME should have tools to do a lot of that work themselves instead of having to extract it from the leads or follow the School of Hard Knocks. Good automation supports this, bad automation makes this harder.