Live data from Hacker News

Claude Code Unpacked : A visual guide

ccunpacked.dev

391–400 of 464 posts

Re: Claude Code Unpacked : A visual guide

#391

Earlier quoted context omitted.

It screams vibe coding. This is the anthropic look. Just ask Claude and give it a screenshot.

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.

You well on the path to AI-fueled psychosis if you genuinely believe this.

Re: Claude Code Unpacked : A visual guide

#392
post #321

Earlier quoted context omitted.

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

Depending on your standards and what company is making it you could even have “cruelty free.”

[dead]

Re: Claude Code Unpacked : A visual guide

#393

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.

You well on the path to AI-fueled psychosis if you genuinely believe this.

I genuinely believe this. Even if you're inventing a new algorithm it is better to describe the algorithm in English and have AI do the implementation.

Re: Claude Code Unpacked : A visual guide

#395
post #345

Earlier quoted context omitted.

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.

Can you please explain the use here? I tried the demo, and cat, cp, echo, etc... seem to do the exact same thing without the cost. Their demo even says: `Paste any code or text below. Our model will produce an AI-generated, byte-for-byte identical output.` Unless this is a parody site can you explain what I am missing here? Token echoing isn't even to the lexeme/pattern level, and not even close to WSD, Ogden's Lemma…

It's satire - just see the About page.

Re: Claude Code Unpacked : A visual guide

#396
post #297

Earlier quoted context omitted.

Somebody somewhere is bragging to someone about using React to render a grid of ASCII characters.

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…

Do they reconstruct the scene graph for each frame?! Maybe I'm overinterpreting the phrasing. Someone take a peek at the source?

Re: Claude Code Unpacked : A visual guide

#397

Earlier quoted context omitted.

How about releasing your own source code? It is a beautiful site, love the UX as well as functionality.

It screams vibe coding. This is the anthropic look. Just ask Claude and give it a screenshot.

Must everything be artisanal for some people?

Re: Claude Code Unpacked : A visual guide

#398

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

You need state oriented programming to handle that. I know, because I made one. The keyword is „unpredictability”. Embrace nondeterminism.
Post reply on HN