Time/workload pressure is forcing me to vibe code automations that I don't understand. What's the cleanest way to approach it?
retained text
I know what you're going to say and believe me, you're preaching to the choir. I'm already looking for an out, this is just to keep me sane while I'm stuck here. For some background, my company has been absolutely gutted this year and to absolutely nobody's surprise, we have individuals taking up work previously managed by whole teams. I am one such individual and I find myself drowning in routine admin jobs that, frankly, should've been automated by now. The big examples are REST API updates to some of our SaaS products, ITAM, IAM, etc. Some IaC thrown into the mix for routine deployments of short-lived VMs from an image gallery we maintain. My scripting is appalling and I have nobody to lean on, so I need to start using AI to write scripts for me. I'm pretty comfortable with constructing the automation logic and the "architecture principles" of scripting, so I won't be doing anything stupid like hard-coding my API keys into it. My specific worry is that I won't recognise hallucinated/destructive commands (E.G. it tells me -a means "append" but actually it means "annihilate"). I'll be testing the crap out of these in sandbox environments before they go anywhere near anything important, but other than that, is there anything I can do? Or am I just stuck with trial & error until I absorb enough through osmosis that I can start spotting it myself? **Edit:** I can't reply to everyone but thanks for the responses. After spelling out my reasoning a few times, I think I'm just being overly critical of myself for **not** having an encyclopaedic library of all scripting languages & commands, and I'm just nervous that nobody here can code review it for dummy mistakes. AI is a red herring.
document fetched 2026-09-24 00:40 · canonical https://reddit.com/r/sysadmin/comments/1wo7gmf/timeworkload_pressure_is_forcing_me_to_vibe_code