r/devops • • Sep 12 '26 Mindblown Popcorn Heartwarming

Architecture The end of Software Engineering

Post image
3.6k Upvotes

r/devops • • Jan 13 '25

I automated myself out of my job. That's a first.

3.3k Upvotes

I expected it to happen at some point in my life, but not that early.

Worked at a smaller company (30 devs) - it was pure hell at the beginning.
Within about three years we fixed every problem and automated/standardized everything that might disturb the developers workflow. I tutored everyone and documented everything. We actually got the ball rolling to a really sweet spot.

The last few weeks were pure boredom. Since there were no legit projects left.

Well. Now they kicked me out of the company. Nothing left to do.
I'll get full salary for two months and don't have to work a second anymore.

WTF?


r/devops • • May 19 '25

After 24 years in IT, I'm done.

3.2k Upvotes

I don't want to debug another fucking YAML file.

This is not how I foresee spending my life.

Thank you.


r/devops • • Feb 13 '25

Thank you all and Goodbye!

2.3k Upvotes

I got told I'm affected in VMware's latest layoffs, and I've decided to quit tech after 10 years and focus on my knifemaking hobby to be more consistent in delivering orders on time :D

Reading this sub throughout my career has been so helpful professionally, so thank you all! Wishing everyone's servers/deployments good health! Goodbye!


r/devops • • Apr 16 '25

Been doing interviews for my org. What the fuck is going on. NSFW

2.0k Upvotes

5 interviews for mid level devops.

No one can differentiate between a NAT and an LB.

No one knows databases.

OSI layer? it might aswell be frosting layer on an icecream cake.

"A container is a lightweight version of a VM"

"Redis has latency issue thats why they use etcd for k8s"

These guys have experience on their resumes that amount to 7 - 10 years so they get past the initial interview.

But you know what they're absolutely fucking best at? Talking for an hour about what they work with and how they saved their org by clicking a button on AWS.

Im seriously sad how companies are defining devops. They are hiring people to press buttons in a web ui


r/devops • • Sep 08 '26 Bravo Heartwarming

Discussion how much you agree with this

Post image
1.8k Upvotes

what you think about this ?

credit - https://xkcd.com/2347/


r/devops • • May 21 '26 Helpful Bravo

Discussion Today is why i no longer have the desire to work in IT anymore

1.8k Upvotes

I have over 20yrs experienced and have been a lead for the last 10 years of my career. Im usually the one people go to for help and the one folks come to when junior members cant figure things out. With AI, i have a love hate relationship with it. Im old school, i prefer VI to vscode and with AI i just refuse to accept it. Anyways, today we had an issue in prod. A mid-level engineer went straight to claude. He couldnt figure out what the issue was. He runs out salt code through claude and in claude's defense, it did point out what the root cause was.

Now, because everyone nowadays depend heavily on AI, you'd think ppl wouldve spent the time to actually check the nginx config and see if they were different between our prod environments. No, everyone waited a few hours for me to confirm when all i did was compare our 3 prod env and yes sure enough they were different. Problem solved once we pushed out the correct config.

I think people lost the ability to think for themselves. What im seeing in my org is folks go straight for claude. If you use it right it works but i cant count the number of times i tailed log files in the past few weeks and managed to figure out root cause without using AI.

Lately, we have been told to leverage AI heavily. I found out they are also tracking our token usage. If that is true, then im at the bottom of the list in terms of adoption. I guess they can fire me and keep the folks who use claude for everything while they fumble to address prod issues because claude doesnt have all the necessary information regarding our infra and app.

End rant


r/devops • • Jun 01 '26

Tools Crosspost from ProgrammingHumor

Post image
1.7k Upvotes

r/devops • • Jun 15 '26

Discussion Break the vicious cycle

Post image
1.5k Upvotes

I say it kindly, because I want my AI to think I'm one of the good ones, when it ultimately takes over the world

from ijustvibecodedthis.com (the ai coding newsletter)


