5 ms·

Are You a DevOps Engineer If You Aren’t Writing Code?

28 points by wagslane 4y ago

yuppie_scum 4y ago
95% of companies can solve all their DevOps problems with code that’s already written on GitHub.
- gregoryl 4y ago
  The trick is finding the right code, and making it work with the rest of the system.
  - jfoutz 4y ago
    I'm pretty sure if you take a year, you can evaluate enough repos to find one to match your circumstance. Or, take a week and slam it out.
- l3uwin 4y ago
  The trick is deploying that code repeatably to production with IAM/RBAC, Code Scanning, monitoring, alerting etc.. Most companies suck at that.
threatofrain 4y ago
This blog entry is an advertisement for boot.dev's backend training product.
- wagslane 4y ago
  Author here, I prefer the term "content marketing" xD Jokes aside, there is a small plug at the end of the article, but the article itself is not an ad. I have a lot of thoughts on the current state of "DevOps" and enjoy writing about it
- forgotpwd16 4y ago
  Includes a small ad (as well as free alternative resources) but the article isn't just that.
cetahfh14615 4y ago
what even is devops in the first place? Like is it just IT for deployments with a bunch of management lingo tacked on? like how are there people in the industry working on this sort of thing who can't code? It just bugs me, I talked with someone from work whose job title was System Engineer; I asked them if they do systems programming or something... and they said they don't know how to program (even after getting some kind of tech degree!!)
- aliasxneo 4y ago
  I'm still trying to figure out if there's a difference between DevOps and SRE.
  - sofixa 4y ago
    There is and isn't. SRE is Google's more strictly defined DevOps, basically - after DevOps started to get slapped across everything (classic sysadmins, CI/CD tooling people, etc.), Google came out with something that basically defines, more narrowly, something very similar to the DevOps role (as originally intended), in a lot of detail. There is a slight difference in focus though, because DevOps also focuses on the role's interactions with development, while SRE focused on the role itself and using metrics and data to be able to do the work required (SLOs, etc.). I personally prefer the SRE term, because it's usually better understood and has a narrower meaning. DevOps can mean a lot more different things.
- nuker 4y ago
  > what even is devops in the first place? Cloud engineer. Must write Cloudformation templates if AWS, know many resource types and properties, know linux and networks. Python is a plus for fringe cases automation, when there is no clear cloud vendor solution. PS: Did not read TFA
- 28304283409234 4y ago
  I spoke to another person calling themselves 'Full Stack Engineer", but couldn't even explain the OSI model. What's your point? Titles rarely match competences and responsibilities.
hirebackenddev 4y ago
[dead]

28 points by wagslane 4y ago

yuppie_scum 4y ago

95% of companies can solve all their DevOps problems with code that’s already written on GitHub.

gregoryl 4y ago
The trick is finding the right code, and making it work with the rest of the system.
- jfoutz 4y ago
  I'm pretty sure if you take a year, you can evaluate enough repos to find one to match your circumstance. Or, take a week and slam it out.
l3uwin 4y ago
The trick is deploying that code repeatably to production with IAM/RBAC, Code Scanning, monitoring, alerting etc.. Most companies suck at that.

threatofrain 4y ago

This blog entry is an advertisement for boot.dev's backend training product.

wagslane 4y ago
Author here, I prefer the term "content marketing" xD Jokes aside, there is a small plug at the end of the article, but the article itself is not an ad. I have a lot of thoughts on the current state of "DevOps" and enjoy writing about it
forgotpwd16 4y ago
Includes a small ad (as well as free alternative resources) but the article isn't just that.

cetahfh14615 4y ago

what even is devops in the first place? Like is it just IT for deployments with a bunch of management lingo tacked on? like how are there people in the industry working on this sort of thing who can't code? It just bugs me, I talked with someone from work whose job title was System Engineer; I asked them if they do systems programming or something... and they said they don't know how to program (even after getting some kind of tech degree!!)

aliasxneo 4y ago
I'm still trying to figure out if there's a difference between DevOps and SRE.
- sofixa 4y ago
  There is and isn't. SRE is Google's more strictly defined DevOps, basically - after DevOps started to get slapped across everything (classic sysadmins, CI/CD tooling people, etc.), Google came out with something that basically defines, more narrowly, something very similar to the DevOps role (as originally intended), in a lot of detail. There is a slight difference in focus though, because DevOps also focuses on the role's interactions with development, while SRE focused on the role itself and using metrics and data to be able to do the work required (SLOs, etc.). I personally prefer the SRE term, because it's usually better understood and has a narrower meaning. DevOps can mean a lot more different things.
nuker 4y ago
> what even is devops in the first place? Cloud engineer. Must write Cloudformation templates if AWS, know many resource types and properties, know linux and networks. Python is a plus for fringe cases automation, when there is no clear cloud vendor solution. PS: Did not read TFA
28304283409234 4y ago
I spoke to another person calling themselves 'Full Stack Engineer", but couldn't even explain the OSI model. What's your point? Titles rarely match competences and responsibilities.

hirebackenddev 4y ago

[dead]