this post was submitted on 15 Sep 2025
135 points (82.6% liked)

Technology

75162 readers
1580 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
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
L4s@hackingne.ws
135
Vibe coding has turned senior devs into ‘AI babysitters,’ but they say it’s worth it | TechCrunch (techcrunch.com)
submitted 22 hours ago by kinther@lemmy.world to c/technology@lemmy.world
70 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] wulrus@lemmy.world 3 points 4 hours ago (1 children)

I find it also saves a certain "mental energy".

E. g. when I worked on a program to recover data from the old discontinued Windows photo app: I started 2 years ago and quickly had a proof-of-concept: Found out it's just sqlite format, checked out the table structure, made a query to list the files from one album. So at that point, it was clear that it was doable, but the remaining 90 % would be boring.

So after 2 years on pause, I just gave Gemini 2.5Pro the general problem and the two queries I had. It 1-shot a working powershell script, no changes required. It reads directly from the sqlite (imagine the annoyance to research that when you never ever use powershell!) and put the files to folders named by the former albums. My solution would have been worse, would probably have gone with just hacking together some copy-commands from SELECT and run them all once.

That was pretty nice: I got to do the interesting part of building the SQL queries, and it did the boring, tiring things for me.

Overall, I remain sceptical as you do. There is definitely a massive bullshit-bubble, and it's not clear yet where it ends. I keep it out of production code for now, but will keep experimenting on the side with an "it's just code completion" approach, which I think might be viable.

[–] squaresinger@lemmy.world 2 points 3 hours ago

Yours is pretty much the best-case scenario for AI:

  • Super small project, maybe a few dozen lines at most
  • Greenfield: no dependencies, no old code, nothing to consider apart from the problem at hand
  • Disposable: once the job is done you discard it and won't need to maintain it
  • Someone most likely already did the same thing or did something very similar and the LLM can draw on that, modify it slightly and serve it as innovation
  • It's a subject where you are good enough that you can verify what the LLM spits out, but where you'd have to spend hours and hours to read into how to do it

For that kind of stuff it's totally OK to use an LLM. It's like googleing, finding a ready-made solution on Stackexchange, running that once and discarding it, just in a more modern wrapping. I've done something similar too.

But for real work on real projects, LLM is more often than not a time waster and not a productivity gain.