r/devops • • Apr 26 '26 All Seeing Upvote

Discussion r/devops nowadays

Post image
1.4k Upvotes

for meme Monday


r/devops • • Aug 06 '25

Every startup wants "DevOps", until they realize what it actually takes

1.4k Upvotes

I’ve lost count of how many early-stage teams want CI/CD, infra-as-code, multi-env setups, monitoring, rollback, zero-downtime deploys… all before even having stable revenue.

And they assign it to a solo dev or junior engineer as a “side task”.

Meanwhile:

No one owns infra debt. No budget for proper tooling.

Everyone wants “just one more feature” instead of paying infra tech debt.

When something breaks in prod, it’s magically “DevOps’ fault”.

DevOps is not a checkbox. It’s a long-term investment that touches culture, workflows, and team maturity.

You either take it seriously, or you're just writing TODOs that'll bite you in 3AM alerts later.


r/devops • • Jun 28 '26

meme Monday

Post image
1.4k Upvotes

r/devops • • Aug 26 '24

Juniors using chatGPT are driving me insane

1.3k Upvotes

Zero critical thinking. I have a few people who have faked their way into roles and am now stuck with them, unable to do any work that requires more than a minute of thinking. Is this happening everywhere? All I get is copy/paste output from chatGPT for the most basic questions and it makes me fear about where we're going as a society with all this dumb shit and individuals that AI is creating


r/devops • • Dec 30 '25 Polished Gold Turd Thanks Bravo

AI content I'm rejecting the next architecture PR that uses a Service Mesh for a team of 4 developers. We are gaslighting ourselves.

1.2k Upvotes

I’ve been lurking here for years, and after reading some recent posts, I need to say something that might make me unpopular with the "CV-Driven Development" crowd.

We are engineering our own burnout.

I've sat on hiring panels for the last 6 months, and the state of "Senior" DevOps is terrifying. I’m seeing a generation of engineers who can write complex Helm charts but can’t explain how DNS propagation works or debugging a TCP handshake.

Here is my analysis of why our industry is currently broken:

1. The Abstraction Addiction We are solving problems we don't have. I saw a candidate last week propose a multi-cluster Kubernetes setup with Istio for a simple internal CRUD app. When I asked why not just use a boring EC2 instance or ECS task, they looked at me like I suggested using FTP. We are choosing tools not because they solve a business problem, but because we want to put them on our LinkedIn. We are voluntarily taking on the operational overhead of Netflix without having their scale or their headcount.

2. The Death of Debugging To the user who posted "New DevOps please learn networking": Thank you. We are abstracting away the underlying systems so heavily that we are creating engineers who can "configure" but cannot "fix." When the abstraction leaks (and it always does, usually at 3 AM), these "YAML Engineers" are helpless because they don't understand the Linux primitives underneath.

3. Hiring is a Carnival Game We ask for 8 rounds of interviews to test for trivia on 15 different tools, but we don't test for systems thinking. Real seniority isn't knowing the flags for every CLI tool; it's knowing when not to use a tool. It's about telling management, "No, we don't need to migrate to that shiny new thing."

4. Complexity = Job Security (False) We tell ourselves that building complex systems makes us valuable. It doesn't. It makes us pagers. The best infrared engineers I know build systems so boring that they sleep through the night. If you are currently building a resume-padder architecture: Stop.

If you are a Junior: Stop trying to learn the entire CNCF landscape. Learn Linux. Learn Networking. Learn a scripting language deeply. If you are a Senior: Stop checking boxes. Start deleting code.

The most senior thing you can do is build something so simple it looks like a junior did it, but it never goes down.

/endrant


r/devops • • Mar 03 '25

Words of my CEO - „Why hire juniors when single senior with AI can do work of 10-20 of juniors”

1.2k Upvotes

Its silly how tides have turned in IT.

Beside offshoring to cheaper countries, AI seems to be the new way to push ppl to do more and more with less staff on the board.

