We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect
Analysis Summary
Ask yourself: “Did I notice what this video wanted from me, and did I decide freely to say yes?”
Worth Noting
Positive elements
- The video offers a valuable, non-dogmatic look at DevOps as a business function focused on developer experience and cost, rather than just a list of software tools.
Be Aware
Cautionary elements
- The creator uses the inherent complexity of the 'DevOps Roadmap' to position their own curated resources and stream as the primary way to avoid being overwhelmed.
Influence Dimensions
How are these scored?About this analysis
Knowing about these techniques makes them visible, not powerless. The ones that work best on you are the ones that match beliefs you already hold.
This analysis is a tool for your own thinking — what you do with it is up to you.
Related content covering similar topics.
Santa Claus on delivering 99% Uptime
Kai Lentit
He did WHAT to the DB?
ThePrimeagen
Doppler is without a doubt my favorite secrets management platform
Dreams of Code
Why LLMs are popular
The PrimeTime
A Wake Up Call for Computer Science Students
Phillip Choi
Transcript
how hard is it to learn the devops technology SE I mean listen dude I'm going to be real with you if you do exclamation mark devops in chat you're going to see this big mamama jaming map there's this thing out here called the devops road map this is just like a Dos of technology to the brain if you want to start with some of this technology I don't know man I it's hard to say like I don't want you to follow this by heart if you're talking about just the technical sides of it I think experience is going to be your biggest beneficiary there if you're interested in the tech just jump into the tech but devops isn't just Tech it literally can just overwhelm you for sure the biggest thing I think in devops that you should enjoy is the problem solving part of it as a company how do I solve this problem and what technologies can we use to get there that is really what my job is and there are basic principles in some regards that you can kind of consider but it depends on the size of the company it depends on the goals of the company and the problems that lie with that I would say the only thing that is consistent is really that it's a practice and it's used as a practice to solve problems at a company but that practice isn't standardized which is ironic because we do standardization in devops but the reality of it is is devops itself is not standardized it's very much based off of where you're at what problems you're dealing with can you give some examples how do our Engineers develop what languages are they using what tools are they using locally are we providing a good ecosystem for them to be able to develop in like that whole first developer problems that is a devop thing that you deal with at a company making sure your developers are efficient the local development experience the packages the languages the ecosystem like all that stuff once you've got that solved for or at least somewhat solved for then you can focus on infrastructure and deployment how do we start releasing that code how do we plug in the developer experience that we created into the experience that we want for deployments and infrastructure and so then we plug those two in together because that's the point of devops is it's not okay we did this one thing here now let's just throw out the other one in the window the devops team is really supposed to be the glue of the company in a lot of ways for technical purposes once you glue the developers basically to their deployment cycles and their deployment schemes then at that point you have code being made and contributed and then you also have that code being automatically built tested whatever and then deployed to your cloud provider or whatever those two problems are so General and yet so vast and so different in how we solve those problems it would be difficult for you to find two companies that do the same thing third one would be cost I I would say even maybe before that is scale at that point you know your your spending money you've got stuff in the cloud so again developers deployments scaling that and then the last one I think the last one should pretty much always be cost because cost is something that you really can't reflect upon unless you know how much we're fully spending until you know that entirely it's really hard to be able to be like all right let's do cost savings it's like are we done changing stuff yet and it's like no it's like all right well let's wait till we're done changing stuff and then we'll talk about costs basically I don't have an opinion about codee and that's fair I'm fine with that because I'm not the developer in that regard I can have an opinion about how we manage the code in the sense of like where folders are or structure standardizations and things like but I can't walk in and be like yo we're got to do this in Rust as a devops engineer they would just look at me and be like who the are you which is fair now if I walk into the conversation I say listen guys you guys have got a lot of memory leaks we are constantly having flaky like that's where I come in because then as an engineer devops engineer I walk in and I say we have a set of standards that your tests are not meeting and because your tests are not meeting those standards we're dealing with issues where they're failing again I don't really talk about code but anything related to it deployment development environment all that kind of stuff that's really what devops does
Video description
Blackglasses from TheAltF4Stream goes over how to get into DevOps the right way if you're just starting out. More resources: - DevOps for Developers: https://frontendmasters.com/courses/devops/ - Enterprise DevOps & Cloud Infrastructure: https://frontendmasters.com/courses/enterprise-devops/ Join the Discord: https://discord.gg/7AteQJc Watch live on Twitch: https://www.twitch.tv/thealtf4stream Follow on X: https://x.com/thealtf4stream #devops #platformengineering #programming #softwareengineering