4 ms·

I get more of what you're saying now, but I still think that reinforces OPs point because, to me, what you described is a Systems Engineer not a Systems Adminis

by kodah 4y ago

I get more of what you're saying now, but I still think that reinforces OPs point because, to me, what you described is a Systems Engineer not a Systems Administrator. OP is asking for some structuring as to what these roles require in terms of knowledge. To me, "Administrator", "Engineer", "Technician", etc all prescribe different degrees of knowledge and also usually correlate with responsibility. As for "SRE" vs "DevOps" vs "Systems Engineer", I'm not so sure. For instance, I typically expect SREs to be able to write application software and orchestration software. I have similar expectations of someone who uses the title Systems Engineer but I might expect less application software development experience. DevOps I think I'd rather forget is a word.

xorcist 4y ago
Systems engineer is a title that seems to have fallen somewhat out of favor, but it wasn't unusual that it was a less hands-on role than sysadmin/SRE. Sometimes close to a system integrator but could also be what is now known as an infrastructure architect. Who do you think did the SRE work before that name was invented? Most likely it was your friendly sysadmin. It is the type of role that is not much noticed when done well, and probably that's why some feel it underappreciated enough to keep inventing new job titles. It's still the same job, pretty much the role that requires privileged access.
- kodah 4y ago
  I was raised in the South and grew up across the midwest, so that may color my perspective. The place where I encountered sysadmins the most was people who managed a small collection of assets; the keyword being managed. I didn't see them inventing entirely new systems. Working across DCs, I would see Systems Engineers building these new systems, being escalation support for them, and at times coding up entirely new infrastructure applications. I don't really buy the idea that administrators are underappreciated, I just don't think it accurately captures what a systems person on a product team actually does, much less the distinction between a SRE-SE and a systems person. My base argument is that it's not the same job at all. A good Systems Engineer does not guarantee a good SRE-SE because the job is that much different. One of the notable distinctions is writing application code, which is much different from Terraform, Ansible, Salt etc
  - apple4ever 4y ago
    I have to disagree. SRE=SE=SA. What they exactly do depends on the job. Some can write application code, some cannot. But they are all the same thing. I've worked at SRE jobs where there was no application code writing, and I've worked at SE jobs where there was application code writing.

by kodah 4y ago

xorcist 4y ago

Systems engineer is a title that seems to have fallen somewhat out of favor, but it wasn't unusual that it was a less hands-on role than sysadmin/SRE. Sometimes close to a system integrator but could also be what is now known as an infrastructure architect. Who do you think did the SRE work before that name was invented? Most likely it was your friendly sysadmin. It is the type of role that is not much noticed when done well, and probably that's why some feel it underappreciated enough to keep inventing new job titles. It's still the same job, pretty much the role that requires privileged access.

kodah 4y ago
I was raised in the South and grew up across the midwest, so that may color my perspective. The place where I encountered sysadmins the most was people who managed a small collection of assets; the keyword being managed. I didn't see them inventing entirely new systems. Working across DCs, I would see Systems Engineers building these new systems, being escalation support for them, and at times coding up entirely new infrastructure applications. I don't really buy the idea that administrators are underappreciated, I just don't think it accurately captures what a systems person on a product team actually does, much less the distinction between a SRE-SE and a systems person. My base argument is that it's not the same job at all. A good Systems Engineer does not guarantee a good SRE-SE because the job is that much different. One of the notable distinctions is writing application code, which is much different from Terraform, Ansible, Salt etc
- apple4ever 4y ago
  I have to disagree. SRE=SE=SA. What they exactly do depends on the job. Some can write application code, some cannot. But they are all the same thing. I've worked at SRE jobs where there was no application code writing, and I've worked at SE jobs where there was application code writing.