CEO said he literally sees zero reasons to hire junior ppl now. GPT seems to be on a level good enough to replace all of them. AI agents replaced all of our less senior testers, support call centre was replaced by AI call center, junior devs fired and replaced with 1/10 of seniors with AI at hand.

Funny thing is company did not slow down, rather got faster releases, # of issues decreased and overall customer satisfaction went up.

Sad days to be someone starting IT journey or students. You will have to grind mcdonald till you pass mid/senior position check before landing a job soon :/

On the other hand - amazing news for Senior ppl in less expensive countries.

This looks like the times when switchboard phone operators were replaced by a handful of ppl who maintained automatic switchboards.


r/devops • • Oct 29 '25

AI was implemented as a trial in my company, and it’s scary.

1.1k Upvotes

I know that almost everyday someone comes up and says AI will take my job and I’m scared but I promise to keep this short and maybe different.

I am currently a junior devops, so not huge experience or knowledge, but I was told that the team are trying to implement Claude code into vs code for the dev team and MCPs for provisioning and then later for monitoring generally and taking action when something fails.

The trial was that Claude code was so good in the testing, it scared me alittle, because it planned and worked with hundreds of files, found what it needs to do, and did it first try (now fully implemented)

With the MCP, it was like a junior devops/SRE, and after that trial, the company stopped the hiring cycle and the team is kept at only 4 instead of expanding to 6 as planned, and honestly from what I saw, I even think they might view it as “4 too many”.

This is all happening 3 years after ChatGPT released, 3 years and people are already getting scared shitless. I thought AI was a good boost, but I don’t think management would see it as a boost, but a junior replacement and maybe later a full replacement.


r/devops • • Nov 09 '25

Just realized our "AI-powered" incident tool is literally just calling ChatGPT API

1.1k Upvotes

we use this incident management platform that heavily marketed their ai root cause analysis feature. leadership was excited about it during the sales process.

had a major outage last week. database connection pool maxed out. their ai analysis suggested we "check database connectivity" and "verify application logs."

like no shit. thanks ai.

got curious and checked their docs. found references to openai api calls. asked their support about it. they basically admitted the ai feature sends our incident context to gpt-4 with some prompts and returns the response.

we're paying extra for an ai tier that's just chatgpt with extra steps. i could literally paste the same context into claude and get better answers for free.

the actual incident management stuff works fine. channels, timelines, postmortems are solid. just annoyed we're paying a premium for "ai" that's a thin wrapper around openai.

anyone else discovering their "ai-powered" tools are just api calls to openai with markup?


r/devops • • Sep 25 '22

5 Year into the DevOps industry and here's my learnings and experiences documented in git (~300 DevOps Tasks)

1.1k Upvotes

Hi amazing people,

TL;DR

  • I have documented my 5 years journey in devops by creating nearly 300 tasks and still growing.

  • You might want to checkout the [learn-devops](https://github.com/codeaprendiz/learn-devops)_ for the same.

  • Would love feedback here about how I should go forward. I am thinking of starting a youtube channel and giving back to the community.

The Long Talk

  • I started my carrier as SE in Walmart. Stayed there for for like 1 year. Got an opportunity to work in Dubai and moved to DevOps eventually and have been in the industry for 4 years now.

  • I had a habit of documenting everything I learn.

  • I got this amazing advice from one amazing person that we should always learn new tech by doing small tasks consistently and by the time you reach to task 50 or 100, you are way ahead from where you started.

  • So I started dividing all my learnings in small tasks and still doing the same. Anything I want to learn, I would go here and add another task about the new tool or tech.

  • So far I have created nearly 300 tasks here https://github.com/codeaprendiz/learn-devops including following stack

    • cloud-providers (aws and oci)

    • containers (docker and docker-compose)

    • container orchestration (kubernetes)

    • datebases (mongo, mysql, postgres)

    • Infrastructure As Code (terraform-aws, terraform-oci, ansible)

    • Interview Tasks (legit interview tasks, for an annual pay of 80k to 100k USD in dubai)

    • OS and Concepts (linux commands and concepts)

    • Programming languates (go, python, shell, nodejs, javascript)

    • Productivity

    • Version Control (git)

    • WebServers (nginx)

  • There a lot more I need to learn but I figure why not start my own youtube channel. Afterall the best way to learn is to teach. Only then you understand how much you know.

  • What do you amazing folks think :) ?

