is devops bullshit?

Skip to first unread message

Valb Onne

Mar 9, 2015, 10:29:04 PM3/9/15
Seems like there are a lot of people out there who seem to be falling victim of the buzz surrounding devops (spread by marketeer and recruiters) giving the movement a bad name.
Any thoughts?

Greg DeKoenigsberg

Mar 10, 2015, 9:41:59 AM3/10/15
> --
> You received this message because you are subscribed to the Google Groups
> "devops-toolchain" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
> For more options, visit

Greg DeKoenigsberg
Ansible Community Guy

Find out why SD Times named Ansible
their #1 Company to Watch in 2015:

Stuart Charlton

Mar 10, 2015, 10:17:23 AM3/10/15
We've seen this movie before with Agiie and Lean (or any new subjective technique to learn... like object orientation, I remember "OO is bullshit" being popular in the 90s, which was just after "structured programming is bullshit" in the 80s, and I have heard from many that think the Web is bullshit too )

A new body of knowledge around how people work usually gets misinterpreted and misapplied ... Often deliberately, because people are like that.  Doesn't make it bullshit.  

The term Devops will be as reviled as agile in some quarters fairly soon;  Not sure what can be done about it other than combating bad ideas with better ones.

Sent from my iPhone

Joaquin Menchaca

Nov 10, 2015, 3:12:47 PM11/10/15
to devops-toolchain,
My 2 pence. 

DevOps as a philosophy is the real deal, because apps are in the cloud, not shrink wrapped boxes.  Ops are no longer guys in a closet managing enterprise backend systems, they have to manage a highly distributed application, which calls for greater collaboration between ops and dev, than before, when their scopes were separated.  DevOps is simply a realization of this need. 

Now comes the marketing spin, which typically boil down to misunderstanding of what DevOps is about, and misrepresents it, e.g. talking about Agile challenges and calling it DevOps.  Managers read the marketing fluff, and create jobs titled "devops", as if a culture can be codified in a role.  It's like having a role called "Agile" or "Quality".  Personally, this drives me nuts, because I enter a job, and I am interviewed by 5 people for 5 different roles...  A lot of times, DevOps is a build/release engineer, other times, it could be more Opsey, with change config tooling, scripting, and some light development.  A lot of times, they embed other roles, such as DBA, architect, network engineer, etc.

Text comes the text book authors, that have no clue, and read the marketing fluff, codify it into some theoretical framework.  Then new graduates come out of the system, total noob-sauce, and they either have smarts to adapt (self-learn) in the marketplace, or get thrown to the curb.  

The companies that succeed do surprisingly well, become famous, their employees talk at conventions.  Others that struggle, feel like a chapter out of the Phoenix Project  book (by Gene Kim), but can succeed as well, because ultimately, if the company is meeting marketing/business requirements, they are making money.  Thus enters a whole new field of ... drum roll... BizDevOps..

Reply all
Reply to author
0 new messages