this post was submitted on 07 Dec 2025
1078 points (98.1% liked)

Technology

77084 readers
3347 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
1078
I Went All-In on AI. The MIT Study Is Right. (open.substack.com)
submitted 4 days ago* (last edited 4 days ago) by AutistoMephisto@lemmy.world to c/technology@lemmy.world
299 comments fedilink hide all child comments
 

Just want to clarify, this is not my Substack, I'm just sharing this because I found it insightful.

The author describes himself as a "fractional CTO"(no clue what that means, don't ask me) and advisor. His clients asked him how they could leverage AI. He decided to experience it for himself. From the author(emphasis mine):

I forced myself to use Claude Code exclusively to build a product. Three months. Not a single line of code written by me. I wanted to experience what my clients were considering—100% AI adoption. I needed to know firsthand why that 95% failure rate exists.

I got the product launched. It worked. I was proud of what I’d created. Then came the moment that validated every concern in that MIT study: I needed to make a small change and realized I wasn’t confident I could do it. My own product, built under my direction, and I’d lost confidence in my ability to modify it.

Now when clients ask me about AI adoption, I can tell them exactly what 100% looks like: it looks like failure. Not immediate failure—that’s the trap. Initial metrics look great. You ship faster. You feel productive. Then three months later, you realize nobody actually understands what you’ve built.

you are viewing a single comment's thread
view the rest of the comments
[–] vpol@feddit.uk 60 points 4 days ago (5 children)

The developers can’t debug code they didn’t write.

This is a bit of a stretch.

[–] Xyphius@lemmy.ca 47 points 4 days ago

agreed. 50% of my job is debugging code I didn't write.

[–] funkless_eck@sh.itjust.works 19 points 4 days ago (2 children)

I mean I was trying to solve a problem t'other day (hobbyist) - it told me to create a

function foo(bar): await object.foo(bar)

then in object

function foo(bar): _foo(bar)

function _foo(bar): original_object.foo(bar)

like literally passing a variable between three wrapper functions in two objects that did nothing except pass the variable back to the original function in an infinite loop

add some layers and complexity and it'd be very easy to get lost

[–] theparadox@lemmy.world 14 points 3 days ago

The few times I've used LLMs for coding help, usually because I'm curious if they've gotten better, they let me down. Last time it was insistent that its solution would work as expected. When I gave it an example that wouldn't work, it even broke down each step of the function giving me the value of its variables at each step to demonstrate that it worked... but at the step where it had fucked up, it swapped the value in the variable to one that would make the final answer correct. It made me wonder how much water and energy it cost me to be gaslit into a bad solution.

How do people vibe code with this shit?

[–] vpol@feddit.uk 1 points 3 days ago

As a learning process it’s absolutely fine.

You make a mess, you suffer, you debug, you learn.

But you don’t call yourself a developer (at least I hope) on your CV.

[–] _g_be@lemmy.world 15 points 3 days ago (2 children)

Vibe coders can't debug code because they didn't write

[–] embed_me@programming.dev 7 points 3 days ago (1 children)

Vibe coders can't debug code because they can't write code

[–] _g_be@lemmy.world 2 points 3 days ago

Yes, this is what I intended to write but I submitted it hastily.

Its like a catch-22, they can't write code so they vibecode, but to maintain vibed code you would necessarily need to write code to understand what's actually happening

[–] Evotech@lemmy.world 2 points 3 days ago (1 children)

I don't get this argument. Isn't the whole point that the ai will debug and implement small changes too?

[–] yuki2501@lemmy.world 3 points 3 days ago (1 children)

Think an interior designer having to reengineer the columns and load bearing walls of a masonry construction.

What are the proportions of cement and gravel for the mortar? What type of bricks to use? Do they comply with the PSI requirements? What caliber should the rebars be? What considerations for the pouring of concrete? Where to put the columns? What thickness? Will the building fall?

"I don't know that shit, I only design the color and texture of the walls!"

And that, my friends, is why vibe coding fails.

And it's even worse: Because there are things you can more or less guess and research. The really bad part is the things you should know about but don't even know they are a thing!

Unknown unknowns: Thread synchronization, ACID transactions, resiliency patterns. That's the REALLY SCARY part. Write code? Okay, sure, let's give the AI a chance. Write stable, resilient code with fault tolerance, and EASY TO MAINTAIN? Nope. You're fucked. Now the engineers are gone and the newbies are in charge of fixing bad code built by an alien intelligence that didn't do its own homework and it's easier to rewrite everything from scratch.

[–] Evotech@lemmy.world 0 points 3 days ago

If you need to refractor your program you might aswell start from the beginning

[–] anon_8675309@lemmy.world 14 points 4 days ago (1 children)

Some can't because they never acquired to skill to read code. But most did and can.

[–] Rooster326@programming.dev 2 points 3 days ago

If you've never had to debug code. Are you really a developer?

There is zero chance you have never written a big so... Who is fixing them?

Unless you just leave them because you work for Infosys or worse but then I ask again - are you really a developer?

[–] mal3oon@lemmy.world 1 points 3 days ago

I think it highly depends on the skill and experience of the dev. A lot of the people flocking into the vibe coding hype are not necessarily always people who know how about coding practices (including code review etc ..) nor are experienced in directing AI agent to achieve such goals. The result is MIT prediction. Although, this will start to change soon.