Earlier quoted context omitted.
https://thenewstack.io/how-deepminds-alphatensor-ai-devised-... Not either of the species of algorithms you've described, but still an advance.
That's about as far removed from vibe coding as you can get. It's the result of an algorithm developed for a specific purpose by researchers at one of the most advanced machine learning companies.
Show HN: Vibe coding a bookshelf with Claude Code
131–140 of 221 posts
Re: Show HN: Vibe coding a bookshelf with Claude Code
#132I 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.
More generally, I do think LLMs grant 10x+ performance for most common work: most of what people do manually is in the training data (which is why there's so much of it in the first place.) 10x+ in those domains can in theory free up more brain space to solve the problems you're talking about.
My advice to you is to tone down the cynicism, and see how it could help you. I'll admit, AI makes me incredibly anxious about my future, but it's still fun to use.
Re: Show HN: Vibe coding a bookshelf with Claude Code
#133Re: Show HN: Vibe coding a bookshelf with Claude Code
#134Re: Show HN: Vibe coding a bookshelf with Claude Code
#135Earlier quoted context omitted.
I agree with you as far as project size for vibe-coding goes - as-in often not even looking at the generated code. But I have no issues with using Claude Code to write code in larger projects, including adapting to existing patterns, it’s just not vibe coding - I architect the modules, and I know more or less exactly what I want the end result to be. I review all code in detail to make sure it’s precisely what I want…
> I know more or less exactly what I want the end result to be This is key. And this is also why AI doesn't work that well for me. I don't know yet how I want it to work. Part of the work I do is discovering this, so it can be defined.
1. Have the ai come up with an implementation plan based on my requirements
2. Iterate on the implementation plan / tweak as needed, and write it to a markdown file
3. Have it implement the above plan based on the markdown file.
On projects where we split up the task into well defined, smaller tickets, this works pretty well. For larger stuff that is less well defined, I do feel like it's less efficient, but to be fair, I am also less efficient when building this stuff myself. For both humans and robots, smaller, well defined tickets are better for both development and code review.
Re: Show HN: Vibe coding a bookshelf with Claude Code
#136Earlier quoted context omitted.
> 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…
> Why? People don't ask hammers to do much more than bash in nails into walls. No one is propping up a multi-billion dollar tech bubble by promising hammers that do more than bash nails. As a point of comparison that makes no sense.
Re: Show HN: Vibe coding a bookshelf with Claude Code
#137Earlier quoted context omitted.
Every two months, I run a very simple experiment to decide whether I should stop shorting NVDA....Think of it as my personal Pelican on a Bike test. :-) Here is how it works: I take the latest state of the art model, usually one of the two or three currently being hyped....and ask it to create a short document that teaches Java, Python, or Rust, in 30 to 60 min, complete with code examples. Then I ask the same model…
You clearly live in a different reality than me entirely. Complete opposite experience.
Re: Show HN: Vibe coding a bookshelf with Claude Code
#138Earlier quoted context omitted.
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.
Heh.
Re: Show HN: Vibe coding a bookshelf with Claude Code
#139Earlier quoted context omitted.
Every two months, I run a very simple experiment to decide whether I should stop shorting NVDA....Think of it as my personal Pelican on a Bike test. :-) Here is how it works: I take the latest state of the art model, usually one of the two or three currently being hyped....and ask it to create a short document that teaches Java, Python, or Rust, in 30 to 60 min, complete with code examples. Then I ask the same model…
Ok, but if you wrote some massive corpus of code with no testing it probably would not compile either. I think if you want to make this a useful experiment you should use one of the coding assistants that can test and iterate on its code, not some chatbot which is optimized to impress nontechnical people while being as cheap as possible to run.
Is that how we call Opus 4.5 now? :-)
Re: Show HN: Vibe coding a bookshelf with Claude Code
#140> 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 :)