Live data from Hacker News

Show HN: Vibe coding a bookshelf with Claude Code

balajmarius.com

71–80 of 221 posts

Re: Show HN: Vibe coding a bookshelf with Claude Code

#71

These are the perfect size projects vibe coding is currently good for. At some point you hit a project size that is too large or has too many interdependencies, and you have to be very careful about how you manage the context and should expect the llm to start generating too much code or subtle bugs. Once you hit that size, in my opinion, it's usually best to drop back to brainstorming mode, only use the llm to help…

Reminds me of Ken Miles saying 7000 rpm quote. At what size do you think this happens? Whatever is the most relevant metric of size for this context.

Re: Show HN: Vibe coding a bookshelf with Claude Code

#73

> What I needed was not a better app, but a way to tolerate imperfection without the whole system falling apart. > Claude did not invent that idea. It executed it. > Claude handled implementation. I handled taste. This style of writing always gets me now :)

This style of writing isnt human. Its AI. ^^ These dramatic statements are almost always AI influenced, I seem to always see them in people's emails now as well. "we didnt reinvent the wheel. we are the wheel."

You are absolutely right. It’s not X that’s the give away, it’s A, and B — moreover it’s C that is the clincher.

Re: Show HN: Vibe coding a bookshelf with Claude Code

#74
post #56

I am yet to see a vibe coded success that isn't a small program that already exists in multiple forms in the training data. Let's see something ground-breaking. If AI coding is so great and is going to take us to 10x or 100x productivity let's see it generate a new, highly efficient compression algorithm or a state-of-art travelling salesman solution.

Forget utterly groundbreaking things, I want to hear maintainers of complex, actively developed, and widely used open-source projects (e.g. ffmpeg, curl, openssh, sqlite) start touting a massive uptick in positive contributions, pointing to a concrete influx of high-quality AI-assisted commits. If AI is indeed a 10x force multiplier, shouldn't these projects have seen 10 years' worth of development in the last year?…

> Being able to not only look up but automatically integrate things into your codebase that already exist in some form in the training data is incredibly useful.

Until it decides to include code it gathered from a stackoverflow post 15 years ago probably introducing security related issues or makes up libraries on the go or even worse, tries to make u install libs that were part of a data poisoning attack.

Re: Show HN: Vibe coding a bookshelf with Claude Code

#75
post #56

I am yet to see a vibe coded success that isn't a small program that already exists in multiple forms in the training data. Let's see something ground-breaking. If AI coding is so great and is going to take us to 10x or 100x productivity let's see it generate a new, highly efficient compression algorithm or a state-of-art travelling salesman solution.

> Let's see something ground-breaking

Why? People don't ask hammers to do much more than bash in nails into walls.

AI coding tools can be incredibly powerful -- but shouldn't that power be focused on what the tool is actually good at?

There are many, many times that AI coding tools can and should be used to create a "small program that already exists in multiple forms in the training data."

I do things like this very regularly for my small business. It's allowed me to do things that I simply would not have been able to do previously.

People keep asking AI coding tools to be something other than what they currently are. Sure, that would be cool. But they absolutely have increased my productivity 10x for exactly the type of work they're good at assisting with.

Re: Show HN: Vibe coding a bookshelf with Claude Code

#76

> What I needed was not a better app, but a way to tolerate imperfection without the whole system falling apart. > Claude did not invent that idea. It executed it. > Claude handled implementation. I handled taste. This style of writing always gets me now :)

This style of writing isnt human. Its AI. ^^ These dramatic statements are almost always AI influenced, I seem to always see them in people's emails now as well. "we didnt reinvent the wheel. we are the wheel."

AI is popularizing a writing style that has been common in advertising for quite some time. For example, Apple uses it a lot. Now everyone can imitate advertising copy.

Re: Show HN: Vibe coding a bookshelf with Claude Code

#77

> What I needed was not a better app, but a way to tolerate imperfection without the whole system falling apart. > Claude did not invent that idea. It executed it. > Claude handled implementation. I handled taste. This style of writing always gets me now :)

I feel ya but it didn't get me on this one for some reason. But it gets me a lot on Linkedin - due to which I lost control and blasted off a post yesterday.

I think it some kind of value - vibe dynamics that play in making the brain conscious about it being written with AI or otherwise.

Re: Show HN: Vibe coding a bookshelf with Claude Code

#78
post #74

Earlier quoted context omitted.

Forget utterly groundbreaking things, I want to hear maintainers of complex, actively developed, and widely used open-source projects (e.g. ffmpeg, curl, openssh, sqlite) start touting a massive uptick in positive contributions, pointing to a concrete influx of high-quality AI-assisted commits. If AI is indeed a 10x force multiplier, shouldn't these projects have seen 10 years' worth of development in the last year?…

> Being able to not only look up but automatically integrate things into your codebase that already exist in some form in the training data is incredibly useful. Until it decides to include code it gathered from a stackoverflow post 15 years ago probably introducing security related issues or makes up libraries on the go or even worse, tries to make u install libs that were part of a data poisoning attack.

It's no different from supervising a naïve junior engineer who also copy/pastes from 15 year old SO posts (a tale as old as time): you need to carefully review and actually grok the code the junior/AI writes. Sometimes this ends up taking longer than writing it yourself, sometimes it doesn't. As with all decisions in delegating work, the trick is knowing ahead of time whether this will be the case.

Re: Show HN: Vibe coding a bookshelf with Claude Code

#79
post #56

I am yet to see a vibe coded success that isn't a small program that already exists in multiple forms in the training data. Let's see something ground-breaking. If AI coding is so great and is going to take us to 10x or 100x productivity let's see it generate a new, highly efficient compression algorithm or a state-of-art travelling salesman solution.

Forget utterly groundbreaking things, I want to hear maintainers of complex, actively developed, and widely used open-source projects (e.g. ffmpeg, curl, openssh, sqlite) start touting a massive uptick in positive contributions, pointing to a concrete influx of high-quality AI-assisted commits. If AI is indeed a 10x force multiplier, shouldn't these projects have seen 10 years' worth of development in the last year?…

curl in particular is being plagued by AI-slop security reports which are actively slowing development by forcing the maintainers to triage crap when they could be working on new features (or, you know, enjoying their lives) eg https://www.theregister.com/2025/07/15/curl_creator_mulls_ni...

Re: Show HN: Vibe coding a bookshelf with Claude Code

#80
post #74

Earlier quoted context omitted.

> Being able to not only look up but automatically integrate things into your codebase that already exist in some form in the training data is incredibly useful. Until it decides to include code it gathered from a stackoverflow post 15 years ago probably introducing security related issues or makes up libraries on the go or even worse, tries to make u install libs that were part of a data poisoning attack.

It's no different from supervising a naïve junior engineer who also copy/pastes from 15 year old SO posts (a tale as old as time): you need to carefully review and actually grok the code the junior/AI writes. Sometimes this ends up taking longer than writing it yourself, sometimes it doesn't. As with all decisions in delegating work, the trick is knowing ahead of time whether this will be the case.

Naive junior engineers eventually learn and become competent senior engineers. LLMs forget everything they "learn" as soon as the context window gets too big.
Post reply on HN