3 years ago

Become a DevOps is not a easy task, there is not a easy way, in DevOps there is not a “cookbook” that tells you how to become a DevOps or a path to follow to be one, the first thing is what I need to kwon?, what I need to learn?, and the answer to that questions was: “What does your client need?”, as I say, there is no a path to follow, you must adapt to the needs of the client. Obviously you need to know some basics for example CI/CD or networking, but start to study a tool or technologies depends on the client’s needs, and I’m not talking about a specific client, understanding what the client need will give a path to know what do you need to study, because in the DevOps world is impossible know about all the technologies or tools, if you know someone who knows all the tools and technologies please tell me. The first thing that I notice is that in DevOps the things that you do as DevOps are very different from the things that other DevOps do, the problems that you faced are very different and finding a solution goes beyond understanding the problem, you must understand the client’s needs, what i means is that you can find a “fancy” solution that solves the problem, but that “fancy” solution is expensive and you maybe you not understand that client’s need a cheeper solution. It is not enough to find a solution to solve a problem, you need to find a solution that fits on your client. As developer my understanding of DevOps was limited that the work of a DevOps was only continuous integration, continuous delivery, and maintaining the application running in production servers, i was so wrong, because as DevOps your work don’t stop there as i mentioned you need understand the client’s needs, and understanding the client’s needs brings the idea of ​​improving, if you see something that can improve you not wait until a ticket is created you create your own tickets.