DevOps is NOT a Job Description
Join the DZone community and get the full member experience.Join For Free
the devops hype produces some strange effects. not only do tool
vendors try to jump on the devops band wagon by declaring their products
“devops inside” or listing devops as a feature, but companies start to
look for a “devop” in their job ads. don’t be misled! here’s what devops
devops is about culture
the fundamental basis for successful devops is a culture of trust and a feeling of fellowship. everything starts with how people perceive each other: is it an “us vs them” culture or is it a “we”-culture? i don’t see any job description in here.
devops is about automation
let’s look into automation. a lot of the advantages devops promises lies in the right use of automation tools. automation removes variance from your processes and minimizes human error. while you’ll definitely need people with automation skills and experiences, this is not enough. automation only – without the right culture – will not provide the benefits you hoped for.
devops is about measuring
then let’s examine measuring. while measuring is a critical, mandatory practice for improving processes, it’s not really a job description. every employee should formulate hypotheses, run experiments, and validate or scrap her ideas. no magic sauce here either.
devops is about sharing
what about sharing? i’m sorry to say that while the devops movement is largely driven by sharing ideas, problems, and tools, this isn’t really a good job description. it is an attitude more than a task.
if you run through the points, which really define devops you’ll see for yourself how strange it is to try and hire a “devop”. devops is not a job – devops is culture, automation, measurement, and sharing (cams).
Opinions expressed by DZone contributors are their own.