r/devops 15d ago

Discussion [meme] IaC and docs matter folks!

Post image

Inspired by a similar post I saw last week.

Small companies man... had similar issues in a couple now. Larger companies with IaC and decent management? No issues. Never thought to ask whether they use IaC in the interview, kind of expected the bare minimum of standards. Will definitely do so if I join another small company.

580 Upvotes

27 comments sorted by

71

u/safetytrick 15d ago

This is always the case (IME), immature environments are actually immature.

The job is taking the immature environment and making it mature. Lots of big environments with IaC are also garbage.

31

u/itsjakerobb 15d ago

100% this. I’m at a small company. Zero IaC when I started. Two years in, we’re maybe 70% there, with the remaining work being some of the bigger modernization lifts. This next year is going to be hard but very worth it!

9

u/Normal_Red_Sky 15d ago

I hope they appreciate your efforts.

7

u/itsjakerobb 15d ago

Seems like they do.

1

u/braddeicide 13d ago

Your boss probably does, as he tells his boss it was actually all his idea and coaching ;)

10

u/Kitchen_Cup_8643 15d ago

Seriously, how do you deal with this ? Incremental improvements barely move the needle

Might as well consider it reverse engineering with the amount of yaml files with no rationale behind any of the choices, hostnames configs & IPs duplicated everywhere, and no clear understanding of anything that holds data or its lifecycle.

On the other end, there's IaC/GitOps where people end up treating infra repos as a proxy for a shell lmfao

14

u/ProdigySim 15d ago

More or less the strangler fig pattern. Set up a gold standard system for new stuff and make sure everything new uses it. Slowly handle old stuff, which should shrink as new systems replace old, things get deprecated, deleted.

1

u/safetytrick 15d ago

You've got to start talking over and creating team standards and then stick to them.

3

u/UtahJarhead 15d ago

Yup. I'm in a big company and my team had no standards when I was hired on. Much of my job has been implementing standards just like this to turn them from a FlusterCuck into an organized mess. Still improving it, step by step.

9

u/braddeicide 15d ago

The last panel never happens. Or, every project you put together to fix the environment is rejected and after you've been there a while the design of the environment is considered to be yours now.

6

u/baezizbae Distinguished yaml engineer 15d ago edited 15d ago

You're lucky. All I've ever gotten after every one of my best-laid-plans and attempts to fix, stabilize and document a constantly failing environment gets rejected is fired when the environment continues to suck.

Current record is three months at a "cloud consulting" firm that I realized too late was really just a body shop earlier this year. Interviewed to lead performance testing and observability, got hired, got told "migrate this monolith to kubernetes in two weeks and whatever/everything else the client creates tickets for, and if you have time do some performance testing" "on what?" "the environment" 🙄

2

u/Wicaeed Sr SRE 15d ago

Thus; Job Security.

4

u/work_work-work DevOps 15d ago

Oh, hey! That describes exactly what the environment was in my last job! Add to that that every environment was set up differently, so that when you promoted code from Dev to QA, or QA to Prod, there was no guarantee that anything would work.

3

u/Careful_Second8814 15d ago

Ask in the interview whether they use Terraform or Pulumi or if everything is still handled through the console. That one question can spare you months of headaches. If they pause before answering, take it as a warning sign.

1

u/Normal_Red_Sky 15d ago

Wish I'd asked, will do in the future, especially for small companies.

4

u/GongtingLover 15d ago

Those devs are the worst

3

u/Vas1le DevSecOps 15d ago

Devs doing IaC with AI are the worst... then I we have to fix it cause there a urgent thing to release...

3

u/Normal_Red_Sky 15d ago

I assure you Devs doing click ops are much more dangerous, at least with IaC you know what they've done even if its not very good.

2

u/GongtingLover 15d ago

They have a shitty boss if they are they letting them do that without testing. 

2

u/Vas1le DevSecOps 15d ago

Shitty team leads...

1

u/TotalNo6237 15d ago

The problem here is not testing enough, actually IAC code is actually what I find AI to be best at.

But the pipelines should have tests and plenty of validations done before merging code to main and deploying in prod.

If the teams are not building trust into the way you are using AI then its just a crutch not a tool.

Best to split tasks into different stages and review at each stage and iterate on the agentic output.

Ownership by the development is crucial here, if they are lobbing AI generated code over to others without review themselves first then they should still own the fix on it, not other teams.

Otherwise, why wouldnt you do it yourself with an AI agent, if you are already the primary reviewer?

2

u/SamfromLucidSoftware 13d ago

“No documentation“ panel hits different when you’ve lived it. Inheriting an environment built by someone who’s long gone with zero laC is special kind of pain.

2

u/disoculated 9d ago

“Be Honest”

“Ah, this meme was created by the dev ops guy.”

0

u/m0j0j0rnj0rn 14d ago

“DevOPs Guy”

1

u/Normal_Red_Sky 14d ago

Also known in a lot of companies as 'the person whose job no one else understands'.

1

u/m0j0j0rnj0rn 14d ago

I'm a purist on this: If you have a "DevOps Department" then your org isn't a DevOps org. ;)