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...
.
Claude Code Unpacked : A visual guide
81–90 of 464 posts
Re: Claude Code Unpacked : A visual guide
#82However, 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.
[dead]
Re: Claude Code Unpacked : A visual guide
#83Re: Claude Code Unpacked : A visual guide
#84why do people care so much? it's just an agentic loop
Re: Claude Code Unpacked : A visual guide
#85This 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.
What is the motivation for someone to put out junk like this?
Re: Claude Code Unpacked : A visual guide
#86Even 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 think it is accurate. Where are the autonomous AI who beat the creator to the punch? When we write "Hello, World!" in C and compile it with `gcc`, do we give credit to every contributor to GNU? AI is a tool that thus far only humans are capable of using with the unique inspiration. Will this change in the future? Certainly. But is it the case now? I think my questions imply some reasonable objections.
Re: Claude Code Unpacked : A visual guide
#87Even 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 mean, tools change, but I'd be happy to hear if any tool can create that by just saying create "Claude Code Unpack" with nice graphics. or some other single prompt. It likely was an iterative process and it would be lovely if more people started sharing that, because the process itself is also very interesting.
I've created some chinese characters learning website and I took me typing 1/3 of LoTR to get there[1]. I would have typed like 1% of that writing code directly. It is a different process, but it still needs some direction.
Re: Claude Code Unpacked : A visual guide
#88Even today, I'm still astounded that there are people capable of building a gorgeous and interesting site like this in less than 2 days...
Is this gorgeous?
Content resizing, needing to juggle a speed knob to read, and the overall presentation makes it feel like Edward Tufte flavored nightmare fuel.
Re: Claude Code Unpacked : A visual guide
#89Even today, I'm still astounded that there are people capable of building a gorgeous and interesting site like this in less than 2 days...
Claude itself can generate this in minutes if you know how to ask.
Re: Claude Code Unpacked : A visual guide
#90[dead]