A good DevOps specialist should feel free to work with the people he or she works with. Developed soft skills will definitely contribute to this. Communicating with specialists of different profiles in daily activities requires advanced communication skills. So if you find it difficult to communicate – start to develop this skill from the first days of work, you can learn it.
It’s no secret that DevOps resources in teams are often limited, that’s why a specialist of this practice needs to be independent. This is especially true for development, education and self-study in the initial stages. In addition to professional development, this will allow the junior to determine for himself whether this is exactly what he wants to do in the future and what lies at the heart of his soul. It often happens that in practice DevOps is not exactly what is expected.
It’s also important for a novice specialist to have a technical backround, and even better, a technical education. Understanding of computer networks and infrastructure, as well as the basics of building fault-tolerant solutions will come in handy. Now we can highlight a certain trend, when DevOps become former programmers. Modern devops services can be useful for virtually any company, so it is important to look in this direction.
What not to do
The DevOps team is always in the minority, and on small projects it is just one person. That’s why you shouldn’t put yourself above others and consider yourself the only and unique carrier of knowledge not available to others. You need to communicate with the team and define its priorities, understand how it is more convenient for everyone to interact, how to optimize work and be one. Therefore, it is not recommended to rely only on the theory caught from books and articles, and try to impose it on your colleagues, but to listen to others’ words and make choices based on the needs of the team.
Nevertheless, even a novice specialist should be firm enough in his decisions and not follow all requests and suggestions of colleagues on the project. You need to find some balance between team spirit and best practices, read in books, though it is not easy.
Again, due to the fact that DevOps specialists on projects are often no more than one, there is a certain vacuum of communication with colleagues interested in devops direction and technologies. Despite the contradictory attitude to profile events, we recommend not to disregard them. Meetings, conferences – all this will suit, especially, at the first stages. DevOps should be engaged in its own development, sometimes even more than other specialists. Now let’s try to list what is important and what is at the heart of DevOps.
What to do
- TCP/IP – it is very important to understand how the network works (a classic question in an interview – What really happens when a user hits the google.com address in the browser). Here is the Cisco CCNA course, the TCP/IP section is enough.
- Linux (the distribution doesn’t matter, it’s fresh). Personally it helped me a lot in my time to understand what happens under the hood when the operating system boots up. “Linux from Scratch” is probably the best of the free ones but I have to deal with it.
- Python is probably the easiest to learn and at the same time the most popular language in the world of DevOps and not only.
- AWS – cloud infrastructure, which greatly simplifies the life of DevOps engineers, taking on a huge part of routine tasks. In this case, the so-called AWS Free Tier allows beginners to feel the lion’s share of services absolutely free. For me, the AWS Certified Solutions Architect course, a guide to it, was ideal.