this post was submitted on 30 Sep 2025
1106 points (98.8% liked)

Technology

77090 readers
4096 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.

(page 5) 16 comments
sorted by: hot top controversial new old
[–] ready_for_qa@programming.dev -1 points 2 months ago (3 children)

These types of articles always fail to mention how well trained the developers were on techniques and tools. In my experience that makes a big difference.

My employer mandates we use AI and provides us with any model, IDE, service we ask for. But where it falls short is providing training or direction on ways to use it. Most developers seem to go for results prompting and get a terrible experience.

I on the other hand provide a lot of context through documents and various mcp tooling, I talk about the existing patterns in the codebase and provide sources to other repositories as examples, then we come up with an implementation plan and execute on it with a task log to stay on track. I spend very little time fixing bad code because I spent the setup time nailing down context.

So if a developer is just prompting "Do XYZ". It's no wonder they're spending more time untangling a random mess.

Another aspect is that everyone seems to always be working under the gun and they just don't have the time to figure out all the best practices and techniques on their own.

I think this should be considered when we hear things like this.

load more comments (3 replies)
[–] NuXCOM_90Percent@lemmy.zip -3 points 2 months ago (2 children)

LLMs/"Vibe Coding" is probably a little bit more useful than the average intern with some tasks bumping up to an early career hire (what would historically be a Junior Engineer before title inflation/stagnation).

As in: it can generate code that might do what you want. But you need (actual) senior engineers to review the code thoroughly. And... how do people get the experience they need to do that?

Which basically results in turning everyone into a manager. Except your reports aren't humans and you don't get more pay. Instead your reports are vscode plugins. Which... sounds like absolute hell but I can get why the (wannabe) management class loves that.

load more comments (2 replies)
[–] jaykrown@lemmy.world -5 points 2 months ago (2 children)

I've found success using more powerful LLMs to help me create applications using the Rust programming language. If you use a weak LLM and ask it to do something very difficult you'll get bad results. You still need to have a fundamental understanding of good coding practices. Using an LLM to code doesn't replace the decision making.

load more comments (2 replies)
load more comments
view more: ‹ prev next ›