this post was submitted on 30 Sep 2025
839 points (98.5% liked)

Technology

75634 readers
3467 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. 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.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
 

"No Duh," say senior developers everywhere.

The article explains that vibe code often is close, but not quite, functional, requiring developers to go in and find where the problems are - resulting in a net slowdown of development rather than productivity gains.

you are viewing a single comment's thread
view the rest of the comments
[–] Warl0k3@lemmy.world 85 points 19 hours ago* (last edited 19 hours ago) (7 children)

There's some real perks to using AI to code - it helps a ton with templatable or repetitive code, and setting up tedious tasks. I hate doing that stuff by hand so being able to pass it off to copilot is great. But we already had tools that gave us 90% of the functionality copilot adds there, so it's not super novel, and I've never had it handle anything properly complicated at all successfully (asking GPT-5 to do your dynamic SQL calls is inviting disaster, for example. Requires hours of reworking just to get close.)

[–] Feyd@programming.dev 80 points 19 hours ago (1 children)

But we already had tools that gave us 90%

More reliable ones.

[–] MaggiWuerze@feddit.org 15 points 9 hours ago

Deterministic ones

[–] Sibshops@lemmy.myserv.one 21 points 19 hours ago (2 children)

Fair, I've used it recently to translate a translations.ts file to Spanish.

But for repetitive code, I feel like it is kind of a slow down sometimes. I should have refactored instead.

[–] cam_i_am@lemmy.world 6 points 3 hours ago

This is a thing people miss. "Oh it can generate repetitive code."

OK, now who's going to maintain those thousands of lines of repetitive unit tests, let alone check them for correctness? Certainly not the developer who was too lazy to write their own tests and to think about how to refactor or abstract things to avoid the repetition.

If someone's response to a repetitive task is copy-pasting poorly-written code over and over we call them a bad engineer. If they use an AI to do the copy-paste for them that's supposed to be better somehow?

[–] pennomi@lemmy.world 11 points 18 hours ago (2 children)

Some code is boilerplate and can’t be distilled down more. It’s nice to point an AI to a database schema and say “write the Django models, admin, forms, and api for this schema, using these authentication permissions”. Yeah I’ll have to verify it’s done right, but that gets a lot of the boring typing out of the way.

[–] panda_abyss@lemmy.ca 2 points 4 hours ago

I use it for writing code to call APIs and is a huge boon.

Yeah, you have to check the results, but it’s way faster than me.

[–] Sibshops@lemmy.myserv.one 4 points 18 hours ago
[–] Flamekebab@piefed.social 6 points 16 hours ago

Similarly I find it very useful for if I've written a tool script and really don't want to write the command line interface for it.

"Here's a well-documented function - write an argparser for it"

...then I fix its rubbish assumptions and mistakes. It's probably not drastically quicker but it doesn't require as much effort from me, meaning I can go harder on the actual function (rather than keeping some effort in reserve to get over the final hump).

[–] otacon239@lemmy.world 4 points 19 hours ago

I’ve had plenty of success using it to build things like docker compose yamls and the like, but for anything functional, it does often take a few tries to get it right. I never use its raw for anything in production. Only as a leaping off point to structure things.

[–] Valmond@lemmy.world 2 points 17 hours ago

For the missing 10% : the folder with copies of the code you have already wrote doing that.

[–] MangoCats@feddit.it 1 points 18 hours ago (1 children)

(asking GPT-5 to do your dynamic SQL calls is inviting disaster, for example. Requires hours of reworking just to get close.)

Maybe it's the dynamic SQL calls themselves that are inviting disaster?

[–] Warl0k3@lemmy.world 2 points 17 hours ago* (last edited 17 hours ago) (1 children)

Dynamic SQL in of itself not an issue, but the consequences (exacerbated by SQL's inherent irrecoverability from mistakes - hope you have backups) have stigmatized its use heavily. With an understanding of good practice, a proper development environment and a close eye on the junior devs, there's no inherent issue to using it.

[–] MangoCats@feddit.it 3 points 16 hours ago

With an understanding of good practice, a proper development environment and a close eye on the junior devs, there’s no inherent issue to using it.

My feelings about C/C++ are the same. I'm still switching to Rust, because that's what the company wants.