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

91–100 of 464 posts

Re: Claude Code Unpacked : A visual guide

#91

Post by ricardobeat »

AJRF wrote: post #85

This is AI slop. First command I looked at: /stickers: Displays earned achievement stickers for milestones like first commit, 100 tool calls, or marathon sessions. Stickers are stored in the user profile and rendered as ASCII art in the terminal. That is not what it does at all - it takes you to a stickermule website. What is the motivation for someone to put out junk like this?

Clout and reaching the top of HN apparently.

The animated explanation at the top is also way too fast at 1x, almost impossible to follow; that immediately hinted at the author not fully reading/experiencing the result before publishing this.

Re: Claude Code Unpacked : A visual guide

#93

Post by TeMPOraL »

afferi300rina wrote: post #78
lanbin wrote: post #72

However, excellent development practices involve modularizing code based on functional domains or responsibilities. The utils directory should only contain truly generic, business-agnostic utilities (such as date retrieval, simple string manipulation, etc.). We can see that the code produced by Vibe is not what a professional engineer would write. This may be due to the engineers using the Vibe tool.

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.

Re: Claude Code Unpacked : A visual guide

#94

Post by thepasch »

AJRF wrote: post #85

This is AI slop. First command I looked at: /stickers: Displays earned achievement stickers for milestones like first commit, 100 tool calls, or marathon sessions. Stickers are stored in the user profile and rendered as ASCII art in the terminal. That is not what it does at all - it takes you to a stickermule website. What is the motivation for someone to put out junk like this?

> What is the motivation for someone to put out junk like this?

Getting something with a link to their GitHub onto the frontpage of HN. Because form matters much more in this world than substance.

Re: Claude Code Unpacked : A visual guide

#95

Post by 000ooo000 »

troupo wrote: post #80
stingraycharles wrote: post #13

I guess they really do eat their own dogfood and vibe code their way through it without care for technical debt? In a way, it’s a good challenge, but it’s fairly painful to watch the current state of the project (which is about a year old now, so it should be in prime shape).

They explicitly boast about using claude code to write code: https://x.com/bcherny/status/2007179836704600237 That's how you get "oh this TUI API wrapper needs 68GB of RAM" https://x.com/jarredsumner/status/2026497606575398987 or "we need 16ms to lay out a few hundred characters on screen that's why it's a small game engine": https://x.com/trq212/status/2014051501786931427

Just finished looking at Ink here.. frontend world has no shame. Love the gloating about 40x less RAM as if that amount of memory for a text REPL even approaches defensible. "CC built CC" is not the flex people seem to suggest it is.

Re: Claude Code Unpacked : A visual guide

#96

Post by FartyMcFarter »

rzmmm wrote: post #62
makapuf wrote: post #51

Earlier quoted context omitted.

How was this generated ? I'm quite sure "with ai/claude code" but what are the actual steps ?

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?

Re: Claude Code Unpacked : A visual guide

#97

Post by spondyl »

brauhaus wrote: post #74

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 spit out over months using Claude defaults.

I guess I just find it weird because all the signals are messed up so whenever I see these sorts of layouts, I feel like I'm looking at the average where I don't think "gorgeous and interesting" at all. Instead, I'm forced to think "I should be skeptical of this based on the presentation because it presents as high quality but this may be hiding someone who is not actually aware of what they're presenting in any depth" as the author may have just shoved in a prompt and let it spin.

There's actually a similarly designed website (font weights, font styles etc) here in New Zealand (https://nzoilwatch.com/) where at a glance, it might seem like some overloaded professional-backed thing but instead it's just some guy who may or may not know anything about oil at all, yet people are linking it around the place like some sort of authoritative resource.

I would have way less of an issue if people just put their names by things and disclosed their LLM usage (which again, is fine) rather than giving the potentially false impression to unequipped people that the information presented is actually as accurate and trustworthy as the polish would suggest.

Re: Claude Code Unpacked : A visual guide

#98

Post by franze »

jwilliams wrote: post #5
restlessforge wrote: post #2

Okay those "hidden features" are amazing, especially the cross-session referencing. I hope we can look forward to that in the future Also I definitely want a Claude Code spirit animal

It's live! If you're on the latest cc you can use /buddy now.

[dead]

Re: Claude Code Unpacked : A visual guide

#99

Post by cududa »

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…

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

Re: Claude Code Unpacked : A visual guide

#100

Post by supersparrow »

raincole wrote: post #92
brauhaus wrote: post #74

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

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.

Post reply on HN