|Sent on:||Thursday, June 6, 2013 3:41 PM|
> @Michael, I have to admit I'm curious to hear why managing a DevOps team is a terrible idea... sounds like a good story.I am not going to go into detail on a mailing list, maybe over a beer some time!
My personal take on it is that DevOps is about breaking down barriers,
and focusing on making the process of turning code into a running
production service as smooth and efficient a pipeline as possible.
Adding a DevOps team into your org structure has the opposite effect
unless you do it very delicately; instead of making the process
simpler the team instead becomes another silo competing with the
Network, Security, Build, Systems, QA, Development etc.
Quite a few other people have explained why a DevOps team is a
terrible idea much more elegantly, some of my favorite bookmarks
This recent blog post by Ben Kepes:
"Operations is Dead, but Please Don’t Replace it with DevOps"
Adrian Cockrofts post on how they approach things at Netflix is well
"Ops, DevOps and PaaS (NoOps) at Netflix"
And if you want something much more cynical try the adventures of DevOps dave:
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Michael ([address removed]) from Vancouver Ruby Meetup Group.To learn more about Michael, visit his/her member profile: http://www.meetup.com/vancouver-ruby/members/40770052/
Set my mailing list to email mehttp://www.meetup.com/vancouver-ruby/list_prefs/?pref=1
As they are sent
In one daily email
Don't send me mailing list messages
Meetup, POB 4668 #37895 NY NY USA 10163 | [address removed]