Since the last 5 years, the DevOps ecosystem was changing fast but I always heard the same question “How to become a DevOps engineers ?”
Without taking into account the fact that DevOps is not a job and all of this debate — because I need a new blog post (probably more) only to talk about this — I was asking myself why does this question is more asked than many others, why I’m always receiving the same question ?
For people who started working in system administration and development since more than 5 years, DevOps was like a natural evolution of development and production systems and organizations, especially for the organizations who adopted agile methodologies and felt a need to go further.
New developers and IT engineers trying to understand DevOps, found themselves in front of something new having multiple definitions and many point of views.
As I said in other blog posts, everyone defines DevOps according to what he’s selling, so recruitment companies don’t have the same definition as DevOps evangelists.
For beginners and even intermediate developers, this is what makes DevOps hard to understand: There is no single clear definition.
In IT industry, if you are passionate about DevOps, you’ll find yourself working as a DevOps engineers in most cases. Even if some companies avoid using this position name but most of them uses “DevOps engineer”, “DevOps developer” .. etc
A digital transformation today needs to be done while taking into consideration the DevOps philosophy and practices. In large companies, making this transformation happens and changing many teams and departments at the same time, comes with costs and especially risks.
Any change could come with risks, which is normal, that’s why these companies felt the need to bootstrap DevOps from inside the organization by employing “DevOps engineers” and “DevOps teams”.
Most of these “DevOps engineers” are ops with a good understanding of development or in some cases developers with ops experience. But since DevOps is about transformation, business and communication, these engineers with technical skills, found themselves with many other responsibilities that are not technical.
Deploying several times a day could not be done without a good technical understanding of development, operations, QA and many other technical skills but before all of this, without communication, strategy, planning, learning and other non-technical skills, it’s rather impossible to deploy several times a day.
What’s hard about DevOps ?
DevOps is a philosophy and when a philosophy becomes a job, this job will not be something easy to do.
In order to face these challenges, a DevOps engineer must be polyvalent and multidisciplinary.
DevOps is full of challenges and learning, it needs more skills than just the technical ones, a good understanding of complex technical problems and business needs at the same time.
Many of you are DevOps specialists and what I learned from my personal experience and from what I’ve been seeing around, is that most of us are highly skilled professionals but don’t have enough knowledge about business and business processes. With time, we can have less time to learn new skills ..
This is your first challenge as a DevOps practitioner, continuously learning new things !
With a fast changing world, there’s always new technical skills to master, as many things to learn as once you stopped learning, you’ll feel outdated and out of the market.
What’s hard about learning is not leaning itself but the increasing amount of things to learn. I’ve always shared what my knowledge and new skills in my blogs and now by email 🙂
If you feel your last blog post will help members of DevOpsLinks learn new things, email me and I’ll be happy to review it and share it in the newsletter !
I appreciate the fact that many of you share their thoughts and technical knowledge in blog posts, mailing lists, books .. etc
Without all of this, I am sure learning will be harder and takes more time !
Stay in touch !