this post was submitted on 14 May 2026
462 points (96.2% liked)

Technology

84733 readers
3288 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
462
Software Engineers Say They're Losing the Ability to Code Now That AI Does It for Them (futurism.com)
submitted 3 days ago by throws_lemy@reddthat.com to c/technology@lemmy.world
154 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[โ€“] shoo@lemmy.world 19 points 2 days ago (6 children)

Things I've realized while working with AI (Claude code):

  • It's fantastic for very small macros and medium length scripts. Think dev ops stuff, pre-commit hooks, transforming data. Keep it small enough to manually review and something you can run without destroying anything important. This can massively boost your codebase QoL. [Double bonus for not wasting tokens to solve the same problem over and over]
  • It's decent-to-good at debugging but not consistent with fixes. It can find some utf encoding edge case that might have taken you 1hr+ but suggest the dumbest bandaid fix you've ever seen. Also very good at spinning up unit test suites for basic edge cases.
  • Due to obvious training bias, it's pretty good with common libraries and cloud platform infrastructure. It could probably help with writing a complex cron call, debugging regex or fixing an IaC config. On the flip side it won't bother to use the latest package version or know your niche/new library.
  • It does better with greenfield because exploring your codebase introduces a ton of bias. It might try to fit in an ugly hack when a refactor to simplify everything is way easier.
  • It's absolutely garbage with UI, just throws the most disorganized HTML together that isn't reactive or reusable. OK enough for ugly internal stuff but God help anyone relying on it for that.
  • This is setting up to be the biggest rug pull in history. People that buy into it heavily just to save a couple bucks on engineer payroll are going to be fucked when they start ratcheting up the token price.

All in all it can be useful when used with care but will never be a magic bullet.

[โ€“] Archr@lemmy.world 2 points 2 days ago

This is basically what I discovered as well. I have found that Ai writes code that is complex and "works" (at least most of the time) but it is heavily over engineered and often contains design choices that make expanding functionality effectively impossible without a full refactor.

When I tried having the Ai fix a test failure the Ai would either fix the code, fix the test, or change the test and the code breaking everything else in the chain.

I no longer use vibe coding because it is just faster/better for me to write the code.

But for tiny scripts it is very good.

load more comments (5 replies)