Ask HN: Why was system admin re-branded as devops?
I am thirty seven years old who has been in the field for 11 years on-and-off. This just gives you only an idea of when I started. I have experience in writing web software for various commercial applications. I don't have experience with scalable design, unit testing, continuous development, or agile development methodologies. I am comfortable with the mechanics of writing small programs. In most places, I would be considered a junior developer having some mastery over smaller scale work before delving deep into software production and design topics. This confuses several people when they see my years of experience, especially recruiters who usually have to cope with their own limited sense of technical knowledge to accurately fit workers into proper roles. Seems like I have greatly missed out on a part of the pipeline that has creeping into more developer jobs, and I (possibly a bad luck thing) somehow has continued to evade this invasion through particular jobs that don't expose me to it. Despite that, I tell myself and others that I am not a systems admin, but a developer. I have 0 experience working with an "operations" team and have little experience with the deployment part of the pipeline, with the exception of blogs and brochure-style websites that use shared hosting services. My understanding is that it's the people that would be doing the job of fortune 50 companies if they were trying to roll their own data infrastructure? If developers are expected to take more roles, doesn't that turn development into "second class" work if no one is left to fill a dedicated role for software development? With the work I do, I just "throwing it over a wall" and we pay a third party hosting service to handle it. Uptime, stability, that's usually left on them so I don't really need to think about it. Yet if new devops work involves more and more writing code for automation systems, then perhaps we need to make a case for why has rebranding take place. Has it been mainly due to shifting more responsibilities around different people? 2 comments on Hacker News.
I am thirty seven years old who has been in the field for 11 years on-and-off. This just gives you only an idea of when I started. I have experience in writing web software for various commercial applications. I don't have experience with scalable design, unit testing, continuous development, or agile development methodologies. I am comfortable with the mechanics of writing small programs. In most places, I would be considered a junior developer having some mastery over smaller scale work before delving deep into software production and design topics. This confuses several people when they see my years of experience, especially recruiters who usually have to cope with their own limited sense of technical knowledge to accurately fit workers into proper roles. Seems like I have greatly missed out on a part of the pipeline that has creeping into more developer jobs, and I (possibly a bad luck thing) somehow has continued to evade this invasion through particular jobs that don't expose me to it. Despite that, I tell myself and others that I am not a systems admin, but a developer. I have 0 experience working with an "operations" team and have little experience with the deployment part of the pipeline, with the exception of blogs and brochure-style websites that use shared hosting services. My understanding is that it's the people that would be doing the job of fortune 50 companies if they were trying to roll their own data infrastructure? If developers are expected to take more roles, doesn't that turn development into "second class" work if no one is left to fill a dedicated role for software development? With the work I do, I just "throwing it over a wall" and we pay a third party hosting service to handle it. Uptime, stability, that's usually left on them so I don't really need to think about it. Yet if new devops work involves more and more writing code for automation systems, then perhaps we need to make a case for why has rebranding take place. Has it been mainly due to shifting more responsibilities around different people?
I am thirty seven years old who has been in the field for 11 years on-and-off. This just gives you only an idea of when I started. I have experience in writing web software for various commercial applications. I don't have experience with scalable design, unit testing, continuous development, or agile development methodologies. I am comfortable with the mechanics of writing small programs. In most places, I would be considered a junior developer having some mastery over smaller scale work before delving deep into software production and design topics. This confuses several people when they see my years of experience, especially recruiters who usually have to cope with their own limited sense of technical knowledge to accurately fit workers into proper roles. Seems like I have greatly missed out on a part of the pipeline that has creeping into more developer jobs, and I (possibly a bad luck thing) somehow has continued to evade this invasion through particular jobs that don't expose me to it. Despite that, I tell myself and others that I am not a systems admin, but a developer. I have 0 experience working with an "operations" team and have little experience with the deployment part of the pipeline, with the exception of blogs and brochure-style websites that use shared hosting services. My understanding is that it's the people that would be doing the job of fortune 50 companies if they were trying to roll their own data infrastructure? If developers are expected to take more roles, doesn't that turn development into "second class" work if no one is left to fill a dedicated role for software development? With the work I do, I just "throwing it over a wall" and we pay a third party hosting service to handle it. Uptime, stability, that's usually left on them so I don't really need to think about it. Yet if new devops work involves more and more writing code for automation systems, then perhaps we need to make a case for why has rebranding take place. Has it been mainly due to shifting more responsibilities around different people? 2 comments on Hacker News.
I am thirty seven years old who has been in the field for 11 years on-and-off. This just gives you only an idea of when I started. I have experience in writing web software for various commercial applications. I don't have experience with scalable design, unit testing, continuous development, or agile development methodologies. I am comfortable with the mechanics of writing small programs. In most places, I would be considered a junior developer having some mastery over smaller scale work before delving deep into software production and design topics. This confuses several people when they see my years of experience, especially recruiters who usually have to cope with their own limited sense of technical knowledge to accurately fit workers into proper roles. Seems like I have greatly missed out on a part of the pipeline that has creeping into more developer jobs, and I (possibly a bad luck thing) somehow has continued to evade this invasion through particular jobs that don't expose me to it. Despite that, I tell myself and others that I am not a systems admin, but a developer. I have 0 experience working with an "operations" team and have little experience with the deployment part of the pipeline, with the exception of blogs and brochure-style websites that use shared hosting services. My understanding is that it's the people that would be doing the job of fortune 50 companies if they were trying to roll their own data infrastructure? If developers are expected to take more roles, doesn't that turn development into "second class" work if no one is left to fill a dedicated role for software development? With the work I do, I just "throwing it over a wall" and we pay a third party hosting service to handle it. Uptime, stability, that's usually left on them so I don't really need to think about it. Yet if new devops work involves more and more writing code for automation systems, then perhaps we need to make a case for why has rebranding take place. Has it been mainly due to shifting more responsibilities around different people?
Hacker News story: Ask HN: Why was system admin re-branded as devops?
![Hacker News story: Ask HN: Why was system admin re-branded as devops?]()
Reviewed by Tha Kur
on
March 06, 2020
Rating:
No comments: