I am a developer with a passion for testing. I've been coding for 14 years and I want to share my experience and learnings with other developers to help them write better software.
I started writing software in 1984. Over the years I worked with many languages, technologies, and tools. I have been in leadership positions since the early 2000s, and in executive roles since 2014.
I guess it depends on the Org. However, DevOps is not really a role, or something that somebody does; it is a culture.
Unfortunately, budding engineering teams in startups don't have money to invest on it. The tooling is still rough, and much work is necessary to set things up correctly. Teams in the early stages are too busy building a product to become obsessed about DevOps practices (unless the team members are already experts, which is rare at this point)
For established teams, it is difficult to quickly change ways things work, so organizations often hire someone with a "DevOps" title to bring-in the discipline and get things started. Eventually, it is not something somebody "does". It is something that is part of how everyone does things. It is a "how," not a "what."
DevOps considerations have to be built-in the way the software is designed. It is an all-encompassing culture that allows engineering teams to scale without having to scale a technical operations team linearly with the development team.
I am a developer with a passion for testing. I've been coding for 14 years and I want to share my experience and learnings with other developers to help them write better software.
I absolutely get what you're saying about the team culture. And it's not something we've quite cracked in my team yet.
There is still a Dev Ops role though, particularly when it comes to Linux. There is a great deal of knowledge and skill required to set up environments, manage permissions, security, etc, etc. This is generally focused in an individual or individuals because it requires focus and dedication to learn properly. Also a lot of Devs are quite happy for someone else to handle it for them.
That's not to say a whole team's knowledge and skill can't be improved generally in this area though.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
DevOps seems to be something you find yourself doing if you're the most experienced developer working in an underfunded team... 😉
I guess it depends on the Org. However, DevOps is not really a role, or something that somebody does; it is a culture.
Unfortunately, budding engineering teams in startups don't have money to invest on it. The tooling is still rough, and much work is necessary to set things up correctly. Teams in the early stages are too busy building a product to become obsessed about DevOps practices (unless the team members are already experts, which is rare at this point)
For established teams, it is difficult to quickly change ways things work, so organizations often hire someone with a "DevOps" title to bring-in the discipline and get things started. Eventually, it is not something somebody "does". It is something that is part of how everyone does things. It is a "how," not a "what."
DevOps considerations have to be built-in the way the software is designed. It is an all-encompassing culture that allows engineering teams to scale without having to scale a technical operations team linearly with the development team.
I absolutely get what you're saying about the team culture. And it's not something we've quite cracked in my team yet.
There is still a Dev Ops role though, particularly when it comes to Linux. There is a great deal of knowledge and skill required to set up environments, manage permissions, security, etc, etc. This is generally focused in an individual or individuals because it requires focus and dedication to learn properly. Also a lot of Devs are quite happy for someone else to handle it for them.
That's not to say a whole team's knowledge and skill can't be improved generally in this area though.