this post was submitted on 27 Jun 2026
416 points (98.1% liked)

Technology

85805 readers
3628 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 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] AA5B@lemmy.world 1 points 18 hours ago* (last edited 18 hours ago)

I was just planning to do some sort of write up on this topic, although it will be internal only.

Of the three projects I’m currently on

  • existing code base where AI sometimes has good ideas but almost never able to implement them successfully. This is legacy code, all human generated, and is probably too tightly coupled. Test framework is tightly coupled to the environment so ai cannot run it
  • new tool implementation to give cheaper and faster context across all repos (Spotify Backstage)
  • new code base almost entirely ai generated. Much more loosely coupled. There is no test /mock framework available, so it’s all scripts, which the ai is able to run at will to refine its guesses

There’s definitely distinct conditions where ai can be the right tool and can succeed vs when it can’t. In managements blind rush to vibe code everything, they need to better understand where it works and where it doesn’t

In particular, functionality I’m working on this week

  • existing code base ”modify function x to cover scenario y” at best gives a useful strategy
  • new code base “implement function x similar to existing code base, but that also covers scenario y” seems to work