Starting Your New DevOps Job 

Right on, glad you liked it!

Awesome, glad you enjoyed it!

These spam bots are getting crazy! 🤣🤣🤣 Just kidding, thank you very much for your kind words. I hope the content proves to be valuable to you.

Right on, glad you enjoyed it!

Right on, good luck!

Glad it was helpful!

Awesome, glad it was helpful!

It is!

You’re welcome, thanks for watching!

Glad it was helpful!

Right on, good luck!

Glad it was helpful!

Right on, glad it was helpful!

My pleasure

Aaaaaawwwww yeah! Good luck and be sure to let me know how it goes!

@@DevOpsForDevelopers Sure I will, thank you!

Yup, sure can!

That's awesome, thanks for subscribing. I'm happy to hear you're enjoying the videos. IMO: yeah- CCNA is definite overkill. Basic networking skills should work, you can always learn more as needed. You should have a solid understanding of the 7 layer OSI model, routing, firewalls, vpns, and subnets. Top that off with some skills with the tools needed for troubleshooting like ping, nmap, tracert, etc... and I think that will cover 99.999% of all the problems you encounter.

Many many thanks

Lol. Get after it!

Like Forest Gump

I'm glad to hear you found the video helpful. I definitely have thoughts on this: go camp out with the developers. Go to their scrums/stand-ups, hang out in their chatrooms, if you're working in the office: sit in their office. One of the biggest obstacles implementing DevOps is those who benefit from it don't know how it can help them. It's like traveling around the world: challenging if you've never heard of an airplane. As a result, they are likely over there building airplanes while you've got a parking lot full of jets sitting idle. Spending time with them lets you see what they are trying to accomplish and show them DevOps solutions that already exist. Worst case scenario: they hire a bouncer to keep you out but until then, keep at it! 🤣 Good luck!

I'll add also this is one area where being in-office vs. remote really makes a difference. In-office, you can go where they physically are. Most people tend to frown (or call the cops) when you show up their house uninvited though 🤣🤷‍♂️

@@DevOpsForDevelopers "One of the biggest obstacles implementing DevOps is those who benefit from it don't know how it can help them." 100% agree here. I see the DevOps role as a support role and our primary customers the developers and ops team. But for them, their customers, is the actual customers who uses the products that the devs create. When it comes the implementations of features to fulfill requirements set the business, do you think the DevOps role should be involved? If so, how? In my understanding, DevOps primarily focus on the packaging of the app and move it from A to B using pipelines, but doesn't seem like we need to know the content inside the box or how it is architectured.

IMO: DevOps extends far beyond packaging and pipeline management. DevOps is the conduit between Dev and Ops. So when Dev is implementing a new feature, it's the DevOps role that guides them to utilizing and implementing the infrastructure provided by Ops. A good example of this is a Dev team building a containerized app when the Ops team has no infrastructure to support containers. During feature planning and building is also the opportunity for DevOps to prepare for a successful deployment. That means not only building any package and deploy pipelines necessary, but communicating to the Ops team about any changes in infrastructure capacity requirements or application monitoring that may result. There are also security implications: building and packaging the code should try to catch any unmitigated security holes which will lead to another conversation with either Dev or Ops on how to resolve or protect against the vulnerability. The more familiar you are with the code, infrastructure, and architecture, the more opportunities for success you will see.

@@DevOpsForDevelopers That makes sense, I will keep this in mind and build up my overall knowledge of the product on the dev side and how that is being operated on the ops side to generate opportunities for improvement. I really appreciate you taking the time to give your insights :)

In my career spanning 3 decades, I've worked with many frameworks in places with good and bad cultures. Most of it depends on you.

@@DevOpsForDevelopers Thank you for the heads up, what company are you specifically working for and where is the location

@@fahadmolla9581 I’m at Polygon Labs. We’re global and 100% remote

@@DevOpsForDevelopers oh nice what’s the team size within your role and what are your day to day roles specifically. I work at MIT Consulting as a QA Engineer

@@fahadmolla9581 8 of us in DevOps, engineering team is 50+ (I think). Lots of activities to streamline, standardize, and automate processes to make it easier for dev teams to self-serve their infrastructure. How is it where you are?