Live data from Hacker News

Claude Code Unpacked : A visual guide

ccunpacked.dev

101–110 of 464 posts

Re: Claude Code Unpacked : A visual guide

#101
post #62

Earlier quoted context omitted.

For the animations specifically, it's using Motion (fka Framer Motion) Javascript library. If you describe some animations from the site to an LLM and ask it to use Framer motion, you get very similar results. The creator likely just prompted for a while until they were happy with the outcome.

Is there a reason to think it was done by an LLM?

It states "curation assisted by AI" at the bottom.

Re: Claude Code Unpacked : A visual guide

#102

Earlier quoted context omitted.

That's the hallmark of "vibe coding": optimizing for immediate output while treating the utils folder as a generic junk drawer.

Another "hallmark" that happens to describe pretty much every codebase people wrote even before LLMs were a thing.

Sadly, the AI’s have been trained on human developed repos.

Re: Claude Code Unpacked : A visual guide

#103
post #53

Earlier quoted context omitted.

Which makes for an interesting thought / discussion; code is written to be read by humans first, executed by computers second. What would code look like if it was written to be read by LLMs? The way they work now (or, how they're trained) is on human language and code, but there might be a style that's better for LLMs. Whatever metric of "better" you may use. Just a thought experiment, I very much doubt I'm the first…

LLMs read and write human-code because humans have been reading and writing human-code. The sample size of assembly problems is, in my estimate, too small for LLMs to efficiently read and write it for common use cases. I liken it to the problem of applying machine learning to hard video games (e.g. Starcraft). When trained to mimic human strategies, it can be extremely effective, but machine learning will not discove…

But starcraft training is not through mimicking human strategies - it was pure RL with a reward function shaped around winning, which allows it to emerge non-human and eventually super-human strategies (such as the worker oversaturation).

The current training loop for coding is RL as well - so a departure from human coding patterns is not unexpected (even if departure from human coding structure is unexpected, as that would require development of a new coding language).

Re: Claude Code Unpacked : A visual guide

#104

Even today, I'm still astounded that there are people capable of building a gorgeous and interesting site like this in less than 2 days...

I was talking to one of the people who works at a big agentic coding tools. If I recall correctly, he was talking about how they use the tool to build the tool. I was complaining that all of the websites/frontends I make look pretty weak, and I'm amazed they get much slicker looking UIs with the same tool. He showed me that one way they do it is by having an extensive UI library of components/graphics/whatever, and also mentioned that the folks build their UIs know how to prompt/use the tool because it's backed by years of UI development knowledge & superior resources. I realized I didn't have any of that, and it actually made me feel better.

Last week we I was struggling to go from vague prompt to a OMG-it's-so-nice-looking web app, I remembered that example above and then decided to create my own component library, which I did in a couple days: https://www.substrateui.dev/. I was actually super happy that I was able to accomplish that, and then I realized I wanted to better understand the content that I had vibe coded into existence. So now I'm recreating that design system step by step w/ Claude code, filling in gaps in my knowledge & learning a bit about colors, typography, CSS, blah blah blah. It's actually a lot of fun because I'm able to explore all of the concepts and learn enough to build a front end that doesn't suck & is good enough for my use case without getting stuck for days on trying to center a stupid div by hand or play whack-mole-fix-something-and-break-something-else when trying to clean up AI slop.

Re: Claude Code Unpacked : A visual guide

#105
post #99

Earlier quoted context omitted.

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…

When you say it’s not a massive codebase, I’m curious, what are you comparing it to?

The previous poster was making out that in a year the code base would be a mess if people had done it.

This is a two-pizza team sized project, so it's not a project that the code quality would inevitably spiral out of control due to communication problems.

A single senior architect COULD have kept the code quality under control.

Re: Claude Code Unpacked : A visual guide

#106
post #97

Even today, I'm still astounded that there are people capable of building a gorgeous and interesting site like this in less than 2 days...

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 headlines, figure out how you can exploit them with vibe coding, do some hyphy project and repeat.

Maybe some lobster themed bullshit between openclaw and the claudecode leak.

I'm not being a cynic here, I'm just telling you what I'm going to do tomorrow.

Re: Claude Code Unpacked : A visual guide

#107

Earlier quoted context omitted.

But somehow, according to HN, LLMs make you less productive, not more :)

The people who don’t know how to use an LLM to make them more productive, or are scared it’s going to take their job, are louder than the people who are making good use of them to make them more productive. That just seems to be human nature unfortunately - the complainers are always louder.

What? We must have different internets, I agree in general, but the "AI is the second coming" crowd is louder than standing next to a jet on takeoff. I'm in the "AI is making me more productive but a worse developer" crowd, don't know what I count as.

Re: Claude Code Unpacked : A visual guide

#108
post #11
post #7

There's this weird thing about AI generated content where it has the perfect presentation but conveys very little. For example the whole animation on this website, what does it say beyond that you make a request to backend and get a response that may have some tool call?

Also it's just randomly incorrect in places. For instance, it lists "fox" as one of the "Buddy" species, but that's not in the code.

The classification is pretty weird sometimes, too. For example the `/exit` slash command is filed under advanced and experimental commands...

Re: Claude Code Unpacked : A visual guide

#109

Even today, I'm still astounded that there are people capable of building a gorgeous and interesting site like this in less than 2 days...

I was talking to one of the people who works at a big agentic coding tools. If I recall correctly, he was talking about how they use the tool to build the tool. I was complaining that all of the websites/frontends I make look pretty weak, and I'm amazed they get much slicker looking UIs with the same tool. He showed me that one way they do it is by having an extensive UI library of components/graphics/whatever, and a…

that's really awesome. how did you go about building the component library?

Re: Claude Code Unpacked : A visual guide

#110
519K lines of code for something that is using the baseline *nix tools for pretty much everything important, how do they even manage to bloat it this much? I mean I know how technically, but it's still depressing. Can't they ask CC to make it good, instead of asking it to make it bigger?
Post reply on HN