61–70 of 80 posts
I wish the idea that DevOps was a role or activity would die.
In practice, and talking from my experience, unless you're one of the lucky few this is what it really means to do DevOps in 2019: - Forget what the books said, theory, semantics and idealism. You are a DevOps Engineer, working in a platform specific team. - You deal with Jenkins or similar, and consult other teams or developers to write scripts for it, or worse, do the work for them since they're too busy doing actu…
In practice, and talking from my experience, unless you're one of the lucky few this is what it really means to do DevOps in 2019: - Forget what the books said, theory, semantics and idealism. You are a DevOps Engineer, working in a platform specific team. - You deal with Jenkins or similar, and consult other teams or developers to write scripts for it, or worse, do the work for them since they're too busy doing actu…
My company calls what I do DevOps but I write full stack webapps to support the network operations team. I prefer to call it OpsDev, but noone seems to agree with me.
In practice, and talking from my experience, unless you're one of the lucky few this is what it really means to do DevOps in 2019: - Forget what the books said, theory, semantics and idealism. You are a DevOps Engineer, working in a platform specific team. - You deal with Jenkins or similar, and consult other teams or developers to write scripts for it, or worse, do the work for them since they're too busy doing actu…
Well there's your first mistake. DevOps is not a career, unless you are a management consultant.
In practice, and talking from my experience, unless you're one of the lucky few this is what it really means to do DevOps in 2019: - Forget what the books said, theory, semantics and idealism. You are a DevOps Engineer, working in a platform specific team. - You deal with Jenkins or similar, and consult other teams or developers to write scripts for it, or worse, do the work for them since they're too busy doing actu…
My company calls what I do DevOps but I write full stack webapps to support the network operations team. I prefer to call it OpsDev, but noone seems to agree with me.
https://smcleod.net/tech/2019/08/08/camels-and-unicorns.html
In practice, and talking from my experience, unless you're one of the lucky few this is what it really means to do DevOps in 2019: - Forget what the books said, theory, semantics and idealism. You are a DevOps Engineer, working in a platform specific team. - You deal with Jenkins or similar, and consult other teams or developers to write scripts for it, or worse, do the work for them since they're too busy doing actu…
At current job, its kind of frustrating in that ee act as if we're doing dev ops, but as a dev, when a (my) job fails, ops doesn't trust me to either abort or restart the job.
So we've got all the buzzwords, none of the benefit.
Typical support call: ops calls me with the failed job. I log in, take a look see; tell them to download a file and restart a job. Whole lot takes an hour because I dont have permissions in prod to do anything but look at the log. Take that definition of devops and whove it up your ass.
I do recognize its not like this everywhere, but thays how it is at my current company, and they want to call it dev ops. More like roadblock he'll.
In practice, and talking from my experience, unless you're one of the lucky few this is what it really means to do DevOps in 2019: - Forget what the books said, theory, semantics and idealism. You are a DevOps Engineer, working in a platform specific team. - You deal with Jenkins or similar, and consult other teams or developers to write scripts for it, or worse, do the work for them since they're too busy doing actu…
My company calls what I do DevOps but I write full stack webapps to support the network operations team. I prefer to call it OpsDev, but noone seems to agree with me.
I’m an ops engineer but develop the code to do my team’s operations tasks.
"DevOps" == "sysadmin that can write scripts"
Or “a developer that does on-call” I’m being facetious. Sysadmins always wrote scripts and developers always got called at home.
Many of the rest did, but not high quality scripts, and only in shell; not perl or python or tcl or ...
The lower rungs of sysadmin were happy to point and click on guis and lug and plug hardware.