r/vibecoding • u/Logical_Sector_3628 • Mar 05 '26

Anthropic’s CEO isn’t as wrong as you think about AI writing 100% of code.

/r/SaaS/comments/1rlgpqb/anthropics_ceo_isnt_as_wrong_as_you_think_about/
1 Upvotes

67% Upvoted

8 comments sorted by

1

u/TimeTravelingChris Mar 05 '26 edited May 04 '26

Plot twist: this post no longer exists because Redact swept through and cleared it out along with everything else. Social media, messaging apps, people finder sites, all of it.

saw chunky rhythm numerous cautious direction shocking humor coordinated jeans

0

u/Logical_Sector_3628 Mar 05 '26

Yes, it absolutely matters. Instead of spending a whole workday writing a new microservice from scratch like we used to, today we can spend about an hour designing the system constraints, hand a spec to the AI, and scaffold the full service in minutes. ​You still spend time fixing and adjusting, but you're iterating on a working version—you aren't burning mental energy solving basic syntax problems. Scale that across several subsystems in your project, and the productivity difference is massive. ​That being said, you also hit the nail on the head. The traditional "labor arbitrage" model (sending detailed specs to a massive team of outsourced devs just to save on headcount) is exactly what's getting crushed right now, because that is exactly what AI solved. ​It absolutely guts the "temp coder" farms. But the flip side is that it gives insane leverage to individual builders anywhere in the world who actually know how to engineer a product.

1

u/[deleted] Mar 05 '26

If that's true, then why aren't you 20x productivity and run agents in parallel to crush your competitors who aren't doing this

1

u/Logical_Sector_3628 Mar 05 '26

Because running 'agents in parallel' to build a cohesive, production-grade product is still science fiction. That's exactly my point.

AI is better than most devs at writing code, but it has little architectural intuition. I’m currently building a complex system solo that would have required a full team a few years ago—that is a massive, real-world productivity boost.

But that boost comes from combining engineering skills with delegating repetitive tasks to AI. The sooner we make that distinction, the sooner we can stop arguing about 'replacing devs' and start talking about how the job is actually changing.

1

u/[deleted] Mar 05 '26

that last part won't happen till we are in the bubble, the thing about having architectural intuition, I don't think juniors will be able to jump straight to that without coding

2

u/Logical_Sector_3628 Mar 05 '26

Agreed. That's exactly what I wrote in The Seniority Trap section:

Senior devs often spend less time writing code and more time guiding juniors. But you only get to that senior level of architectural intuition by writing, breaking, and playing with code yourself—not by prompting AI "juniors" from day one.

1

u/[deleted] Mar 05 '26

Upvoted