[flagged]
Please don’t use AI to write comments on HN.
Claude Code Unpacked : A visual guide
31–40 of 464 posts
Re: Claude Code Unpacked : A visual guide
#32How is this on the front page?
Re: Claude Code Unpacked : A visual guide
#33Re: Claude Code Unpacked : A visual guide
#34Re: Claude Code Unpacked : A visual guide
#35Re: Claude Code Unpacked : A visual guide
#36Re: Claude Code Unpacked : A visual guide
#37Re: Claude Code Unpacked : A visual guide
#38I 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).
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.
Re: Claude Code Unpacked : A visual guide
#39Earlier quoted context omitted.
It's live! If you're on the latest cc you can use /buddy now.
It's a ridiculous folly. I've already lost a well-constructed question because I accidentally tabbed into my pointless 'buddy'. (Yes, I know I can turn it off. I have.)
Re: Claude Code Unpacked : A visual guide
#40I mean, I get it: vibe-coded software deserves vibe-coded coverage. But I would at least appreciate it if the main part of it, the animation, went at a speed that at least makes it possible to follow along and didn't glitch out with elements randomly disappearing in Firefox... How is this on the front page?