Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Claude Code Unpacked : A visual guide

ccunpacked.dev

Post reply on HN
Print view View original

401–410 of 464 posts

Re: Claude Code Unpacked : A visual guide

#401

Post by ericfr11 »

pred_ wrote: post #345
amangsingh wrote: post #148

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

The time is ripe for deterministic AI; incidentally, this was also released today: https://itsid.cloud/ - presumably will be useful for anyone who wants to quickly recreate an open source Python package or other copyrighted work to change its license.

April's fool. Check the career page

Re: Claude Code Unpacked : A visual guide

#402

Post by gbibas »

amangsingh wrote: post #148

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

[dead]

Re: Claude Code Unpacked : A visual guide

#403

Post by gbibas »

troupo wrote: post #135
fragmede wrote: post #129

Earlier quoted context omitted.

How many LoC should it be, for that kind of program?

It's a TUI API wrapper with a few commands bolted on. I doubt it needs to be more than 20-50kloc. You can create a full 3D game with a custom 3D engine in 500k lines. What the hell is Claude Code doing?

[dead]

Re: Claude Code Unpacked : A visual guide

#405

Post by couscouspie »

autocracy101 wrote: post #114

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…

I thought that early coding assistants came to be written in some Java/TypeScript, because AI companies just had web-devs playing around and then made it a product even though the languages being such a misfit for terminal. Why did you decide for TypeScript?

Re: Claude Code Unpacked : A visual guide

#406

Post by throwatdem12311 »

xendo wrote: post #346
GoatInGrey wrote: post #342

Earlier quoted context omitted.

https://x.com/trq212/status/2014051501786931427 " Most people's mental model of Claude Code is that "it's just a TUI" but it should really be closer to "a small game engine". For each frame our pipeline constructs a scene graph with React then -> layouts elements -> rasterizes them to a 2d screen -> diffs that against the previous screen -> finally uses the diff to generate ANSI sequences to draw We have a ~16ms fram…

You can argue that any UI is like a game engine in that sense. Some make sensible choices and don't need to pretend they have to render at 60fps.

60fps is pathetic for a TUI when most terminals worth their salt are GPU accelerated and displays can be up to 240fps or even more. But let’s be real if I can play Quake at >500 fps they have no excuse.

Re: Claude Code Unpacked : A visual guide

#408

Post by zargon »

Melatonic wrote: post #373
amangsingh wrote: post #312

Earlier quoted context omitted.

Just posted it here: https://news.ycombinator.com/item?id=47601608 Thank you so much for the coffee offer, that genuinely made my day! I don't have a sponsor link set up. Honestly, the best support is just hearing if this actually helps you ship your personal project faster without losing your mind to prompt engineering. I really hope it gives you your sanity back. Let me know how it goes!

Some of your comments have already been marked as "dead" oddly enough that just seemed like normal comments explaining your rationale. edit: Also seems like peoples replies are getting downvoted to hell and getting marked as dead and dissapear. Someone must not like your idea :-)

Comments are marked dead by automatic processes, not through downvotes. They're dead before anyone sees them, and you can't vote on a dead comment. amangsingh's comments have probably triggered some automated moderation. Probably at least partially because they sound LLM-generated.

Re: Claude Code Unpacked : A visual guide

#409

Post by shepherdjerred »

mattmanser wrote: post #61
brabel wrote: post #38

Earlier quoted context omitted.

> is about a year old now, so it should be in prime shape A 1yo project may be in good shape if written by just one dev, maybe a few. But if you have many devs, I can guarantee it will be messy and buggy. If anything, at 1yo it is probably still full of bugs because not enough time has elapsed for people to run into them.

It's only 510k LoC, at ~100 lines of code a day for a year, this code base would take 23 engineers a year to write. That's for 220 working days in somewhere civilized. And I'm sure we all know that when working on a greenfield project you can produce a lot more LoC per day than maintaining a legacy one. Given that vibe code is significantly more verbose, you're probably talking about ~15 engineers worth of code? I kn…

Who writes only 100loc per day, especially on a greenfield project?

Re: Claude Code Unpacked : A visual guide

#410

Post by small_scombrus »

zeroq wrote: post #321
lateforwork wrote: post #307

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".

Our organic artisanal code is written by free-range developers
Post reply on HN