3 ms·

The problem is not that the experts have dismissed vibe coding without even trying it. The problem is that the experts have tried it and found that vibe coding

The problem is not that the experts have dismissed vibe coding without even trying it. The problem is that the experts have tried it and found that vibe coding doesn't actually work at scale that they need. Will it ever? Perhaps, but I'd argue a near-AGI level of intelligence would need to be achieved first. When that happens, we have bigger problems (and/or opportunities?) than a few programmers losing their jobs.

edg5000 1y ago
From your comment I understand you tried and didn't like it? Why not?
adastra22 1y ago
You’re mistaking current capabilities for potential future extensions. The the exact thing the comment you are replying to is talking about.
singularity2001 1y ago
No way you tried Claude Code in the right set up and came to this completely outdated conclusion
- swat535 1y ago
  Yes you can get surpsingly far with Claude if you’re persistent enough and don’t care about bugs, security issues or code quality. Eventually it will spit out something that works. Sometimes it gets very stuck and you have to delete everything it did and start again.
theshrike79 1y ago
"at scale" is the issue here. Yes, you can't vibe code a full-ass enterprise level product fit to sell as SaaS for a Fortune 500 company. But what you can vibe code is a bunch of small _bespoke_ tools that fit your exact use-case. Stuff you could buy (or rent) as SaaS, but they'd have 80% too many features and a constant monthly cost. Just last week I converted a bunch of docker compose -based containers to run on Opentofu, took me maybe an hour or two with Claude Code while watching TV. Would've been a week easy if I went for the artisanal route of reading Terraform documentation and digging through forums and Stack Overflow. Not a world-changing thing, I could've lived with the compose setup, but now the whole system is declarative. I set the state and the state is applied, no drift.

edg5000 1y ago

From your comment I understand you tried and didn't like it? Why not?

adastra22 1y ago

You’re mistaking current capabilities for potential future extensions. The the exact thing the comment you are replying to is talking about.

singularity2001 1y ago

No way you tried Claude Code in the right set up and came to this completely outdated conclusion

swat535 1y ago
Yes you can get surpsingly far with Claude if you’re persistent enough and don’t care about bugs, security issues or code quality. Eventually it will spit out something that works. Sometimes it gets very stuck and you have to delete everything it did and start again.

theshrike79 1y ago

"at scale" is the issue here. Yes, you can't vibe code a full-ass enterprise level product fit to sell as SaaS for a Fortune 500 company. But what you can vibe code is a bunch of small _bespoke_ tools that fit your exact use-case. Stuff you could buy (or rent) as SaaS, but they'd have 80% too many features and a constant monthly cost. Just last week I converted a bunch of docker compose -based containers to run on Opentofu, took me maybe an hour or two with Claude Code while watching TV. Would've been a week easy if I went for the artisanal route of reading Terraform documentation and digging through forums and Stack Overflow. Not a world-changing thing, I could've lived with the compose setup, but now the whole system is declarative. I set the state and the state is applied, no drift.