Re:Continuous Deployment
by ghurlman on Saturday February 12, 2011 @03:24PM
(#2211033)
More likely, the developer can handle the tech pressure, but having his/her manager FREAKING OUT and over his shoulder asking questions the whole time is what really causes the slowdown.
[ Parent
| on HN ]
Step 0. in getting started with continuous deployment is having an organization that doesn't lose it's mind every time there's a blip.
That often means you need managers who are especially good at (or at least dedicated to) deflecting the freak out/crazy.
CD won't increase your changed related incidents, but to paraphrase the IBM parable, "no one ever got fired, for doing quarterly releases, and heavy QA."