Cause DevOps.
Some would say that you should learn it simply because you should, end of story. But it’s not that simple. Regardless of...
For further actions, you may consider blocking this person and/or reporting abuse
Nice article, great reasons, and totally agree - the more Ops Devs know, the better; just don't expect most Devs to be excited about being Ops and Ops services experts, though they should support their code in production.
I recommend Devs who want to learn Ops should learn to use infrastructure as code tools, like Ansible for config mgmt and HashiCorp Terraform for provisioning workflow (many devs already are using TF from a self-service module template standpoint).
Then for networking, service mesh seems to be what's making it more dev-approachable these days. For that you should check out HashiCorp Consul, Istio, or Linkerd.
And of course there's Kubernetes, but that's got quite a learning curve. I think a simpler container orchestrator to start with would be HashiCorp's Nomad.
I intentionally avoided to give specific tool suggestions, but since you did:
Great tips!
Just don't go to service mesh 'because it makes networking more dev approachable', ideally you should have a good reason to mess with it, and there are a lot of people just going cause it's trending.
Same for kubernetes some times. That's why I said to look for tools that your company already uses, and expand from there.
I did not give any references about CI/CD, orchestration, and other important Ops/DevOps topics since they so closely relate to tools... But we could give more tips like that here in the comments!
I 100% agree with you. It's one of the reasons I started to write vpsformakers.com as an introduction to the world of managing a server. Even if you end up using a managed platform it will help you tremendously to know how this things work. I would be careful though to recommend people to start with "service mesh" or Kubernetes. It's better to start really simple and add more complexity step by step.
Totally agree with you!
And nice book!
As a front end developer can I make the transition to a DevOps career? Just being curious ... :)
See the last gif of that post :)
ALL of this. I started out in old-fashioned sysadmin, so I've always been "the developer on my team who isn't afraid of ops". Which means I become, by default, the devops guy if there isn't already one. And I see my fellow engineers being kind of afraid not just of the servers but of their own machines, and I'm like, "Dude...you are a wizard. The machine exists to do what you tell it to do. You'd better know exactly how to tell it how to do stuff and why and when."
I don't understand any developer who doesn't get that...
I like the way you approach the question. Should you? If you want to be a better developer.
There's Google's Site Reliability Engineer book as well that talks a lot about DevOps. A really good primer for understanding it.
I did not want to share any "organizational" reference since in Twitter I also shared @lizthegray article about Production Excellency together with this one. (Also she worked at Google and the reference that you linked is in her blood)
Here I only wanted to share pure ops references. In this post I'm only talking to devs. In @lizthegray post she talks to companies.