[mattmanser]

It's just not true, it is not ready.

Especially Claude, where if you check the forums everyone is complaining that it's gone stupid the last few months.

Claude's code is all over the place, and if you can't see that and are putting it's code into production I pity your colleagues.

Try stopping. Honestly, just try. Just use claude as a super search engine. Though right now ChatGPT is better.

You won't see any drop in productivity.

[bratbag]

It's not about blindly accepting autogenerated code. Its using them for tooling integration.

Its like terminal autocomplete on steroids. Everything around the code is blazing fast.

[IshKebab]

This is far too simplistic a viewpoint. First of all it depends what you're trying to do. Web dev? AI works pretty well. CPU design? Yeah good luck with that.

Secondly it depends what you're using it for within web dev. One shot an entire app? I did that recently for a Chrome extension and while it got many things wrong that I had to learn and fix, it was still waaaaaay faster than doing it myself. Especially for solving stupid JS ecosystem bugs.

Nobody sane is suggesting you just generate code and put it straight into production. It isn't ready for that. It is ready for saving you a ton of time if you use it wisely.

[mattmanser]

I'd say it was pretty naunced. Use it, but don't vibe code. The crux of the issue is that unless you're still writing the code it's too hard to notice when Claude or Codex makes a mountain out of a mole hill, too easy to miss the subtle bugs, too easy to miss the easy abstractions which would have vastly simplified the code.

And I do web dev, the code is rubbish. It's actually got subtle problems, even though it fails less. It often munges together loads of old APIs or deprecated ways of doing things. God forbid you need to deal with something like react router or MUI as it will combine code from several different versions.

And yes, people are using these tools to directly put code in. I see devs DOING it. The code sucks.

Vibe coded PRs are a huge timesink that OTHER people end up fixing.

One guy let it run and it changed code in an entirely unrelated part of the system and he didn't even notice. Worse, when scanning the PR it looked reasonable, until I went to fix a 350 line service Claude or codex had puked out that could be rewritten in 20 lines, and realized the code files were in an entirely different search system.

They're also generally both terrible at abstracting code. So you end up with tons of code that does sweet FA over and over. And the constant over engineering and exception handling theatre it does makes it look like it's written a lot of code when it's basically turned what should be a 5 liner into an essay.

Ugh. This is like coding in the FactoryFactoryFactory days all over again.