As developers increasingly lean on AI-generated code to build out their software—as they have with open source in the past—they risk introducing critical security failures along the way.
Vibe coding works when you need to say connect to some API and can feed the model a bunch of docs.
It’s great for very low skill, low maintenance, low risk code that I can easily and reliably regenerate.
Increasingly coding models are improving at architecture choices, Claude 4.5 vs 4 is way better here. But ultimately it’s inferior to a ginger making those choices.
It’s also a great debugger and reviewer.
I used it this weekend to connect to an API and to build a table of constants by just feeding it docs. That was a huge time saver.
I also used it to try and implement stuff and I gotta say once it hit tricky things it started trying to game it and just say it works.
thats totally the type of code I have written. granted I really consider it more configuration even if it is code. This is always a thing with jobs. Yes I have written code but no im not really a coder by my definition (writes code over 50% of time at positions). No you don’t really need a coder for this ops role but yeas its fine that it uses continous development and a bit of code needs to be changed and you call it all devops.
I’m a dev and work with some devOPs, and you nailed my experience with them exactly! Here are some projects I’ve seen them build:
open web ui (self-hosted AI) with some custom logic to verify an API key; it’s only available on the VPN/LAN, but IT has rules; basically ended up being a bit of lua in nginx
some JS and Python to add some widgets to the app (stuff like reporting issues)
random lambdas and other scripts to check server health
I remember doing all that stuff when I worked at a startup, and it’s nice to just see things get automated.
Like half my last role was pretty much automation. Which is sorta good and I guess maybe why devops is a better way to look at it. Back when it was just ops it seemed like they would never give time to get things like automation done.
Vibe coding works when you need to say connect to some API and can feed the model a bunch of docs.
It’s great for very low skill, low maintenance, low risk code that I can easily and reliably regenerate.
Increasingly coding models are improving at architecture choices, Claude 4.5 vs 4 is way better here. But ultimately it’s inferior to a ginger making those choices.
It’s also a great debugger and reviewer.
I used it this weekend to connect to an API and to build a table of constants by just feeding it docs. That was a huge time saver.
I also used it to try and implement stuff and I gotta say once it hit tricky things it started trying to game it and just say it works.
GINGERS DO HAVE SOULS
thats totally the type of code I have written. granted I really consider it more configuration even if it is code. This is always a thing with jobs. Yes I have written code but no im not really a coder by my definition (writes code over 50% of time at positions). No you don’t really need a coder for this ops role but yeas its fine that it uses continous development and a bit of code needs to be changed and you call it all devops.
I’m a dev and work with some devOPs, and you nailed my experience with them exactly! Here are some projects I’ve seen them build:
I remember doing all that stuff when I worked at a startup, and it’s nice to just see things get automated.
Like half my last role was pretty much automation. Which is sorta good and I guess maybe why devops is a better way to look at it. Back when it was just ops it seemed like they would never give time to get things like automation done.