[dead]
Claude Code Unpacked : A visual guide
281–290 of 464 posts
Re: Claude Code Unpacked : A visual guide
#282Earlier quoted context omitted.
>A 500k line codebase for an agent CLI proves one thing: making a probabilistic LLM behave deterministically is a massive state-management nightmare. Right now, they're great for prompting simple sites/platforms but they break at large enterprise repos. Is that the case? I'm pretty sure Claude Code is one of the most massively successful pieces of software made in the last decade. I don't know how that proves your po…
Claude code is a massively successful generator, I use it all the time, but it's not a governance layer. The fact that the industry is copying a 500k-line harness is the problem. We're automating security vulnerabilities at scale because people are trying to put the guardrails inside the probabilistic code instead of strictly above it. Standardizing on half a million lines of defensive spaghetti is a huge liability.
>Standardizing on half a million lines of defensive spaghetti is a huge liability.
Again, maybe it will be. Or maybe the way we make software and what is considered good practice will completely change with this new technology. I'm betting on the latter at this point.
Re: Claude Code Unpacked : A visual guide
#283Earlier quoted context omitted.
[flagged]
If writing concise architectural analysis without the fluff makes me an AI, I'll take the complement. But no - just a tired Architect who has spent way too many hours staring at broken agent state loops haha.
I'll bet you $20 you ran your original comment through an LLM. Likely an OpenAI model.
Re: Claude Code Unpacked : A visual guide
#284Earlier quoted context omitted.
All of them are really, REALLY bad.
Bad by whose definition? They work really well in my experience. They aren't perfect but the amount of hand holding has gone down dramatically and you can fix any glaring problems with a code review at the end. I work on a multimillion line code base which does not use any popular frameworks and it does a great job. I may be benefiting from the fact that the codebase is open source and all models have obviously been…
It takes 10 seconds for Gemini CLI to load. 10 seconds to show an input field. This is for a CLI program.
For comparison, it takes me less time to load Chrome and go to gemini.google.com.
Re: Claude Code Unpacked : A visual guide
#285A 500k line codebase for an agent CLI proves one thing: making a probabilistic LLM behave deterministically is a massive state-management nightmare. Right now, they're great for prompting simple sites/platforms but they break at large enterprise repos. If you don't have a rigid, external state machine governing the workflow, you have to brute-force reliability. That codebase bloat is likely 90% defensive programming;…
I find it really strange that there is so much negative commentary on the _code_, but so little commentary on the core architecture. My takeaway from looking at the tool list is that they got the fundamental architecture right - try to create a very simple and general set of tools on the client-side (e.g. read file, output rich text, etc) so that the server can innovate rapidly without revving the client (and also so…
[dead]
Re: Claude Code Unpacked : A visual guide
#286Anthropic is now more open than OpenAI Itself lmao!
Re: Claude Code Unpacked : A visual guide
#287Earlier quoted context omitted.
> A 500k line codebase for an agent CLI proves one thing: making a probabilistic LLM behave deterministically is a massive state-management nightmare. Considering what the entire system ends up being capable of, 500k lines is about 0.001% of what I would have expected something like that to require 10 years ago. You can combine that with all the training and inference code, and at the end of the day, a system that li…
> You can combine that with all the training and inference code, and at the end of the day, a system that literally writes code ends up being smaller than the LibreOffice codebase. You really need to compare it to the model weights though. That’s the “code”.
>You really need to compare it to the model weights though
Then you'd need to compare the education of any developer in relation to how many LOC their IDE is. That's the "code".
So yea, the analogy doesn't make a whole lot of sense.
Re: Claude Code Unpacked : A visual guide
#288Re: Claude Code Unpacked : A visual guide
#289A 500k line codebase for an agent CLI proves one thing: making a probabilistic LLM behave deterministically is a massive state-management nightmare. Right now, they're great for prompting simple sites/platforms but they break at large enterprise repos. If you don't have a rigid, external state machine governing the workflow, you have to brute-force reliability. That codebase bloat is likely 90% defensive programming;…
brute-forcing pattern-matching at scale. These are brittle systems with enormous duct-taping to hold everything together. workarounds on workarounds.
Re: Claude Code Unpacked : A visual guide
#290Earlier quoted context omitted.
Comments like these remind me of the football spectators that shout "Even I could have scored that one" when they see a failed attempt. Sure. You could have. But you're not the one playing football in the Champions League. There were many roads that could have gotten you to the Champions League. But now you're in no position to judge the people who got there in the end and how they did it. Or you can, but whatever.
> Sure. You could have. But you're not the one playing football in the Champions League. The only reason people are using Claude Code is because it's the only way to use their (heavily subsidized) subscription plans. People who are okay with using and paying for their APIs often opt out for other, better, tools. Also, analogies don't work. As we know for a fact that Claude Code is a bloated mess that these "champions…
"Even I would have scored that goal"
==
"I would never ever have created a bloated mess like Anthropic"
You just repeat the same statement.
That bloated mess is what got them to the Champions League. They did what was necessary to get them here. And they succeeded so far.
But hey, according to some it can be replicated in 50k lines of wrapper code around a terminal command, so for Anthropic it's just one afternoon of vibe coding to get rid of this mess. So what's the problem? /s