I agree with this, but I wonder if its because people right now are just still trying to figure out the tech. We're in the beginning of the adoption curve, so to speak and specialties will come eventually.
As an additional point, I see DevOps expanding to DevSecOps, DevTestOps, and when the marketing folks catch up I'm sure we'll soon see DevSecTestOps. These are all just fancy words for being a more complete Developer - and enabling Developers to deliver faster.
Anecdotally... From where I'm sitting right now (devops IT, huge non-tech company), it hasn't actually solved the problem of dumping crap over the wall, because ultimately people balk when going to prod with changes. (Compliance/SOX, fear of change, gui based existing deployments, bad APIs, etc....)
So would I get paid more for being good at all of these areas? Or is this a move to open up a bunch of positions for mediocre people? (no offense, I am mediocre at code)
Because DevOps fans seem to be advocating for more responsibility for similar/less pay (and you're outright fucking yourselves if you take on-call often without compensation).
If DevOps moves anything like software does, there will be industry leaders which cause a lot of followers (90%) to hamfist the 10%'s methods onto their weird deployment/lifecycle processes and it will be an ongoing mutant until some other new thing promises to bring the light.
I think a side-effect of devops is that more developers have to be good at more things, and less excellent at one. But, if I'm a hiring manager, there's places for both of those profiles in my team.
That's fine, but if I'm maximizing my pay for the effort spent, I'm just going to screw companies as hard as I can by charging them a ton of money while doing very little for them as a contractor. As much as you'd think the market would remove people like this from the industry, it isn't happening.
I could join up as a fulltime employee for 6 months only to find out they don't actually want to change anything (despite lying to my face in the interview) and increase value because they're a shitty non-profit, which means I won't get rewarded for putting ideas forth. WHERE IS MY RECOURSE FOR WASTING 6 MONTHS OF MY LIFE?!
a. Learning how to detect BS in interviews. Interviews are two-way streets.
b. Sit down and figure out what you really do want and how you ended up in this situation so it doesn't happen again.
c. 6 months over a career is nothing, and again, it wasn't wasted, its just the way you're looking at it.
d. Have you networked at all in these six months? If so, not wasted. If not, well that can only be on you not the company, right?
e. If you think non-profits are shitty, maybe a) they're not for you; b) you don't understand non-profits; and/or c) what were you doing there in the first place.
f. "screwing" a company is the same thing as looking out for your own needs (or in this case, the contractor's). There's good and bad contractors, of course.
Your observations may not necessarily be wrong, but to say it was a waste of time is short-sighted.
(edit: formatting)
Exactly. I'm a mobile developer and I cross into "DevOps" field a lot, but I see it as a part of my job as a developer to make our team's lives easier.
It's a fine job to take if you know that's what you're in for, and you're not planning on advocating for actual devops.
Everytime I see a posting hiring a DevOps developer, I grind my teeth a little.
It's like a posting for an Agile Developer from a couple years ago. There isn't such a thing as an agile developer, just developers who use agile. I feel like its just turned into a way for a company to signal that they are modern and attrach developers.
It reminds me of https://www.commitstrip.com/wp-content/uploads/2016/11/Strip...
Ops was about discipline and method. Restrict the problem set to known values. The one thing that I see these days is that developers don't have a fucking clue about ops but they do see that the basic task responsibility is toilsome, counter-creative and that 90% of it can be automated by reliance on coded procedures in write once argot that hopefully is editable and doesn't give up the family jewels when posted in pub github.
"DevOps" is a teamwork style and process pattern, wherein the same people engineering the logic of a system also support each other in taking ownership over the execution of the logic and maintenance of the system.
DevOps means that, instead of sending an impatient email to the "DB admin" to apply your migrations, that you invite her to become familiar with the reason the migration was needed in the first place. In turn, she extends her toolchain to empower you to apply the migration yourself. Soon, you are part of the same team and the line dividing you, stopping you from supporting each other, is gone.
DevOps is good for people who like to always be learning; it can be difficult for people who like to ever more deeply specialize.
One thing that seems clear to me: the rise of packaged and automated ops solutions is not a threat to DevOps; on the contrary, it makes it even easier for a "Dev" team to collaborate on and take ownership of the "Ops" of an organization.