I ran across this video the other day that I thought did a great job of summing up all the reasons why I intend never to touch GenAI bullshit.
And it’s from a former “vibe coder”. I’ll definitely be keeping this in my back pocket to share with people who ask me why I eschew GenAI.
More than half of job postings I seen now require proficiency with AI agents and I have never used one. Our company has copilot set up to do code reviews (after which humans also review it), but I will likely be out of the job soon. It’s killing me.
I really wish Programming. dev werent so pro-AI, makes it harder to talk about issues like these to other programmers.
I know, how dare the people who support technology in the technology instance. Parish the thought.
Perish.
- Be Pinto, the Bean
- Visit /c/fuck_ai
- People there hate AI
- Pinto, the Bean:

I get it. I really, really do. But if the tools stick around and remain affordable (and the if is load bearing) I think it will be difficult to have this stance and remain in employment in modern software companies.
Maybe there will be anti-AI software shops or you can work in places that are entirely backwards (I mean I once worked at a place where a developer was basically maintaining what would normally be a database using a series of Java collections so … not everyone is going to be on the “cutting edge”).
The posters’ qualms are exactly right. You become more of like a business analyst and/or tester rather than a programmer when writing code using these tools. However, that’s what will be needed for the creation and maintenance of software if these tools stick around, remain in use, and remain affordable.
It 100% feels like developing software with a cheat code enabled using claude code and friends and I think it likely leads to apathy about what you’re developing in probably most cases, but 🤷. Most software written before this was seemingly made by people who didn’t care at all about the people using it so I’m not sure that changes much of anything.
I do, however, think the “my website has a chatbot” and “try to one shot a bug fix using my token workflow” things that have sprung up everywhere are entirely useless and will quickly find a graveyard when the bubble bursts.
I consider myself a mediocre developer, I have a security+ and a year of experience, before getting my bachelor’s. I am by no means an expert in coding or such, but even then, I can’t stress just the number of completely abysmal experiences I’ve had with AI coding tools, there are dozens of individual examples I can list but it’s easier to just talk about the central problems instead.
-
it writes incredibly inefficient and/or broken code, following almost no coding standards or guidelines, it will also gladly take a broken foundation and build on it.
-
context window is either lost or slowly poisoned, the “best” models(up to 1m tokens) can barely keep up with re-writing single files, since it needs to keep the whole file in-context before editing, let alone whole project (20+ files cohesive changes are basically still a fantasy)
-
“suggestions” during development are just hyper idealistic google fetch results, it retrieves anything in the first page mildly related to some keywords and tells you “so, those are basically your options” otherwise it just flat-out refuses or massively overcomplicates certain implementations
-
incapable of noticing errors or debugging proactively, it is essentially blind to all coding errors unless you keep referencing or correcting the results, you must now sit there and QA and babysit
-
incapable of learning or improving, you can tell it in detail about a mistake it made, it will sincerely apologize, then moments later repeat the exact same mistake
The list can go on forever but the last one alone would be a fireable offense for any employee in a company, I’m not sure why this shitbox is getting preferential treatment, but it’s whatever I guess
It 100% does all of the things you’re saying. Using these tools to produce things that are not 100% rubbish requires: (1) for you to be a babysitter, (2) for you to set standards early on using automated checks, and (3) for you to generally understand on a large scale how a software project typically runs.
That’s where I just don’t see software developers being obsolete even with these tools. Managers and directors will not be able to produce anything but garbage that doesn’t work using them.
A big issue IMO is that entry level programmers are likely also not going to be capable of running them with much success.
-






