3 ms·
DevOps is a concept, not a role. It means breaking down the silos and allowing processes, ideas, capabilities to run across both SWE & operations teams. I nev
by inopinatus 10y ago
DevOps is a concept, not a role. It means breaking down the silos and allowing processes, ideas, capabilities to run across both SWE & operations teams. I never knew a really first-class *nix sysadmin who wasn't also a kernel hacker, so this isn't anything new, it's just got a label.
Probably the most devops-y thing you can do in an applications environment is operate a continuous delivery pipeline.
The most un-devops-y thing you can do is start a devops team.
- tyingq 10y agoWhether it's correct or not, it's a named title people are hiring for. https://www.indeed.com/q-DevOps-jobs.html https://www.indeed.com/q-DevOps-jobs.html So I thought it worth mentioning as one of those hybrid roles.
- inopinatus 10y agoThat's a great example. There's nothing in those job listings that wasn't, conceptually speaking, in the job description of a system engineer or sysadmin thirty years ago. In this usage of "DevOps" it's a buzzword, and I recommend you should avoid anyone who puts buzzwords in your job title, because it speaks volumes up front about their culture and values and clarity of thinking. I really do like the descriptor Site Reliability Engineer, though, for exactly the same reasons.
- traf68 10y agoIt allows the company to save on dedicated resources in my experience. A lot of first-class *nix admins in my generation have a problem dealing with dev ideas in system context. In the company I am at now we have gone a step further and allowed dev/mgmt to control ops|prod and reserved system to sidestep the crapulence of this concept.