[sandeepkd]

My assumption is that a lot of these checks and changes lately are not well though out. They are knee jerk reaction to address something which was not anticipated in the original design. A lot of these changes to address scaling and abuse challenges probably fall into bucket of applying bandages on top of bandages. Maybe if Claude could build something to validate the baseline quality of the product to ensure these things are discovered early on.

[captn3m0]

Worse than that, these are all vibe coded changes. If you look at any public Anthropocene codebase, they are all vibe coded messes with no coherent vision. I was looking at the Claude Code GitHub Action and it is a mess of options that don’t exist together, unclear documentation, and usage story being terribly unclear.

[raincole]

People say that a mostly-vibed project will collapse under its own weight. I personally doubt it, but I will be amused if the first big one falls this way is Claude Code itself.

[somat]

Unfortunately it will all probably sort of work, But best not to dwell too much on how the sausage is made, it is pretty unpleasant. There will be some interesting job titles in the future however.

I just read Vernor Vinge's "A deepness in the sky" And the way he modeled their compute systems felt depressingly believable, they have thousand of years of libraries floating around, sort of loosely tacked together. and specialist programmer-archaeologists are the ones who who dig deep and try to understand the system.

[weiliddat]

> Unfortunately it will all probably sort of work, But best not to dwell too much on how the sausage is made, it is pretty unpleasant.

Interestingly, most long-running codebases are like that, no?

It's just that producing (incl. reviewing/testing and all those, even AI-assisted) that amount of code in a significantly shorter period of time highlights this discrepancy much more to us.

Boiling frog

[imtringued]

Considering that Claude Code stalls out on the installation process for me to the point where I never had a chance to use it, we're already there.

[notarobot123]

I've seen ancient codebases that you need to be blessed by a priest to even touch but they keep chugging away and having new features added. I wouldn't hold my breath for a collapse, just a quagmire that we continually have to wade through to get anything done.

[jacamera]

Isn't it also true that the deeper and thicker the quagmire, the more tokens one will have to use to wade through it?

This seems like a path to eventual LLM lock-in once the codebase gets messy enough. These things could end up being like 0% interest credit cards for technical debt. I guess it all depends on how the token usage scales over time. My guess is it will be steeper than linear.

[wraptile]

What continues to perplex me is that these people claim that they will be able to contain AGI yet can't roll out a regex match? If AGI is possible then we're most certainly not containing anything.

[dr_kiszonka]

Don't worry. AGI will be vibe-coded too.

[y1n0]

Just give it a little time. AGI will be redefined to whatever is current and a new AI acronym will be coined for what everyone expected true AI to be in the first place.

Artificial Human Intelligence. Actually they'll probably drop the Artificial part. Human Scale Intelligence.

[imtringued]

AGI is a specific brand of Arm processors.

The meaning behind the acronym is so wrong that I already forgot what it stands for. This is aggravated by the fact that every single marketing page of this Arm brand refuses to mention what the acronym stands for.

Thanks to being at the forefront of AGI, Arm has had a spark of genius. The G in AGI stands for AI.

Of course the A is obviously Agentic and the I is Infrastructure.

[ex-aws-dude]

Why does it seems like they do everything so hacky

[SpicyLemonZest]

Given what we know about their development practices, they almost certainly implemented this check by writing text along the lines of “Please ensure requests from Openclaw always go to extra usage” into a Claude prompt. Perhaps some junior engineer who didn’t understand the problem reviewed the generated code, or perhaps nobody at all reviewed it.

[sumeno]

They're the poster child for what eventually happens when you just vibe code everything

[vkou]

Of course they are not well thought out. The biggest limiting factor on software quality has always been PM and executive prioritization. If they decide that you should build garbage anti-user features, that's what you'll build for them.

Letting SWEs execute on that prioritization faster was never going to get us better software, it was just going us more enshittification faster.

AI improving productivity is great, except that the C-suite controlling where that productivity goes are people that are consistently ranking in the top of the 'Never should be trusted with a lot of power' list. All they want is to make more paperclips.