this post was submitted on 07 Jul 2025
1237 points (99.0% liked)
Technology
72610 readers
3640 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Retired dev here, I'm curious about the nature of "the mess". Is it buggy AI-generated code that got into production? I know an active dev who uses ChatGTP every day, says it saves him a hell of a lot of work. What he does sounds like "vibe coding". If you're using AI for grunt work and keep a human is in the workflow to verify the code, I don't see how it would differ from junior devs working under a senior. Have some companies been using poorly managed all-AI tools or what? Sorry for the long question.
essentially, from what I've been dealing with, most if it is their offshore people using the AI to completely do the job from start to finish and no one is verifying anything. So it's not even vibe coding, it's "here's a prompt, build it, i'm pushing it to production" coding.
LOL, sort of like hiring the CEO's unemployed brother in law to build your new factory because he has a friend who knows about construction.
An example from work a few weeks ago. I fixed some vibe coded UI code that had made it to prod. The layout of the UI was basically just meant to be an easy overview of information relevant to an item. The LLM had done everything right except it assumed a weird mix of tailwind and bootstrap, mixing and matching css classes from both. After I implemented the classes myself it went from a single column view to grids and nested grids grouping the data intuitively. I talked with the dev who implemented it, and basically it was just something quickly cobbled together with AI until it was passable. The AI had added a lot of extra that served no function and that didn’t conform to a single css framework, but looked like it could. For months noone questioned it despite talk about that part of the UI needing a facelift.
I don’t know how representative it is, but about half the time I’m thoroughly confused about a piece of code and why it was written the way it was, the answer has turned out to be AI. And unlike when a developer wrote it, there rarely is any reason to have written it the weird way.
TBH that sounds like a lot of code I've seen from outsourcing companies in India. Their typical approach is to copy an existing program, module, web page or whatever and modify it as quickly as possible to turn it into what's needed. The result is often a mishmash of irrelevant code, giant data queries that happen to retrieve some field that's needed along with a ton of unnecessary crap, mixing frameworks, etc.
Think of AI as a hard working, arrogant, knowledgeable, unimaginative junior intern.
The vibe coding is great for small, self contained tasks. It doesn't scale to a codebase (yet?).