DevOps is just WRONG

Introduction

DevOps jobs can mean a hundred different things in a hundred different companies. In some places, DevOps roles are centered around building CI/CD pipelines to deploy software releases, whereas in others, it involves managing Cloud infrastructure, networking, and permissions — tasks that are quite similar to traditional admin work.

Many DevOps positions focus exclusively on a specific tool, such as Kubernetes, while others are dedicated to automation and on-call support. Most of the time, however, DevOps roles end up being glorified admin jobs with better pay. These roles might involve a bit of script writing and Python automation, which has made the industry fragmented. The term DevOps has become so broad that it’s almost meaningless.

The main issue is that many high-paying and desirable jobs require proficiency in all these skills. Yet, in practice, you often only end up using a subset of them. This reality translates into a long learning curve each time you switch jobs, unless you specialize in one particular area and offer it as a service.

Keywords

• DevOps
• CI/CD pipelines
• Cloud infrastructure
• Networking
• Permissions
• Kubernetes
• Automation
• Script writing
• Python
• Fragmented industry
• Specialization

FAQ

Q: What are the common responsibilities in a DevOps role? A: DevOps responsibilities can vary significantly but often include building CI/CD pipelines, managing Cloud infrastructure, handling networking and permissions, focusing on specific tools like Kubernetes, automation, and on-call support.

Q: Why is there a long learning curve for DevOps roles? A: There is a long learning curve for DevOps roles because the term encompasses a wide range of skills and responsibilities. Many high-paying DevOps jobs require proficiency in multiple areas, but you usually end up using only a subset of those skills in practice.

Q: How can someone reduce the learning curve when switching DevOps jobs? A: One way to reduce the learning curve is to specialize in a specific area of DevOps and offer that expertise as a service. That way, you can focus deeply on one skill set, making transitions smoother and more focused.

Q: Why do some people consider the term 'DevOps' to be meaningless? A: The term 'DevOps' has become so broad and fragmented that it can refer to vastly different roles in various companies. This lack of a standard definition makes it challenging to understand what specific skills and responsibilities the term entails in any given job.