Even though I've developed some familiarity with tools like docker & k8s along with cloud platforms. I've been managing the whole CI/CD pipeline of a MERNstack-based project recently. But I don't think I've learned something very useful which could benefit me for years in the sense of career development. I think "Ops" is just a set of tools that any dev could learn anytime and get used to it.
There are no programming techniques or logic behind managing cloud infrastructure and resources. Anyone who has some familiarity with systems can easily learn these sets of tools, follow good practices, and manage "Ops".
I tend to beg to differ on this. Infrastructure as code is a well-known pattern that you can apply almost every programming technique for managing your infrastructure. I agree that any dev can learn the tools, though.
Heidi is a developer advocate at LaunchDarkly. She is passionate about clear communication, humane workplaces, and conference speaking. In her spare time, she sews dresses with pockets.
I think that it isn't just a set of tools, but a set of mindsets and experience patterns. Ops people spend a lot of time thinking about stability, persistence, and safety, and that's not always something that we reward in developers.
Just as devs learn patterns for how to build and architect systems that don't take up too much memory or have message collisions, ops folks learn about patterns of storage, single points of mechanical or network failure, or overusage threat profiles.
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.
Even though I've developed some familiarity with tools like docker & k8s along with cloud platforms. I've been managing the whole CI/CD pipeline of a MERNstack-based project recently. But I don't think I've learned something very useful which could benefit me for years in the sense of career development. I think "Ops" is just a set of tools that any dev could learn anytime and get used to it.
There are no programming techniques or logic behind managing cloud infrastructure and resources. Anyone who has some familiarity with systems can easily learn these sets of tools, follow good practices, and manage "Ops".
I tend to beg to differ on this. Infrastructure as code is a well-known pattern that you can apply almost every programming technique for managing your infrastructure. I agree that any dev can learn the tools, though.
I think that it isn't just a set of tools, but a set of mindsets and experience patterns. Ops people spend a lot of time thinking about stability, persistence, and safety, and that's not always something that we reward in developers.
Just as devs learn patterns for how to build and architect systems that don't take up too much memory or have message collisions, ops folks learn about patterns of storage, single points of mechanical or network failure, or overusage threat profiles.