EDIT on 4th Dec - 2022

I started a youtube channel.

Breaking DevOps into smaller tasks. Currently posting only practical tasks.

Channel Link - https://www.youtube.com/@thecloudterminal

Git - https://github.com/thecloudterminal01/learn-devops

Would love some feedback here.


r/devops • • Mar 27 '25

I'm about to walk away because software stole my life

1.1k Upvotes

I've spent the last year thinking about this. I kept telling myself it would get better. That if I worked hard enough, if I gave it time, things would fall into place. That I’d meet someone. That I’d stop feeling like I was running out of time.

But none of that happened. And I don’t think it ever will, not while I’m here.

Right now, I’m still employed at a major tech company. They keep offering me raises, more responsibilities, reasons to stay. And maybe I will, for another week. Maybe two. But I don’t see a future for myself here. Not one that makes sense.

I love coding. I love the challenge. But this job has taken everything from me outside of work. I’ve spent years buried in deadlines, sitting in meetings that go nowhere, fixing problems that shouldn’t exist, chasing promotions that don’t matter. And all the while, life kept moving without me. Friends got married. Had kids. Built something real. And I just kept working.

I tell myself it’ll change. That I’ll finally have time to date when work calms down. That I just need to push through this project, this quarter, this year. But it never calms down. It never ends. And I’m still alone.

I see people who have what I want, real connections, real experiences, a life that means something outside of work. And I know I’ll never have that if I stay.

I haven't quit yet. But I will. Maybe next week. Maybe the one after. But soon.


r/devops • • Nov 01 '22

'Getting into DevOps' NSFW

1.0k Upvotes

What is DevOps?

  • AWS has a great article that outlines DevOps as a work environment where development and operations teams are no longer "siloed", but instead work together across the entire application lifecycle -- from development and test to deployment to operations -- and automate processes that historically have been manual and slow.

Books to Read

What Should I Learn?

  • Emily Wood's essay - why infrastructure as code is so important into today's world.

  • 2019 DevOps Roadmap - one developer's ideas for which skills are needed in the DevOps world. This roadmap is controversial, as it may be too use-case specific, but serves as a good starting point for what tools are currently in use by companies.

  • This comment by /u/mdaffin - just remember, DevOps is a mindset to solving problems. It's less about the specific tools you know or the certificates you have, as it is the way you approach problem solving.

  • This comment by /u/jpswade - what is DevOps and associated terminology.

  • Roadmap.sh - Step by step guide for DevOps or any other Operations Role

Remember: DevOps as a term and as a practice is still in flux, and is more about culture change than it is specific tooling. As such, specific skills and tool-sets are not universal, and recommendations for them should be taken only as suggestions.

Please keep this on topic (as a reference for those new to devops).


r/devops • • Jul 20 '21

How do I become a carpenter

1.0k Upvotes

Any good suggestions ?


r/devops • • Jan 20 '25

I just worked on a project that optimized 95% of our package build time

965 Upvotes

So long story short, my director pointed out that other teams complained that our package build time was too long (1 hour). And those other teams were depending on this package to build. So it caused a huge bottleneck within the org.

So he asked me to look into it, and I was like, fine... First, i saw we were building two ruby versions sequentially, so I cut the time in half by just removing one release version since that one was deprecated (Ruby 2.5).

Then, I saw we were spending most of our time on running tests, so I was like, let me parallelize it. Then it cut build time to 15 minutes (from 30 minutes).

