Live data from Hacker News

Claude Code Unpacked : A visual guide

ccunpacked.dev

421–430 of 464 posts

Re: Claude Code Unpacked : A visual guide

#421
post #321

Earlier quoted context omitted.

Of course I expect it is vibe coding. It would be insane to code anything by hand these days. But that doesn't mean there is no creative input by the author here.

>> It would be insane to code anything by hand these days. I strongly disagree, but it made me chuckle a bit, thinking about labeling software as "handmade" or marketing software house as "artisanal".

There's a lot of errors you can miss by coding by hand, even as a seasoned developer. Try taking Claude Code, point it at your repo, and ask it to find bugs. I bet it will.

Claude is actually a crazy good vuln researcher. If you use it that way, your code might just be more secure than written purely by hand.

Re: Claude Code Unpacked : A visual guide

#422
I have no engineering background. I build websites and tools for a living. Claude Code changed what's possible for me in a way that's hard to overstate.

I can't evaluate the source code architecture. What I can say is that before this, I had ideas I couldn't execute without hiring a developer. Now I ship them myself. Not prototypes, not demos. Real products that people use and pay for.

The leaked internals are interesting to engineers. From where I sit, the interesting part is that it works well enough that someone without a CS degree can build production software with it. That's the actual story.

Re: Claude Code Unpacked : A visual guide

#423

I have no engineering background. I build websites and tools for a living. Claude Code changed what's possible for me in a way that's hard to overstate. I can't evaluate the source code architecture. What I can say is that before this, I had ideas I couldn't execute without hiring a developer. Now I ship them myself. Not prototypes, not demos. Real products that people use and pay for. The leaked internals are intere…

I don't think CS degree was needed pre-LLM era, you just needed to know what you're doing. Maybe learning and doing got faster, but you still need to learn and know. There are CS grads that don't know still. I hope you know what is required for "production software". Claude code doesn't.

Re: Claude Code Unpacked : A visual guide

#425
post #349
post #319

Earlier quoted context omitted.

It's weird to look at the world like this. If they deliver doesn't that invalidate thousands of other business plans? What about paying for that? If they fail, doesn't software and the giant companies that make it go back to owning the world?

“if they deliver” As I’m reading this, I’m thinking about how in 1980. It was imagined that everyone needed to learn how to program in BASIC or COBOL, and that the way computers would become ubiquitous would be that everybody would be writing program programs for them. That turned out to be a quaint and optimistic idea. It seems like the pitch today is that every company that has a software-like need will be able to…

> breaking capitalism

It seems non sequitur. This hypothetical scenario sounds like entrenching capitalism, because it would concentrate capital even more.

It would probably weaken democracy and weaken free market (esp. the job market), yes.

> society will collapse before then because of said breaking of capitalism itself

Or, maybe the society would continue to exist with even more inequality? And, of course, much changed from what it is today.

Re: Claude Code Unpacked : A visual guide

#426

Earlier quoted context omitted.

> Claude Code is an interface to using AI to do any computer task Shouldn't interfaces be smaller than the implementation?

No. We aren't talking about .h vs .c files nor PL interfaces. A GUI/client can be arbitrarily more or less complex than the things it's GUI'ing.

> A GUI/client can be arbitrarily more or less complex than the things it's GUI'ing.

If it's an interface to ffmpeg, then sure, the GUI could be extremely complicated code.

But that's not what we are talking about, is it? We are talking about an interface to a chatbot that can accept and return chats, accept and return files, and run a selection of internal commands (which include invoking itself recursively).

The interface to this chatbot that has a settings entry for "personality" is still only going to map that to one of a small number of chatbot inputs. Same with basically anything else (read the skills file, etc).

I dunno... maybe 500kSloC for a fancy IRC client is the going rate, but the last time I wrote an interface to a chat client, it was barely 10k lines, not counting the lib*.so that the the program called to interact with the chatbot, with said chatbot supporting file uploads and '/' commands.

Re: Claude Code Unpacked : A visual guide

#427

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. 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;…

[flagged]

Re: Claude Code Unpacked : A visual guide

#429

Author here. I built this in a few hours after the Claude Code leak. I've been working on my own coding agent setup for a while. I mostly use pi [0] because it's minimal and easy to extend. When the leak happened, I wanted to study how Anthropic structured things: the tool system, how the agent loop flows, A 500K line codebase is a lot to navigate, so I mapped it visually to give myself a quick reference I could come…

Hi, Autocracy. I took your site and built Clyde: https://github.com/dev-divi/choice-agent-clyde
Post reply on HN