6 ms·
Alternatively, the elephant in the room I'm surprised no one wants to talk about: the vibe coding is catching up with them.
by 827a 6mo ago
Alternatively, the elephant in the room I'm surprised no one wants to talk about: the vibe coding is catching up with them.
- muyuu 6mo agothat is a separate issue indeed, but their comms make it rather obvious they are scrambling to reduce compute and they're just slashing their service selectively - with openclaw and max users being the first in the chopping block
- eatsyourtacos 6mo agoThat's not an elephant in the room.. it's just proof of how insanely useful the tool is and the reality that so much more hardware is needed. Thus people saying "why are these companies building insanely large data centers" ... this is why!
- SpicyLemonZest 6mo agoI have no particular insight into the Anthropic backend, but it's possible in general for systems to have architectural issues which cannot be mitigated by just adding more hardware.
- skeeter2020 6mo agomaybe you should study up on correlation and causation before you declare "proof"; it's also possible that it goes the other way.
- eatsyourtacos 6mo agoThe proof is already there. It's concrete. I've seen it directly the last few months of using claude code. It closed the loop. It's insanely beneficial when used properly- that is a pure fact. You act like it's an opinion.
- georgeecollins 6mo agoI think it is telling that this audience down votes this. It's kind of obvious that the thing is being used a lot. Doesn't mean it works as well as advertised. Doesn't mean the business model they have works. Just means there is a lot of demand. You can't ignore that.
- kartoffelsaft 6mo agoThe problem is that vibe-coding, when it fails (i.e. it's non-useful, at least for a bit), is usually solved by more vibes. Try again and hope it works. Ask it to refactor and hope the cleaner code helps it along. If you're willing to think about the code yourself you'll likely ask it questions about the codebase. High vibe-code usage is both a metric that it is working and that it's failing.
- otikik 6mo agoThat is only true if there's a pricepoint that vibecoders are willing to pay per token that allows Anthropic to make a profit.
- xmprt 6mo agoI don't think anyone is talking about it because it's not a very productive conversation to have. I'm not particularly bullish on vibe coding either but if you could explain what exactly about vibe coding causes these specific issues then it could be more interesting to discuss. But as it stands, the more likely reason is capacity crunch caused by a chips shortage and demand heavily outpacing supply. You vibe coding reason is based on as much vibes as their code probably is.
- leptons 6mo agoVibe coding does not usually produce performant code, it produces spaghetti with the goal of making the user asking for work to be done to go away as soon as possible with a (often barely) working solution. I recently vibe-translated a simple project from Javascript to C, where Javascript was producing 30fps, and the first C version produced 1 frame every 20 seconds. After some time trying to get the AI to optimize it, I arrived at 1fps from the C project. Not a win, but the AI did produce working C code. I have no doubt that if I had done this myself (which I will do soon), with the appropriate level of care, it would have been 30fps or more.
- throwaway27448 6mo agoIt should catch up faster. It's absolutely useless for the bulk of the tedium—notably, soldering together random repos to satisfy executives—that makes up my job now.
- stemlord 6mo agoThat's mostly been my job since I started around 2010 haha
- sutib 6mo agoIf an AI doesnt generate perfect code, if left to its devices it will at some point create a codebase big and nasty enough that it will not be able to deal with it.