3 ms·
I recently was part of a team that properly practiced DevOps and as soon as it started working we had a reorg and it was broken apart. If the premise of the ar
by phamilton 11y ago
I recently was part of a team that properly practiced DevOps and as soon as it started working we had a reorg and it was broken apart.
If the premise of the article is "Developer time is precious, don't make them do grunt work" the I would counter with "Developer momentum is precious, don't let developers get blocked by operations/QA/release."
On our team, we had Ops and QA. But I needed something done and they were already working on something then I could have a quick 15 minute chat after standup about the Puppet change I needed to make and then go do it myself. An hour later I'm done, the change is deployed and I'm moving on to the next task. Now, without an embedded Ops resource on the team, I have to file a ticket and pray someone picks it up within a few days.
- Turbots 11y agoI couldn't agree more! If you've read the Phoenix Project, it clearly states DevOps solves the problem of bottlenecks, which is the single most important aspect in the Product Development lifecycle. You just can't have developers waiting anymore for Ops to do something, or vice versa... Shit needs to go fast and blocking factors need to disappear, or else you sacrifice agility
- lowmagnet 11y agoThe way to not get "blocked by QA" is to have automated tests and QA people who can write them as well as dream up scenarios to break your toys. They are also able to do code reviews in your stack as well.