Claude Code Unpacked : A visual guide
181–190 of 464 posts
Re: Claude Code Unpacked : A visual guide
#182Earlier quoted context omitted.
Well, I assume this is all just generated with Claude Code, right? Whether there is much back and forth with the LLM is a valid question and nothing wrong with generating websites (I do it too for some side projects). Claude loves generating websites with a particular style of serif font. We also saw this with https://tboteproject.com/timeline/ and I've just generally seen it from various designs that coworkers have…
I really wish I had that clout-chasing gene - it doesn't even occur to me until I see someone else do it. I'm serious. The hype chasing clearly clearly matters. . things like this: https://github.com/instructkr/claw-code I mean ok, serious people put in years of effort for 100 of those stars ... it's continually wild how extremely irrelevant hard effortful careful work is. I think that's the game. Get up, look at the…
Re: Claude Code Unpacked : A visual guide
#183Re: Claude Code Unpacked : A visual guide
#184Earlier quoted context omitted.
I really wish I had that clout-chasing gene - it doesn't even occur to me until I see someone else do it. I'm serious. The hype chasing clearly clearly matters. . things like this: https://github.com/instructkr/claw-code I mean ok, serious people put in years of effort for 100 of those stars ... it's continually wild how extremely irrelevant hard effortful careful work is. I think that's the game. Get up, look at the…
We do need "hard effortful careful work" to keep planes flying, electrical grids running and medical devices safe. It's very relevant but very undervalued by our current economy.
Re: Claude Code Unpacked : A visual guide
#185A 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
#186Re: Claude Code Unpacked : A visual guide
#187Re: Claude Code Unpacked : A visual guide
#188Earlier quoted context omitted.
Is there a reason to think it was done by an LLM?
The biggest reason would be: do you know a single developer who could have produced this in a couple of hours?
Re: Claude Code Unpacked : A visual guide
#189A 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;…
What do you mean by "actually governing the agents at the system level", and how is it different from "herding cats"?
System-level governance means the LLM is completely stripped of orchestration rights. It becomes a stateless, untrusted function. The state lives in a rigid, external database (like SQLite). The database dictates the workflow, hands the LLM a highly constrained task, and runs external validation on the output before the state is ever allowed to advance. The LLM cannot unilaterally decide a task is done.
I got so frustrated with the former while working on a complex project that I paused it to build a CLI to enforce the latter. Planning to drop a Show HN for it later today, actually.
Re: Claude Code Unpacked : A visual guide
#190Earlier quoted context omitted.
More code means more entropy, more room for bugs, harder to find issues, more time to fix, more attack surface, more memory used, more duplication, more inconsistencies... I bet you at some point we'll get someone reporting how AI performance deteriorates as the code base grows, and some blog post about how their team improved the success of their AI by trimming the code base down to less than 100k LOC or something l…
The history of programming is also each generation writing far less performant code than the one before it. The history of programming is each generation bemoaning the abstractions, waste and lack of performance of the code of the next generation. It turns out that there is a tradeoff in code between velocity and quality that smart businesses consider relative to hardware cost/quality. The businesses that are outcomp…