 So you want to be a DevOps engineer in 2021 where you reach the right video, let me explain. This video was brought to you by Digitalink Academy. You're number one source to learning programming fast and get to that six figure freelance salary you desire. Our courses include our secret project course, our freelance Kickstarter, our Python course and our interview programming course and much, much more. So if you haven't already, go ahead and click the link below to get to our free seven step freelance guide so that we can help take your career to the next level. I'll see you guys in the course. All right guys, let's dive into some of the problems and expectations and the realities of a DevOps engineer to make sure everybody's on the same page about what to expect depending on what type of situation we in and hopefully I can bring clarity to this situation. But before I get started, go ahead and put a comment below on your experience as DevOps. Do you know what it is? Are you a DevOps engineer? Do you wanna do that? Share your experience below and some of the role blocks and questions you guys may have so that we can start a conversation below and I have a good sense of how you guys think, what's your expectations of DevOps compared to what we're gonna talk about in the video. So go ahead and comment below. That being said guys, DevOps is a term that's thrown around really nobody have a really good explanation for all companies because it's a mix and match depending on the company. But at the end of the day, a company have a technology software stack that they do maintenance on and they have to actually make sure they maintain the code and the software. Well, they're gonna deploy that to production so that the end user can use it. Well, when a small organization, this process is not that bad because you got less people, you probably just got one person or two people who actually deploying the stuff. So it's not that big of a deal. Once you start to increase the size of the company, more people involved, more systems, more impact, it becomes harder and harder to do that and you need a process in place that's gonna allow you to do that smoothly, communicate with the people, do testing, make sure things are good before you deploy it. So once you deploy it, everything is good to go. Well, the problem with this is you got so many different steps along that way and traditionally the system administrator is responsible for the server, the infrastructure and what put on there but the developer sitting over here is responsible for the actual software. So, you know, and the handoff in a small company is pretty easy and then the communication is pretty easy. The larger the company, the more complex situation and the more people are in between those two and we haven't even talked about the end user that's over here that's actually communicating with the software developer on that system requirements and testing and all that stuff. That being said, it's a lot of stuff to manage. That's where a DevOps engineer come in. The person who's gonna make sure that communication between that dev developer and the operations infrastructure guy is top notch and also for the end user and the customer as well during testing QA, deployment, testing, rollback if needed. All that stuff is managed by the DevOps engineer. Some companies do a little different. It's not a specific exact science for every company but generally speaking, this is what the role is. So, that being said, you have to come in as the DevOps engineer and identify all this stuff. A lot of people think, hey, the DevOps engineer is gonna come into a ready-built system and everybody gonna know what to do and life is gonna be good. No, that's not the case. You're gonna have to come in and see how they're currently doing things, whether some of the issues and then slowly but surely build this process out. It's not gonna be done overnight. I can tell you that now. It's gonna be a slow and steady process. Don't try to do too much too fast. People do not like change, especially rapid change. You wanna roll this out in controlled fashion. Make sure everybody's comfort level is good. Make sure everybody's okay with the process and doing their part. If you don't do this, your process will fail. I can tell you a lot of situations where a really eager developer or DevOps engineer come in and try and change stuff overnight only to get booted out of the company because they come in and ruffling too many feathers and don't get that buy-in, which there's a certain extent to, well, yeah, you wanna do the best for the company and also you wanna get buy-in as well. That's a delicate balance that a lot of developers, DevOps engineer don't have and they tend to upset the customer, upset the operations manager, upset the developer because they're trying to implement new systems without letting them know the benefits of it. And yeah, you're gonna have some bad apples who don't push regards of how good it is. But for the most part, once you kinda get most of the people involved, you should be good to go. That being said, guys, DevOps is a great career. I wouldn't recommend this for somebody at the beginner stages of their career. I would highly recommend you to work as a, either the developer, most of the time, operation manager or BA role, depending on what the situation is, you can start from any place in the IT field, but just coming in as a pure beginner and not necessarily knowing what the developer do or the system administration do or none of the terminology of the department or industry or anything. It's extremely hard to become a DevOps manager or an engineer in that specific situation. So I would say in my humble opinion that DevOps engineers is not a beginner level career. It's more of you've been a developer or a system administrator or a BA for about two to three years, possibly more, the more, the better. And then you start to see the need for this type of communication. And your role will obviously evolve into being a DevOps engineer in a larger environment, guys. So I would say, being a DevOps engineer, I personally haven't had that role for an extended amount of time. The good thing about my role and more like a solutions engineer slash engineer slash whatever needs to be done. So I've been all over the board and I had roles where I had to play DevOps for a while. And the most, the important thing is, is the end product in hearts and minds and getting everybody on the same page about that process and then making sure you maintain that process over time to make sure it scales with your company. This is not something that you're gonna set and forget and don't have to do it anymore. It's just something that you're gonna have to kind of regroup and refresh. It's not gonna be as often as you think, but it's not gonna be something that you can go two or three years without touching. And it's just not gonna be the case with technology, minded company, things change, system change, requirements change and it throws a different variable in play that wasn't currently there. So guys, like, subscribe to the content. If you have additional questions, comment below. Tell me what your failures are or what's going on on your side. As far as just why you can't become a DevOps engineer, what's going on, all that good stuff, we'll have a conversation. And get things figured out for you and kind of go from there. But if you haven't already, go check out my premium courses. Links are in the description box guys. Take your courage to the next level and also support the channel. And if you haven't already, I'll put links to my seven step guide here on the screen. So go check that out, it's free. I'll see you guys in the next video. Peace.