The biggest WTF trick that management ever pulled off was to convince developers that they needed to be Dev/Ops Engineers. They put a new title on it, praised it, and developer drank it up. Suddenly it got the BUZZ and people are wickedly attracted to whatever is buzzing. SO they jumped and now years later are wondering "WTF DID I DO?" The key - RESIST THE BUZZ. I've been in IT for well over 20 years and the buzz never stops with this field. There is always something new, something better, something else that everyone else is doing......the BUZZ. Find what you like and ferociously stay true to that. Management finds the BUZZ irresistible and most managers push for the BUZZ.
This video is excellent. I've been working as a DevOps engineer for about five years now, and there's one thing I've come to realize: it's a profession where burnout is not just common, it's almost expected. And it's hit me hard. I'm seriously contemplating a career change, despite my passion for the field. It's a strange feeling - on one hand, the pay is great, but that doesn't seem to compensate for the growing dislike I have towards my job. At home, I have a Kubernetes cluster set up in my home lab, and tinkering with it is genuinely enjoyable. But the thought of turning on my work laptop every morning fills me with dread.
Devops sucks. The pay is the only attractive thing but it's like working with sticks and gum. Most of the tech is still new and not implemented correctly. It's a junk area of tech IMO. Also cloud is overrated. Bring back on prem all you morons.
I think that's common across IT these days. I was a developer in a large enterprise that went "agile" over the last 5 years. I was there for a total of 20 and I hated my life for the final 5 and ended up resigning.
I think some people are not built for IT. You have to have some sorta "calmness". One Task at a time. A trainer of mine once said "You gotta create SPACE for yourself". If you can't do that, then you're screwed in IT.
@@RabbitConfirmedI think you missed the point of this video and a lot of the responses. I've worked in IT for 20 years and it used to be possible to do what you described but I ended up leaving my job because of the endless emails, web based "tests" on ethics and diversity etc., 6 month self-assessment, yearly self-assessment, "agile" projects that weren't really agile but just a way to force delivery out of people on a schedule that ultimately just created pointless structure that consumed time, scrum meetings with more non-developers than developers that were just status updates. Maybe at a FAANG company or somewhere else that sells technology you can "make space" for yourself but for the rest of us like the man said "it's hard out here for a pimp".
Refreshingly honest take! I always loved setting up the infrastructure for the team in my CS projects, and even today, I prefer writing tooling and DSLs for use by analysts than webdev slop. You've got me considering transitioning into DevOps
I have not had a job till now (a senior student), I was here just to see what is the real work_style in devops. Instead of making me scared of DevOps, this video got me inspired. I liked the learnings, I loved the Internships. DevOps now seems to my cup of Tea. Also I want to Work on my own Projects and Services as a product, a startup. But a want to take my time, first want to feel the industry and gain clarity and meet people. All (most) , negative points seemed positive to me.
i love working as devops, lots of constant learning, very challenging sometimes im usually with a lot of things going around, developing process, adopting strategies, standarizing its very taxing on my time, but its specially worth when working with a highly capable team problem solving is something thats highly appreaciated here
man..for me, being distracted constantly is the biggest con especially if your manager don't account for it. I can relate to all of the points you said
I've been DevOps Engineer about 7 years now and its hard to see me doing anything else in the industry. In normal life, I hate unpredictability and learning constantly new things, but in work, those are the things that keep me engaged and fresh, an idea of being a basic SW engineer coding some particular things just feels boring and depressive, and the pay is great is another advantage. I think you got most of the challenges pretty spot on, you need certain kind of personality to really enjoy DevOps work.
" In normal life, I hate unpredictability and learning constantly new things, but in work, those are the things that keep me engaged and fresh" - lol I'm quite the opposite, when it comes to the money for mortgage/ providing for my family/etc., I like stability and predictability.
Thank you, I'm currently studying to be a DevOps engineer switching from Software Engineering it's good to hear about the negatives because it provides a realistic view of the job as compared to only seeing positives.
You guys have an oversupply of developers? Currently there is a huge demand for practically every tech job here in Germany. They have positions open for several months even with good pay.
@@MoonShadeStuff don't be silly. I tried to get a job in Germany as a software developer. After applying for more than 100 job offers I got only 1 short interview and I have more than 20 years of experience as a developer and my salary expectation was very low in comparison to average salaries of developers in Germany. The main reason why I didn't get more interviews is that I only speak basic German.
Fantastic vid. I've been DevOps since before it was cool and can relate to much of this. One of the bigger issues for DevOps/CloudOps/Platform Engineers is when they find themselves in a product company that uses technology, rather than a tech company that makes products. The perspectives, values, etc., are all backwards, and they find themselves wondering what the difference is between themselves and their competitors when they have all the same "pieces"... Generally though, the industry is getting much better at embracing ops-first(ish) postures.
i've been working as a DevOps Engineer since 2014, it's definitely not an easy role to assume, however the part i like the most is doing a lot of different programming automations that are not necessarily CRUD applications. For example a have scripts to deploy applications on kubernetes, copy key vaults data, provide entire environments just in a few minutes.
What kind of issues you have? If I can help lemme me know, if you search cultura do caractere on App Store or play store, it’s my app where I share some content
You shed light on a common sentiment in the tech industry. It's not just DevOps; the expectation for a holistic understanding of the SDLC is becoming the norm for software engineers. Embracing continuous learning is the key to staying relevant in our dynamic field.
Continuous learning has been a daily practice for me, I have been in computer engineering jobs for over 40 years. Its not something new, it has been here all along, it is like any other professional career (Doctors, lawyers, dentists etc) , you need to study constantly to stay up to date.
I've been DevOps Engineer about 5 years and can't land a job for 4 months already because mass layoff and a lot of developers switched to DevOps the market is overheated now.
So u are on the mid/senior level. Could you share your technology stack and the background because for example in Europe u would get like 10+ offers per week.
Yep, sure. AWS and Kubernetes (AWS SAA-C03 and CKAD), also Terraform, Git, Docker, Jenkins, CI/CD with Jenkins, Makefiles, Helm charts, Bash scripting logic, EFK, Prometheus and Grafana. Cloud engineer for 2 years, DevOps engineer for 2.5. But I have an accent so that could be a reason and maybe not but it's how I explain it to myself. Anyway the described situation in Europe looks much more better than here in US.
@@DevOps691 Lol mate, then look for a job in Europe with such a stack I assume that u have highly developed problem solving skills so it shouldn't be a real deal to find job!
learning constantly new things for me is a requirement in tech industry. Everything can be change. I'm full-stack developer, I do some devops sometime, for me, it is difficult because it need you to practice all the time. Otherwise, we can forget most of things after a week not touching it.
Just started a position as a DevOps engineer. My background is as an SDET engineer, so it was a somewhat unexpected change of pace with regards to the day to day operations. I think this was largely due to my underestimation of the role managing infrastructure plays in the position. I also was under the impression that building out the CI/CD pipelines on which the test run involved actually building said tests, as I was very familiar with in my role as an SDET. While these assumptions weren't on the mark, I'm still really enjoying the position. I especially enjoy that learning on the job isn't something unique to new engineers, but a constant part of the position which engineers cut out time for at all levels of seniority. I love learning new things, but in other roles felt like it was the mark of a newer dev to spend a significant portion of time learning. I feel like taking the time to learn is expected in the role of a DevOps engineer, which is quite refreshing.
Hey.. I'm working as SQA role and wanna make a switch to DevOps for some time..The problem I'm having is how do I justify my 4 yrs exp in devops..would you like to share your journey from SDET to DevOps and may as well share the roadmap..
“Developer complains that DevOps contains Ops”. All of these complaints are things that operations have been dealing with their entire career. I’m glad people are starting to understand just how exhausting/sucky operations can be. The context switch is particularly brutal. As well as having to constantly relearn everything every 2 years.
This is the perspective of a Jr Engineer, and it shows. I'm assuming you worked as a DevOps Engineer at a startup company. If that's the case, sure, it's definitely a grind. But chances are most everyone else across the entire Engineering organization is also grinding. Because, you know, that's how startups survive. Seems like you're actually into the managing Infrastructure piece. My advice would be to stay with it and eventually join a bigger company. Ideally one that doesn't put DevOps in the job title, and actually respects the fact that managing Infrastructure is its own separate discipline. You'll come to find the work suddenly feels way more stable, there's no quicksand under your feet (constant learning about new tools and switching to them), your Manager will be more than reasonable about deadlines, and you'll write way more actual code/will have the time to contribute upstream to open source projects.
Thanks for sharing. Just to clarify, I am not saying that I don't enjoy my role at my company. Many of the factors that I touch upon in this video are actually things I see as positives. But I see your point, perhaps the perspective of a senior engineer will be different.
Great video. I am a softawre engineer looking to transition into DevOps. In software the code you wrote last week is already outdated and incompatible with the other library introduced.. I dont think constantly learning is something you don't do in software and I would say you do it as much or more. BTW, with the bad tech market, you have a much better shot at a stable career with DevOps/SRE work than SWE. SWE is quite saturated and the requirements for a software engineer are all over the map from being the architect, back/front end developer to the web designer.
@@the_computer_scientist Hello, would you mind sharing your linkedin ? I've recently graduated have very good experience in java but I'm unable to land a job. I'm thinking of going into DevOps. Do you think this field supports freshers well ?
I am not that good in Infra part, but other things in DevOps are interesting to me. Got Bachelor degree in Computer Science, Masters in Networks, worked for many years as Software Dev, but wanted to try new things. DevOps seemed quite interesting, because you learn all the time new things, and understand how everything is put together. It's quite true you can't focus on one thing in particular, but at least this helps you grow somehow and to be more disciplined in a way.
Indeed, all those tasks upon tasks and new things ALL add up to your experience. You will be able to find a job anywhere in the dev (ops) field if you stick around long enough. Turn disadvantages into advantages people!
I am excited about this job opportunity as it aligns perfectly with my skills and interests in DevOps. Before focusing on DevOps, I was a Linux user and a backend web developer. I believe my experience in web development has provided me with valuable knowledge that will be useful in my pursuit of learning DevOps. I am eager to gain more experience through an internship in this field.
I’m a senior System administration working for the DoD cloud infrastructure and just got my Linux+ and DKA (docker) cert. my goal of 2024 is to land a full devops role and pass Terraform cert as well
Funny that I started listening the video and was like "obviously, that's the Ops part of DevOps", I've been in the area more that 15 years (before it was even called DevOps) and what you describe is exactly my job now, and that's what I like, constant challenge, always learning something new (using docker since 0.3 for example, look this new shinny "bsd jail for linux" XD ), always in that "discomfort zone" where you have to figure out how this new tech works and pass it to the rest of the team. Can be challenging at times, but very rewarding at least for me, not everyone is made for that job. If you are starting in this area let me tell you something: you will never know enough, but you have to keep the wagon moving forward.
here I am, a Machine Learning Engineer who also does MLOps from time to time. I love my role because I can scratch all my itch at once. be it DevOps, ML itself and SWE. I can relate twith everything you said.
I have been a DevOps/SRE for close to 10 years now and now and this is my advice for all new engineers: Start from the fundamentals. Learn Linux and Netowkring basics. Forget about Kubernetes and AWS if you are really new. Start with virtual machines and running different services in it and getting yourself familiar with the basics like webserver, reverse proxies, load balancers, databases etc before moving into cloud or Kubernetes. You can't run a marathon without learning to walk.
Most companies in my area is looking for software developers with devops experience. In fact I am going on an intervju soon where they highlighted this. I don´t think I would be happy only doing devops but for sure I like to be able to manage all aspects of delivering a product so devops is included in that.
Even though I’m an application programmer I like DevOps simply cause I like not being at the mercy of others. I like controlling my servers and optimizing performance with my code and my servers.
Based on all the IT and Tech Engineers I have met, DevOps Engineers make less than Software Architects and Engineers, in general! Never done DevOps Engineering but I might consider it! My specialty is hardware, operating systems, networks and software engineering!
Thank you for this video- I am a project manager for the past 7 yrs and now transitioning into DevOps and this was a great video with excellent advise for someone getting into DevOps.
After 15 years in UX/IxD I was looking for a career change to devops (since is almost a hobby dealing with infra and servers since teenage years discovering slackware, and I never stopped). Started this video to get some cons perspective and maybe reevaluate the route, but man this got me even more craving for some devops/infra role (most the part 1 and 5, bc my focus is broken and get super bored doing only one thing for days). Great video, going back to the studies and the job form filling (really hard to get a entrance role these days :( ).
Don't forget, devs jumping to devops see a better overall view of the industry and the pipeline they work in. Yeah doesn't scratch the coding itch but thay doesn't mean you can build custom CLI tools.
This is one of the best videos about DevOps role, keep uploading videos !!!. Loves your "realistic" takes on DevOps roles instead of highlighting the pro's only. I'm surprised that theres one thing you don't mention and that is On-Call rotation, if your team lack sufficient amount of resource (both in manpower & infra) then it can be super stressful. And team cohesive/coordination is also super duper important, I remember that on time we had a major migration, Our SRE Lead managed to split on-call so the teams are not burned out, "It's a marathon, not a sprint" she said, and always ensures checkpoints are introduced. Definitely one of the best Lead I've worked with
We build our own cloud for internal products. For me it’s puppet, salt, ansible, docker, python, ruby, bash, kvm, groovy, distro images, kickstart, packaging rpm. It’s just endless
Thanks. Interesting vid. I find devOps being a lot more interesting than a "simple" developer. But me being a bit weak at the coding side I find the DevOps role a bit challenging too.
It seems like you spoke my mind, glad to know there are other people who feel the same. Some days are good which you love some are too distracting. I love being challenged so I am enjoying my job.
What was funny is thought this video I thought you WERE trying to convince me to be a devops engineer. I work as a Tech Act Mgr (customer facing system admin) and was looking for the next step as my role is getting a bit too "salesy" and this sounds like the move! Thank you
It all depends on what software you work on, what product, projects and teams. Working on a narrowly scoped functionality, fixing bugs, dealing with untested spaghetti code copied from SO can be more frustrating and boring than Infrastructure automation. Nowadays many software engineering jobs are plain and simply farming k8s yaml files!
Couldn't agree more to each of these points mentioned. I work as a PKI consultant, the amount of time I spend on that technology is a day to at most 2 days in a week. Rest of is meetings, follow ups about meetings, dependencies on other teams, conducting workshops to increase technology adaptation, only to later discover there is problem with funding. Companies do not focus on a devops framework long enough for their staff to be moderately competent in it. Board level members and CTO changes the whole stack, that sends ripples down below in a bid to cut costs.
All of this is true, especially if people have dedicated "devops teams", which for me shouldn't exist, its not devops at that point, its a support team.
@@kipa_chuJust support means it´s only the Ops part of DevOps. Nothing wrong with that, but it´s wrong to call that DevOps. It's plain old legacy Ops support. A purely IT Operations job.
It's not only devops, it's everywhere in tech, and even non-tech. For example, many bigger tech companies require passing few coding interviews, but the skill set tested by them is unrealistic: real development and devops require people skills, endurance skills (90% of tasks is boring bugfixing of bugs made by someone else, who probably doesn't even work here) and engineering skills (being able to understand limitations and select the best existing solution). However coding interview checks only coding skills, which constitute maybe 1% of what's it needed for a programmer (for a devops even less), leaving the rest of unchecked, and everyone frustrated: good coders because they got a wrong, boring job, experienced engineers because they have to learn not-used things before interviews (or get rejected) and then similarly - get a boring mostly bugfixing job, HR and mangement because they hire wrong and inefficient people. And it all comes down to the fact that most people in HR and management have no idea what the job of their employees is actually about!!!
tbf, most "DevOps Engineers" are Cloud Engineers, fancy SysAds or Platform Engineers. Even most employers dont have a clue what devops really means and so the people that work as so calles devops Engineers. DevOps is not a single role or function in a team, its whole lot of principles, processes and cultural aspects which define real devops. DevOps is about building cross functional teams, not being a one man army who knows it all.
Agreed! I think there’s a misunderstanding between what a business thinks is ‘DevOps’ and what engineers think. Hence, all of the job titles that end up being interchangeable.
Thank you! I am an older software developer and was curious what being a DevOps REALLY meant. I absolutely have NOT worked for large companies (intentionally) so this is more speculation. Feel free to correct me where I'm wrong. Here are my thoughts. "DevOps" and "DevSecOps" is undeniably a very "cool" and "exciting" name, so it's no wonder that companies are jumping on the bandwagon especially with most videos promoting how fast projects will be completed and such. I don't know if the "only 50% of software projects get completed" stat is still true (and/or was ever true) but I can understand why that's appealing to top brass to get projects complete fast. Perhaps I am a dinosaur or am an exception since I have worked with small companies, but I still don't "get" the whole obsession with Kubernetes, Containers and such and building servers with code, etc, etc. I mean, I GET how cool and powerful it could be from a technical perspective, but being as I'm at core a businessman, it seems like massive amounts of endless work that never really pays off in the end for most small/mid size companies. Again, could be 100% wrong and maybe for large companies it's night and day, but this seems to be a core concept of being a DevOps engineer + using testing tools and such. Thinking through it, I have to wonder if these big companies have their "core engineers" that specialize as coders, DB admins, server specialists, etc and then have a whole bunch of DevOps at the top level. If this is the case, I would bet that those "core engineers" have it pretty good with an light workload and near guaranteed job security while the DevOps (despite any level of productivity they achieve) are expected to work at max levels and are always at risk of being let go. Why? Because by definition, DevOps people don't need to have DEEP understanding of anything and are expected to learn and adapt... so, how would someone with 10+ years experience be considered better than someone with say 1-5? Those Core Engineers can't be replaced because the difference between someone who KNOWS and Kinda-Knows is the difference between something working and complete disaster. College is the proof that "well rounded" doesn't really get you anywhere. I would imagine that DevOps engineers are only really good in a DevOps type of company. Smaller companies would expect you to "dig in" and improve things and build new things and that only comes from experience. If all you've done is write some code in basically some sandbox, when you are faced with a "blank page" needing to plan out a project with coding and database you'll just stare at it like you are trying to write a book. No interviewer is going to choose you for a Coding job where people have more experience coding, same for DB, servers, etc. Quantity of knowledge doesn't matter, it's DEPTH. My guess is that being a DevOps/DevSecOps would be great way to GET STARTED in IT. Get a wide net and cover a lot of bases and find out what type of stuff you like and don't like to do. Once you've found that, you then can migrate to another job (maybe at same or potentially lower pay) that focuses on what you love doing and then you can eventually get in a great job where you have security and a reasonable work schedule. My thoughts at least :)
As a college student can’t say much bout how corporates devops engineer works. But knowing this is ahead of me if I choose this career i like it thanks.
I have been a software engineer for over 10 years but this week I'll be starting a course in DevOps. I think at this stage of my career, learning about the infrastructure side of things will be beneficial and it seems that the industry may be moving more favourable toward infrastructure.
I currently work as a data engineer and whenever I can do something infrastructure related I have so much more fun than when I’m writing a pipeline to gather and process some poorly structured data following constantly changing requirements from the product managers. Devops sounds much more in line with what I enjoy. Any advice on where to start? I already know terraform and got AWS SAA cert.
Great to hear! Sounds like you're already most of the way there. I would try something like this: 1. If you don't have them already, get basic skills in Linux, networking and writing CI/CD pipelines (Jenkins seems to be a popular requirement in job listings). You don't need to be an expert in any of these but it's likely that you will get asked questions related to these areas in an interview. 2. Commit to at least 1 cloud provider (sounds like you have already chosen AWS). Get comfortable with the main services. 3. Start looking for opportunities! If your company has a DevOps/cloud platform team, it may be easier to try and transfer to one of these teams. Reach out to them and ask if they have any projects that you can collaborate on.
@@homebrewhenry thanks for the advice! I was planning to look more into networking and CI/CD especially since it's relevant to my current position and I'm so-so with those. Linux wasn't on my radar though, what are some examples of tasks related to Linux? Unfortunately no DevOps focused team at my company, data engineers deal with DevOps tasks, but it's generally more of a side topic :| even though automation and some neat infra can save a lot of time in the long run, most immediate priorities have to be taken care of, and those are either more data, or nicer data
@@ArekxQQQ Understandable! In that case, it may be worth while trying to introduce some DevOps related projects to the company. A great benefit is that you'll be able to talk about this in any future interviews even for non DevOps roles. RE: Linux - mainly shell scripting and SysOps-related tasks. For example in an AWS team, this could be making sure that AMIs have the latest packages installed or writing a bootstrapping script for a server. Shell scripting is also used a lot in automation. Definitely do not need to have super in-depth knowledge though.
Thanks man! Currently on helpdesk planning to move out to servers but without opportunities around servers it seems that devops have taken those server responsibilities as well..
I'm a Devops and I think it is about to game over now. Because I don't see there''s no more openings for the DevOps jobs in my market since the last year. The fate of DevOps role is just like the EA role back in 2 decades ago. The Enterprise Architect thrived only a couple years (2005 - 2010). Then it sank forever. And I saw no more Enterprise Architect jobs available in the market in the past decade anymore. The Devops is on the same path as the EA now. So Devops will be history in a couple years later. Just a waste of time (I earned the title but no future to sustain).
That whole getting people pinging you for various stuff should be directed to a ticket system. I've been a Linux sysadmin for 20 years and that will crush you eventually trying to be the sme for everything because it makes you feel like some kind of god. You aren't. I kinda hate what things have become which is basically all the sysadmin work I did with as much extra as can be crammed in. It kinda depends on the company though how much of that actually ends up happening or not though.
"You may only have surface level knowledge of certain tools but still be considered a subject matter expert by other people in your company." I thought I was the only one, and it's been hard to deal with. Especially when management gets pushy.. I'm just hopeful I can find something else when they determine that I will never know it all. lol
I think that DevOps isn’t a job title, is a culture that involves on everyone in the company. I would describe it as a SRE of Google, but also a SRE have much culture powers than a “DevOps” engineer. Source: sre book from google (oreilly).
I think that PaaS and AI tools now can enable much other functions for cloud engineers to perform. i.e. CI/CD, automation, networks, architecture, observability, maintainability, etc.
As a systems engineer and having worked along side many devops teams I see a couple issues. One the orgs I have been part of put too much on them when we are still there and are pretty capable of helping with these tasks. Two way too many devops team will do all this work and not really ask for our help and then complain about what they have on their plate. Devops teams should be working along side the Saas teams and admins to make this all work and so no one is doing more than they have too.
man all I care about is paying my bills. Ima keep taking software dev, dev ops, info-sec, networking projects etc as they come. Being flexible is how you survive layoffs.
What I don't like in the industry is that it treats vendors as technologies and half of the field is AWS-engineering where you are a glorified AWS operartor for a lot of the time.
Thank you for putting it out, really not for me. If I'm forced to do such job (visa expiry, threat of starvation) I would, but not out of my free will. It's important to have honest opinions on jobs.
On the 'focus' subject, how do you manage other work that you have that is being managed in agile scrum sprints? My work, although not DevOps, is very similar in terms of demands on my time, dealing with incidents etc. and so i don't think sprints align naturally with it, much to the frustration of managers who want to apply it blindly to everything.
Great question. Unfortunately I don't have an elegant solution to this. I've found it helpful to let my team/manager know as soon as there is a task that may take my attention away from what's in the current sprint. Luckily for me, they are usually quite understanding. If this happens a lot, it may be worth trying to define a more formal process with your manager.
I don't even know I'm trynna transition from commerce background to DevOps, cool thing about what you have mentioned is that I love troubleshooting things, and I'm open to knew technology and I think since i have opted for DevOps course i barely go out! seems like kinda getting used to it. I don't even know if they would even consider me for the role or not. (TSE VMware)
I beg to differ.. regarding 1:00 , you are building platforms and software that DEFINITELY is customer facing.. it's just the customer is in this case other developers or in my case.. data scientists working with data.. I am 1000X happier doing that.. than arguing with chrome which pixel to move 1 pixel that way or this way..
DevOps is NOT engineering job. DevOps is yaml and json file editing job, and the amount of infrastructure and networking that you need to know is just very small and abstracted by cloud provider GUI, cli and REST interfaces. You are only learning what is specific to that cloud provider, you barely need to know what CCNA has to know, not to mention CCNP or CCIE. The same goes for system engineering and security, you are just scratching the surface of all that doing DevOps.
On the other hand, because it’s abstracted away, you will get to cover more ground and become knowledgeable in many different areas - companies are more than willing to pay for that. You won’t become a networking guru immediately, but as the problems you face become more complex, and you start realising your gaps in knowledge, you will get to dive deeper than the cloud interfaces. You will also get the opportunity to specialise in what you like most, or re-spec if you’re bored with what you do (e.g. from Networks to Data or containers). Not to mention that you will always be able to go back to development - and be rather good at it knowing CI/CD, infra, security, etc.
What do the cisco networking certs have to do with devops? Saying a CCIE has to know more than a devops engineer is like saying an electrician has to know more than a chemist. You are comparing apples with oranges. Building secure deployment pipelines is nothing like maintaining an isp backbone for example. Almost none of the skills are transferable
Yes.. I do devops as part of my software engineering role.. made possible by the abstractions provided by the API we can interact with via CLI or by file manifests.
That is exactly my point, DevOps by itself is not engineering work, but more some kind of administration. I am sorry if DevOps "engineers" are offended by that. Anyway, they are in high demand. But recruiters now call "DevOps" a lot of things, and expect often some programming skills. @@TheStickofWar
Damn, I've yet to have it that easy. I still get called a fraud because of my usage of programming(python, C#, perl, groovy, others) outside of tooling, shell interfaces, gauging OS health w/ classic Sysadmin techniques, SQL querying, and automating using those tools(particularly IaC) with metaprogramming. I regularly find myself making my own headless apps / services, having to budget my time between maintaining, hardening, automating, and enhancing(i.e.: feature dev). So you're suggesting I've just been subject to hate? Thats really disheartening
devops jobs are kind of a scam, your not signing up to be a dev you're signing up to be an ops engineer. They sell it as you're doing both like coding, but slapping a terraform script together on the side, no that's not how it works. You are doing infrastructure, probably just infrastructure. However in all of software the learning doesn't stop, even if you're a normal developer.
I’m looking into switching into the IT-industry and I’m very interesting in networking. What would the biggest difference be between a devops engineer and a systems engineer? Is a systems engineer more ”practical” while devops is more project managing? How would you best explain the difference?
The biggest WTF trick that management ever pulled off was to convince developers that they needed to be Dev/Ops Engineers. They put a new title on it, praised it, and developer drank it up. Suddenly it got the BUZZ and people are wickedly attracted to whatever is buzzing. SO they jumped and now years later are wondering "WTF DID I DO?" The key - RESIST THE BUZZ. I've been in IT for well over 20 years and the buzz never stops with this field. There is always something new, something better, something else that everyone else is doing......the BUZZ. Find what you like and ferociously stay true to that. Management finds the BUZZ irresistible and most managers push for the BUZZ.
This video is excellent. I've been working as a DevOps engineer for about five years now, and there's one thing I've come to realize: it's a profession where burnout is not just common, it's almost expected. And it's hit me hard. I'm seriously contemplating a career change, despite my passion for the field. It's a strange feeling - on one hand, the pay is great, but that doesn't seem to compensate for the growing dislike I have towards my job. At home, I have a Kubernetes cluster set up in my home lab, and tinkering with it is genuinely enjoyable. But the thought of turning on my work laptop every morning fills me with dread.
Thanks for sharing. I’m sure you’re not alone in these thoughts.
Devops sucks. The pay is the only attractive thing but it's like working with sticks and gum. Most of the tech is still new and not implemented correctly. It's a junk area of tech IMO.
Also cloud is overrated. Bring back on prem all you morons.
I think that's common across IT these days. I was a developer in a large enterprise that went "agile" over the last 5 years. I was there for a total of 20 and I hated my life for the final 5 and ended up resigning.
I think some people are not built for IT.
You have to have some sorta "calmness". One Task at a time.
A trainer of mine once said "You gotta create SPACE for yourself".
If you can't do that, then you're screwed in IT.
@@RabbitConfirmedI think you missed the point of this video and a lot of the responses. I've worked in IT for 20 years and it used to be possible to do what you described but I ended up leaving my job because of the endless emails, web based "tests" on ethics and diversity etc., 6 month self-assessment, yearly self-assessment, "agile" projects that weren't really agile but just a way to force delivery out of people on a schedule that ultimately just created pointless structure that consumed time, scrum meetings with more non-developers than developers that were just status updates. Maybe at a FAANG company or somewhere else that sells technology you can "make space" for yourself but for the rest of us like the man said "it's hard out here for a pimp".
Refreshingly honest take! I always loved setting up the infrastructure for the team in my CS projects, and even today, I prefer writing tooling and DSLs for use by analysts than webdev slop. You've got me considering transitioning into DevOps
I have not had a job till now (a senior student), I was here just to see what is the real work_style in devops. Instead of making me scared of DevOps, this video got me inspired. I liked the learnings, I loved the Internships. DevOps now seems to my cup of Tea. Also I want to Work on my own Projects and Services as a product, a startup. But a want to take my time, first want to feel the industry and gain clarity and meet people. All (most) , negative points seemed positive to me.
i love working as devops, lots of constant learning, very challenging sometimes
im usually with a lot of things going around, developing process, adopting strategies, standarizing
its very taxing on my time, but its specially worth when working with a highly capable team
problem solving is something thats highly appreaciated here
This video has gotten noticed by the algorithm, this will boost your channel 100%.
man..for me, being distracted constantly is the biggest con especially if your manager don't account for it. I can relate to all of the points you said
I've been DevOps Engineer about 7 years now and its hard to see me doing anything else in the industry. In normal life, I hate unpredictability and learning constantly new things, but in work, those are the things that keep me engaged and fresh, an idea of being a basic SW engineer coding some particular things just feels boring and depressive, and the pay is great is another advantage. I think you got most of the challenges pretty spot on, you need certain kind of personality to really enjoy DevOps work.
" In normal life, I hate unpredictability and learning constantly new things, but in work, those are the things that keep me engaged and fresh" - lol I'm quite the opposite, when it comes to the money for mortgage/ providing for my family/etc., I like stability and predictability.
Basic SW engineer, lol, if there is no code, what will you deploy? Your json template?
@@Dikimkd he hates coding in html and css
I can't go back to maintaining ginormous enterprise web app #55230 that takes half a day to build and test
Same!! I can't imagine going back to dev
Thank you, I'm currently studying to be a DevOps engineer switching from Software Engineering it's good to hear about the negatives because it provides a realistic view of the job as compared to only seeing positives.
Don't do that because soon there will be huge oversupply of DevOps much larger that the current oversupply of developers.
You guys have an oversupply of developers? Currently there is a huge demand for practically every tech job here in Germany. They have positions open for several months even with good pay.
@@MoonShadeStuff don't be silly. I tried to get a job in Germany as a software developer. After applying for more than 100 job offers I got only 1 short interview and I have more than 20 years of experience as a developer and my salary expectation was very low in comparison to average salaries of developers in Germany. The main reason why I didn't get more interviews is that I only speak basic German.
Likewise, I'm switching from software engineering to devops engineer.
@@justiceowusuasare701 devops is also getting crowded. It is better to stay developer.
Fantastic vid. I've been DevOps since before it was cool and can relate to much of this. One of the bigger issues for DevOps/CloudOps/Platform Engineers is when they find themselves in a product company that uses technology, rather than a tech company that makes products. The perspectives, values, etc., are all backwards, and they find themselves wondering what the difference is between themselves and their competitors when they have all the same "pieces"... Generally though, the industry is getting much better at embracing ops-first(ish) postures.
i've been working as a DevOps Engineer since 2014, it's definitely not an easy role to assume, however the part i like the most is doing a lot of different programming automations that are not necessarily CRUD applications.
For example a have scripts to deploy applications on kubernetes, copy key vaults data, provide entire environments just in a few minutes.
Hello Culturam a DevOps engineer l have challenges having a genuine DevOps job please how can I go about it
What kind of issues you have? If I can help lemme me know, if you search cultura do caractere on App Store or play store, it’s my app where I share some content
You shed light on a common sentiment in the tech industry. It's not just DevOps; the expectation for a holistic understanding of the SDLC is becoming the norm for software engineers. Embracing continuous learning is the key to staying relevant in our dynamic field.
Very well said!
Continuous learning has been a daily practice for me, I have been in computer engineering jobs for over 40 years. Its not something new, it has been here all along, it is like any other professional career (Doctors, lawyers, dentists etc) , you need to study constantly to stay up to date.
I too started my devops journey recently, you are 100 % right, task over task make us don't stay focused
I've been DevOps Engineer about 5 years and can't land a job for 4 months already because mass layoff and a lot of developers switched to DevOps the market is overheated now.
So u are on the mid/senior level. Could you share your technology stack and the background because for example in Europe u would get like 10+ offers per week.
Yep, sure. AWS and Kubernetes (AWS SAA-C03 and CKAD), also Terraform, Git, Docker, Jenkins, CI/CD with Jenkins, Makefiles, Helm charts, Bash scripting logic, EFK, Prometheus and Grafana. Cloud engineer for 2 years, DevOps engineer for 2.5. But I have an accent so that could be a reason and maybe not but it's how I explain it to myself. Anyway the described situation in Europe looks much more better than here in US.
@@DevOps691 Lol mate, then look for a job in Europe with such a stack I assume that u have highly developed problem solving skills so it shouldn't be a real deal to find job!
@@et2931 Yup, the market in EU is so much better than the US. Not sure what the hell is up with the US lol
learning constantly new things for me is a requirement in tech industry. Everything can be change. I'm full-stack developer, I do some devops sometime, for me, it is difficult because it need you to practice all the time. Otherwise, we can forget most of things after a week not touching it.
Well said!
Man, now I really want to get into DevOps. My ADHD could do wonders for me 🤣😂.
Just started a position as a DevOps engineer. My background is as an SDET engineer, so it was a somewhat unexpected change of pace with regards to the day to day operations. I think this was largely due to my underestimation of the role managing infrastructure plays in the position. I also was under the impression that building out the CI/CD pipelines on which the test run involved actually building said tests, as I was very familiar with in my role as an SDET.
While these assumptions weren't on the mark, I'm still really enjoying the position. I especially enjoy that learning on the job isn't something unique to new engineers, but a constant part of the position which engineers cut out time for at all levels of seniority. I love learning new things, but in other roles felt like it was the mark of a newer dev to spend a significant portion of time learning. I feel like taking the time to learn is expected in the role of a DevOps engineer, which is quite refreshing.
Hey.. I'm working as SQA role and wanna make a switch to DevOps for some time..The problem I'm having is how do I justify my 4 yrs exp in devops..would you like to share your journey from SDET to DevOps and may as well share the roadmap..
please explain why u love devops
“Developer complains that DevOps contains Ops”. All of these complaints are things that operations have been dealing with their entire career. I’m glad people are starting to understand just how exhausting/sucky operations can be. The context switch is particularly brutal. As well as having to constantly relearn everything every 2 years.
re-learing is the strongest advantage of being DevOps.
This is the perspective of a Jr Engineer, and it shows. I'm assuming you worked as a DevOps Engineer at a startup company. If that's the case, sure, it's definitely a grind. But chances are most everyone else across the entire Engineering organization is also grinding. Because, you know, that's how startups survive.
Seems like you're actually into the managing Infrastructure piece. My advice would be to stay with it and eventually join a bigger company. Ideally one that doesn't put DevOps in the job title, and actually respects the fact that managing Infrastructure is its own separate discipline.
You'll come to find the work suddenly feels way more stable, there's no quicksand under your feet (constant learning about new tools and switching to them), your Manager will be more than reasonable about deadlines, and you'll write way more actual code/will have the time to contribute upstream to open source projects.
Thanks for sharing. Just to clarify, I am not saying that I don't enjoy my role at my company. Many of the factors that I touch upon in this video are actually things I see as positives. But I see your point, perhaps the perspective of a senior engineer will be different.
This video is a must-watch. Thanks for making this.
Thanks! Glad you found it useful.
Great video. I am a softawre engineer looking to transition into DevOps. In software the code you wrote last week is already outdated and incompatible with the other library introduced.. I dont think constantly learning is something you don't do in software and I would say you do it as much or more. BTW, with the bad tech market, you have a much better shot at a stable career with DevOps/SRE work than SWE. SWE is quite saturated and the requirements for a software engineer are all over the map from being the architect, back/front end developer to the web designer.
I agree with you 100%, I have 5+ years in SWE and I am transistion to DevOps
@@the_computer_scientist Hello, would you mind sharing your linkedin ? I've recently graduated have very good experience in java but I'm unable to land a job.
I'm thinking of going into DevOps. Do you think this field supports freshers well ?
why please explain to me, I am junior devops and bored. I miss coding.
I am not that good in Infra part, but other things in DevOps are interesting to me.
Got Bachelor degree in Computer Science, Masters in Networks, worked for many years as Software Dev, but wanted to try new things. DevOps seemed quite interesting, because you learn all the time new things, and understand how everything is put together.
It's quite true you can't focus on one thing in particular, but at least this helps you grow somehow and to be more disciplined in a way.
Indeed, all those tasks upon tasks and new things ALL add up to your experience. You will be able to find a job anywhere in the dev (ops) field if you stick around long enough.
Turn disadvantages into advantages people!
I've been in DevOps for a few years. This video is so accurate!
I am excited about this job opportunity as it aligns perfectly with my skills and interests in DevOps. Before focusing on DevOps, I was a Linux user and a backend web developer. I believe my experience in web development has provided me with valuable knowledge that will be useful in my pursuit of learning DevOps. I am eager to gain more experience through an internship in this field.
just be mindfull that it could be very taxing on your time
@@michaelaramis1210 I appreciate your advice. Can you provide more details on what makes it time-consuming? It will help me prepare better
You as a quant of Consciousness were incarcerated on the planet to manage json files! What a life!
I’m a senior System administration working for the DoD cloud infrastructure and just got my Linux+ and DKA (docker) cert. my goal of 2024 is to land a full devops role and pass Terraform cert as well
I am keen to follow your progression. I am on the same path
Funny that I started listening the video and was like "obviously, that's the Ops part of DevOps", I've been in the area more that 15 years (before it was even called DevOps) and what you describe is exactly my job now, and that's what I like, constant challenge, always learning something new (using docker since 0.3 for example, look this new shinny "bsd jail for linux" XD ), always in that "discomfort zone" where you have to figure out how this new tech works and pass it to the rest of the team. Can be challenging at times, but very rewarding at least for me, not everyone is made for that job.
If you are starting in this area let me tell you something: you will never know enough, but you have to keep the wagon moving forward.
"you have to figure out how this new tech works" -
in Production environment, right?
Docker "bsd jail for linux" : haha exactly xD
here I am, a Machine Learning Engineer who also does MLOps from time to time. I love my role because I can scratch all my itch at once. be it DevOps, ML itself and SWE. I can relate twith everything you said.
I have been a DevOps/SRE for close to 10 years now and now and this is my advice for all new engineers:
Start from the fundamentals. Learn Linux and Netowkring basics. Forget about Kubernetes and AWS if you are really new. Start with virtual machines and running different services in it and getting yourself familiar with the basics like webserver, reverse proxies, load balancers, databases etc before moving into cloud or Kubernetes.
You can't run a marathon without learning to walk.
Most companies in my area is looking for software developers with devops experience.
In fact I am going on an intervju soon where they highlighted this.
I don´t think I would be happy only doing devops but for sure I like to be able to manage all aspects of delivering a product so devops is included in that.
Constant learning is the life of a software engineer as well.
Even though I’m an application programmer I like DevOps simply cause I like not being at the mercy of others. I like controlling my servers and optimizing performance with my code and my servers.
I've been a Devops Engineer for 7 years now and this is by far the best video I've ever seen about what we do.
Excellent. I may rewatch this when i have a discouraging day. Thank you for a much appreciated realistic explanation
Based on all the IT and Tech Engineers I have met, DevOps Engineers make less than Software Architects and Engineers, in general! Never done DevOps Engineering but I might consider it! My specialty is hardware, operating systems, networks and software engineering!
This video was really on point 😂 Thanks for making it!
Thank you for this video- I am a project manager for the past 7 yrs and now transitioning into DevOps and this was a great video with excellent advise for someone getting into DevOps.
After 15 years in UX/IxD I was looking for a career change to devops (since is almost a hobby dealing with infra and servers since teenage years discovering slackware, and I never stopped).
Started this video to get some cons perspective and maybe reevaluate the route, but man this got me even more craving for some devops/infra role (most the part 1 and 5, bc my focus is broken and get super bored doing only one thing for days).
Great video, going back to the studies and the job form filling (really hard to get a entrance role these days :( ).
Good to hear!
Don't forget, devs jumping to devops see a better overall view of the industry and the pipeline they work in. Yeah doesn't scratch the coding itch but thay doesn't mean you can build custom CLI tools.
This is one of the best videos about DevOps role, keep uploading videos !!!. Loves your "realistic" takes on DevOps roles instead of highlighting the pro's only.
I'm surprised that theres one thing you don't mention and that is On-Call rotation, if your team lack sufficient amount of resource (both in manpower & infra) then it can be super stressful. And team cohesive/coordination is also super duper important,
I remember that on time we had a major migration, Our SRE Lead managed to split on-call so the teams are not burned out, "It's a marathon, not a sprint" she said, and always ensures checkpoints are introduced. Definitely one of the best Lead I've worked with
Great point, on-call can definitely be hit and miss depending on the team.
I believe that everyone should be into constant learning. That’s really good, and pushes the limit for an individual.
Definitely!
We build our own cloud for internal products. For me it’s puppet, salt, ansible, docker, python, ruby, bash, kvm, groovy, distro images, kickstart, packaging rpm. It’s just endless
Your voice is so soothing and this video has been a fantastic help gaining clarity on what i want in a career.
Great insights mate, I appreciate your video. Sub earned.
I'm an aspiring SWE going into the self taught route. I think your content is great and you present really well! A sub from me!
Thanks for the support!
You are a honest person, thanks. I guess the future is plumbing 😂
You 🫵 my Brother 🤛
I was also blown away, running my first terraform and seeing an EC2 come up, with the ami and subnets I described !! 🤯
Thanks. Interesting vid. I find devOps being a lot more interesting than a "simple" developer. But me being a bit weak at the coding side I find the DevOps role a bit challenging too.
It seems like you spoke my mind, glad to know there are other people who feel the same. Some days are good which you love some are too distracting. I love being challenged so I am enjoying my job.
What was funny is thought this video I thought you WERE trying to convince me to be a devops engineer. I work as a Tech Act Mgr (customer facing system admin) and was looking for the next step as my role is getting a bit too "salesy" and this sounds like the move! Thank you
Good to hear!
It all depends on what software you work on, what product, projects and teams. Working on a narrowly scoped functionality, fixing bugs, dealing with untested spaghetti code copied from SO can be more frustrating and boring than Infrastructure automation. Nowadays many software engineering jobs are plain and simply farming k8s yaml files!
Couldn't agree more to each of these points mentioned. I work as a PKI consultant, the amount of time I spend on that technology is a day to at most 2 days in a week. Rest of is meetings, follow ups about meetings, dependencies on other teams, conducting workshops to increase technology adaptation, only to later discover there is problem with funding.
Companies do not focus on a devops framework long enough for their staff to be moderately competent in it. Board level members and CTO changes the whole stack, that sends ripples down below in a bid to cut costs.
All of this is true, especially if people have dedicated "devops teams", which for me shouldn't exist, its not devops at that point, its a support team.
Exactly
And what's wrong in that ?
@@kipa_chuJust support means it´s only the Ops part of DevOps. Nothing wrong with that, but it´s wrong to call that DevOps. It's plain old legacy Ops support. A purely IT Operations job.
So glad you explained after 8 years of explaining it i'm kinda done@@raulsaavedra709
Great info! Nice presentation too. Very pleasant to watch. Subbed!
Thanks! Glad it was helpful.
It's not only devops, it's everywhere in tech, and even non-tech. For example, many bigger tech companies require passing few coding interviews, but the skill set tested by them is unrealistic: real development and devops require people skills, endurance skills (90% of tasks is boring bugfixing of bugs made by someone else, who probably doesn't even work here) and engineering skills (being able to understand limitations and select the best existing solution). However coding interview checks only coding skills, which constitute maybe 1% of what's it needed for a programmer (for a devops even less), leaving the rest of unchecked, and everyone frustrated: good coders because they got a wrong, boring job, experienced engineers because they have to learn not-used things before interviews (or get rejected) and then similarly - get a boring mostly bugfixing job, HR and mangement because they hire wrong and inefficient people. And it all comes down to the fact that most people in HR and management have no idea what the job of their employees is actually about!!!
Well said!
Great video, and really helpful insights. How about a video about how and from where to learn the DevOps as a beginner ?
Great suggestion, stay tuned!
@@homebrewhenrystay tuned till when
Harsh Reality well articulated
tbf, most "DevOps Engineers" are Cloud Engineers, fancy SysAds or Platform Engineers.
Even most employers dont have a clue what devops really means and so the people that work as so calles devops Engineers.
DevOps is not a single role or function in a team, its whole lot of principles, processes and cultural aspects which define real devops.
DevOps is about building cross functional teams, not being a one man army who knows it all.
Agreed! I think there’s a misunderstanding between what a business thinks is ‘DevOps’ and what engineers think. Hence, all of the job titles that end up being interchangeable.
Thanks for this. Those points from software engineers has swayed me. Cheers for this
Towards or away from devops
stfp bro ur video is popping when someone is just getting started
Thank you! I am an older software developer and was curious what being a DevOps REALLY meant. I absolutely have NOT worked for large companies (intentionally) so this is more speculation. Feel free to correct me where I'm wrong. Here are my thoughts.
"DevOps" and "DevSecOps" is undeniably a very "cool" and "exciting" name, so it's no wonder that companies are jumping on the bandwagon especially with most videos promoting how fast projects will be completed and such. I don't know if the "only 50% of software projects get completed" stat is still true (and/or was ever true) but I can understand why that's appealing to top brass to get projects complete fast.
Perhaps I am a dinosaur or am an exception since I have worked with small companies, but I still don't "get" the whole obsession with Kubernetes, Containers and such and building servers with code, etc, etc. I mean, I GET how cool and powerful it could be from a technical perspective, but being as I'm at core a businessman, it seems like massive amounts of endless work that never really pays off in the end for most small/mid size companies. Again, could be 100% wrong and maybe for large companies it's night and day, but this seems to be a core concept of being a DevOps engineer + using testing tools and such.
Thinking through it, I have to wonder if these big companies have their "core engineers" that specialize as coders, DB admins, server specialists, etc and then have a whole bunch of DevOps at the top level. If this is the case, I would bet that those "core engineers" have it pretty good with an light workload and near guaranteed job security while the DevOps (despite any level of productivity they achieve) are expected to work at max levels and are always at risk of being let go. Why? Because by definition, DevOps people don't need to have DEEP understanding of anything and are expected to learn and adapt... so, how would someone with 10+ years experience be considered better than someone with say 1-5? Those Core Engineers can't be replaced because the difference between someone who KNOWS and Kinda-Knows is the difference between something working and complete disaster.
College is the proof that "well rounded" doesn't really get you anywhere. I would imagine that DevOps engineers are only really good in a DevOps type of company. Smaller companies would expect you to "dig in" and improve things and build new things and that only comes from experience. If all you've done is write some code in basically some sandbox, when you are faced with a "blank page" needing to plan out a project with coding and database you'll just stare at it like you are trying to write a book. No interviewer is going to choose you for a Coding job where people have more experience coding, same for DB, servers, etc. Quantity of knowledge doesn't matter, it's DEPTH.
My guess is that being a DevOps/DevSecOps would be great way to GET STARTED in IT. Get a wide net and cover a lot of bases and find out what type of stuff you like and don't like to do. Once you've found that, you then can migrate to another job (maybe at same or potentially lower pay) that focuses on what you love doing and then you can eventually get in a great job where you have security and a reasonable work schedule.
My thoughts at least :)
Very informative video. Thanks
Well, I want fix job hours but I’m completely fine with the nature of job 👍
As a college student can’t say much bout how corporates devops engineer works. But knowing this is ahead of me if I choose this career i like it thanks.
You will need to learn the other aspects of software engineering when your project isn’t staffed properly.
As a fullstack swe, I agree with your take!
I have been a software engineer for over 10 years but this week I'll be starting a course in DevOps.
I think at this stage of my career, learning about the infrastructure side of things will be beneficial and it seems that the industry may be moving more favourable toward infrastructure.
Definitely! Best of luck with the course
This video's thumbnail and title were quite negative, yet the content of the video was kinda nice and made me more excited about my field xD
Haha, unfortunately that’s the nature of TH-cam! Glad it had a positive overall impression :)
Really drawn to DevOps. Getting my AWS CCP cert soon and then I’m going to get my Terraform Associates. Excited!🤞🏾
Good luck!
I currently work as a data engineer and whenever I can do something infrastructure related I have so much more fun than when I’m writing a pipeline to gather and process some poorly structured data following constantly changing requirements from the product managers. Devops sounds much more in line with what I enjoy. Any advice on where to start? I already know terraform and got AWS SAA cert.
Great to hear! Sounds like you're already most of the way there. I would try something like this:
1. If you don't have them already, get basic skills in Linux, networking and writing CI/CD pipelines (Jenkins seems to be a popular requirement in job listings). You don't need to be an expert in any of these but it's likely that you will get asked questions related to these areas in an interview.
2. Commit to at least 1 cloud provider (sounds like you have already chosen AWS). Get comfortable with the main services.
3. Start looking for opportunities! If your company has a DevOps/cloud platform team, it may be easier to try and transfer to one of these teams. Reach out to them and ask if they have any projects that you can collaborate on.
@@homebrewhenry thanks for the advice! I was planning to look more into networking and CI/CD especially since it's relevant to my current position and I'm so-so with those. Linux wasn't on my radar though, what are some examples of tasks related to Linux?
Unfortunately no DevOps focused team at my company, data engineers deal with DevOps tasks, but it's generally more of a side topic :| even though automation and some neat infra can save a lot of time in the long run, most immediate priorities have to be taken care of, and those are either more data, or nicer data
@@ArekxQQQ Understandable! In that case, it may be worth while trying to introduce some DevOps related projects to the company. A great benefit is that you'll be able to talk about this in any future interviews even for non DevOps roles.
RE: Linux - mainly shell scripting and SysOps-related tasks. For example in an AWS team, this could be making sure that AMIs have the latest packages installed or writing a bootstrapping script for a server. Shell scripting is also used a lot in automation. Definitely do not need to have super in-depth knowledge though.
Thanks man! Currently on helpdesk planning to move out to servers but without opportunities around servers it seems that devops have taken those server responsibilities as well..
I am an infrastructure engineer and that is exactly my day to day. But I have a GREAT Manager.
Everything has a harsh reality but if anyone master that technology it will be valuable
I'm a Devops and I think it is about to game over now. Because I don't see there''s no more openings for the DevOps jobs in my market since the last year. The fate of DevOps role is just like the EA role back in 2 decades ago. The Enterprise Architect thrived only a couple years (2005 - 2010). Then it sank forever. And I saw no more Enterprise Architect jobs available in the market in the past decade anymore. The Devops is on the same path as the EA now. So Devops will be history in a couple years later. Just a waste of time (I earned the title but no future to sustain).
That whole getting people pinging you for various stuff should be directed to a ticket system. I've been a Linux sysadmin for 20 years and that will crush you eventually trying to be the sme for everything because it makes you feel like some kind of god. You aren't. I kinda hate what things have become which is basically all the sysadmin work I did with as much extra as can be crammed in. It kinda depends on the company though how much of that actually ends up happening or not though.
he said he talked me out of a devops engineer, but his demeanor is friendly, smiling, and is breaking down it's format very well?
Thanks?
"You may only have surface level knowledge of certain tools but still be considered a subject matter expert by other people in your company." I thought I was the only one, and it's been hard to deal with. Especially when management gets pushy.. I'm just hopeful I can find something else when they determine that I will never know it all. lol
Loved this video ❤. Thanks so much 😊
Great video for devs to stay devs like me and stop confusing themselves. :-)
Transitioning from Design to DevOps. Here we go.
Thank you for the insights. This really helped making decisions.
Sounds like a good step forward for me being in a Kubernetes support role as learing is pretty much my second nature.
Glad to hear it!
I think that DevOps isn’t a job title, is a culture that involves on everyone in the company. I would describe it as a SRE of Google, but also a SRE have much culture powers than a “DevOps” engineer. Source: sre book from google (oreilly).
I think that PaaS and AI tools now can enable much other functions for cloud engineers to perform. i.e. CI/CD, automation, networks, architecture, observability, maintainability, etc.
As a systems engineer and having worked along side many devops teams I see a couple issues. One the orgs I have been part of put too much on them when we are still there and are pretty capable of helping with these tasks. Two way too many devops team will do all this work and not really ask for our help and then complain about what they have on their plate. Devops teams should be working along side the Saas teams and admins to make this all work and so no one is doing more than they have too.
man all I care about is paying my bills. Ima keep taking software dev, dev ops, info-sec, networking projects etc as they come. Being flexible is how you survive layoffs.
No one thinks there is glitz and glamour in DevOps.
great video bro ,btw what are the Video editing tools you are using ?
Thanks, Premiere Pro.
more videos re devops would be nice to watch. thanks
I find the 2 last points particulary relatable.
Me too!
What I don't like in the industry is that it treats vendors as technologies and half of the field is AWS-engineering where you are a glorified AWS operartor for a lot of the time.
Thank you for putting it out, really not for me. If I'm forced to do such job (visa expiry, threat of starvation) I would, but not out of my free will. It's important to have honest opinions on jobs.
On the 'focus' subject, how do you manage other work that you have that is being managed in agile scrum sprints? My work, although not DevOps, is very similar in terms of demands on my time, dealing with incidents etc. and so i don't think sprints align naturally with it, much to the frustration of managers who want to apply it blindly to everything.
Great question. Unfortunately I don't have an elegant solution to this. I've found it helpful to let my team/manager know as soon as there is a task that may take my attention away from what's in the current sprint. Luckily for me, they are usually quite understanding. If this happens a lot, it may be worth trying to define a more formal process with your manager.
maan, this is a good one, a new sub and a like noti
I don't even know I'm trynna transition from commerce background to DevOps, cool thing about what you have mentioned is that I love troubleshooting things, and I'm open to knew technology and I think since i have opted for DevOps course i barely go out! seems like kinda getting used to it.
I don't even know if they would even consider me for the role or not. (TSE VMware)
Great to hear that you enjoy learning about DevOps. Sounds like a good sign that you’re going to enjoy the job!
I beg to differ.. regarding 1:00 , you are building platforms and software that DEFINITELY is customer facing.. it's just the customer is in this case other developers or in my case.. data scientists working with data.. I am 1000X happier doing that.. than arguing with chrome which pixel to move 1 pixel that way or this way..
Well said and I agree. Building for other devs definitely has it's advantages over building for more 'traditional' customers.
The quality is amazing ❤
Great content, thank you!
Great channel, thanks so much
Amazing video. 7:00 Automation Tasks is real
DevOps is NOT engineering job. DevOps is yaml and json file editing job, and the amount of infrastructure and networking that you need to know is just very small and abstracted by cloud provider GUI, cli and REST interfaces. You are only learning what is specific to that cloud provider, you barely need to know what CCNA has to know, not to mention CCNP or CCIE. The same goes for system engineering and security, you are just scratching the surface of all that doing DevOps.
On the other hand, because it’s abstracted away, you will get to cover more ground and become knowledgeable in many different areas - companies are more than willing to pay for that. You won’t become a networking guru immediately, but as the problems you face become more complex, and you start realising your gaps in knowledge, you will get to dive deeper than the cloud interfaces. You will also get the opportunity to specialise in what you like most, or re-spec if you’re bored with what you do (e.g. from Networks to Data or containers). Not to mention that you will always be able to go back to development - and be rather good at it knowing CI/CD, infra, security, etc.
What do the cisco networking certs have to do with devops? Saying a CCIE has to know more than a devops engineer is like saying an electrician has to know more than a chemist. You are comparing apples with oranges. Building secure deployment pipelines is nothing like maintaining an isp backbone for example. Almost none of the skills are transferable
Yes.. I do devops as part of my software engineering role.. made possible by the abstractions provided by the API we can interact with via CLI or by file manifests.
That is exactly my point, DevOps by itself is not engineering work, but more some kind of administration. I am sorry if DevOps "engineers" are offended by that. Anyway, they are in high demand. But recruiters now call "DevOps" a lot of things, and expect often some programming skills. @@TheStickofWar
Damn, I've yet to have it that easy. I still get called a fraud because of my usage of programming(python, C#, perl, groovy, others) outside of tooling, shell interfaces, gauging OS health w/ classic Sysadmin techniques, SQL querying, and automating using those tools(particularly IaC) with metaprogramming.
I regularly find myself making my own headless apps / services, having to budget my time between maintaining, hardening, automating, and enhancing(i.e.: feature dev).
So you're suggesting I've just been subject to hate? Thats really disheartening
devops jobs are kind of a scam, your not signing up to be a dev you're signing up to be an ops engineer. They sell it as you're doing both like coding, but slapping a terraform script together on the side, no that's not how it works. You are doing infrastructure, probably just infrastructure.
However in all of software the learning doesn't stop, even if you're a normal developer.
I’m looking into switching into the IT-industry and I’m very interesting in networking. What would the biggest difference be between a devops engineer and a systems engineer? Is a systems engineer more ”practical” while devops is more project managing? How would you best explain the difference?