Finally, I kept thinking, can I do better? Then I realized our tests relied on a lot of I/O reads, and that can be cached into memory since it's fairly small (250MB). The in-memory cache I implemented ended up making the build time to be around 2 minutes.

I pushed the change out and wrote an email about it internally. All the other engineers went crazy because the efficiency improvement was so drastic (went from 60 minutes to 3 minutes).

This is crucial because now we can push code through the pipeline faster, and people can run local builds faster. It's a win-win situation across the board.

What are your success stories?


r/devops • • May 13 '25

im finally a DevOps Engineer

936 Upvotes

5 years ago I had zero college, zero experience, no certifications, and no marketable skills coming out of the army. i set the goal for myself to become a DevOps engineer and today I did it.

got into IT with zero experience and one certification in 2020 when i got out of the army infantry.

first job was help desk, then sysadmin, then a couple tier 2/3 remote support positions including as a RHCSA at red hat. then i got a sysadmin position for my current company in August of 2023.

i worked my ass off. i have built full terraform/Terragrunt modules, deployment pipelines, and incident response tools for our clients, who are some of the biggest tech organizations in the world. google, zoom, red hat, Microsoft, etc... I do this across multiple cloud providers based on client needs. it's actually kind of shocking the amount of work we do at the level we do given the size of our team. I'm the only systems person and I get to touch infrastructure for large organizations on a regular basis.

today i got the email that i have officially been promoted to DevOps engineer.

im really proud of myself. I barely graduated high school because of my ADHD. I did well in the army but the violent environment was not good for my soul. college is very uncomfortable for me. I wasn't sure if I'd ever make a good living, let alone doing smart people stuff.

when I was getting into IT I looked for the most lucrative positions. then looked for the one that I thought seemed the most interesting and that was DevOps. now im a DevOps engineer.

I'm really proud of myself.


r/devops • • Jul 04 '22

DevOps is a subset of Software Engineering. Stop all this madness of "Software Engineer vs DevOps"

934 Upvotes

DevOps started as a philosophy, a way to bridge the gap between operations teams and software engineering teams in-order to provide more efficiency and transparency. Why should people who develop the software not care about how it operates? Why should the people who operate the software not care about how it was developed?

Fast forward to today, and the philosophy has actually become a job title.

In the modern day and age, the term "Software Engineer" is actually meaningless. Software Engineering is a gigantic field with many subsets.

Some of these subsets include:

  1. Web Development (this can be farther split up into fullstack, frontend, backend)

  2. Mobile Development (can be split up into fullstack, frontend and backend as well)

  3. Game Development

  4. Embedded Systems Engineer

  5. Data Engineering

  6. Machine Learning Engineering

  7. Virtual Reality Engineering

  8. Desktop Application Developer

  9. "Low Level Developer" (things like Operating Systems, Kernels, Compilers, etc)

  10. Dozens of others I can't remember at the moment

Do you want to know another subset? DevOps!!

Yes, DevOps in the modern era is nothing but a subset of Software Engineering. That's going to trigger a whole lot of people who come from the operations side of things (which is 90% of this sub), but it's true.

Modern DevOps = A software engineer who focuses on infrastructure, automation and internal tooling. These are the folks who write code to make sure that all the other code that was written, works as expected. They also write code to make writing code easier!

Sure, they may use more pre-made tools than web developers. But web developers use plenty of tools and pre-made services too. Modern web development in fact, is all about gluing together pre-made services, and there's plenty of subsets that I listed above that are tool heavy too (like data engineering), but I digress.

Synonyms to the "DevOps Engineer" title include:

  1. Platform Engineer

  2. Cloud Engineer

  3. Infrastructure Engineer

  4. Systems Engineer

  5. Site Reliability Engineer

and probably a few dozen I can't remember right now.

Yes, the titles in the industry are a mess. But I hope this clears things up for you.

That's why it's silly to say "Software engineer vs DevOps". It's like saying "What's better, a vehicle or a truck??"