151–160 of 221 posts
Earlier quoted context omitted.
These are the perfect size projects vibe coding is currently good for. So far... it's going to keep getting better to the point until all software is written this way.
Air traffic control software is not going to be vibe-coded anytime soon and neither is the firmware controlling the plane.
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.
This comment is wrong in two ways: 1. Current LLMs do much better than produce "small programs that already exist in multiple forms in the training data". Of course the knowledge they use does need to exist somewhere in training data, but they operate at a higher level of abstraction than simply spitting out programs they've already seen whole cloth. Way higher. 2. Inventing a new compression algorithm is beyond the…
Earlier quoted context omitted.
These are the perfect size projects vibe coding is currently good for. So far... it's going to keep getting better to the point until all software is written this way.
It seems like it's approaching a horizontal asymptote to me, or is at the very least concave down. You might be describing a state 50 years from now.
ARC AGI 2: https://x.com/poetiq_ai/status/2003546910427361402
METR: https://metr.org/blog/2025-03-19-measuring-ai-ability-to-com...
Earlier quoted context omitted.
Successfully building an IKEA shelf doesn’t make you a carpenter.
no, but I have furniture. it's important to keep sight of the end goal, unless the carpentry is purely a hobby.
Earlier quoted context omitted.
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.
> 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 usually grimace at "GPT smell". The lines you quoted stood out to me as well, but I interpreted them as "early career blogger smell". It's similar, but it didn't come off as AI. I think because it avoided grandiose words, and because it reused the exact same phrase format (like a human tic) rather than randomly sampling the format category (like an AI). This is what human text looks like when it's coming from someone who is earnestly trying to have a punchy, intentional writing style, but who has not yet developed an editor's eye (or asked others to proofread), which would help smooth out behaviors that seem additive in isolation but amateur in aggregate.
Did others share the impression that it's a human doing the same classic tricks that AI is trained to copy, or does anything in this category immediately betray AI usage?
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…
Earlier quoted context omitted.
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.
Who really cares? The goalpost of "AI is useless because I can't vibe code novel discoveries" is a strawman. AI and vibe coding are transformational. So are AI-enhanced efforts to solve longstanding, difficult scientific problems. If cancer is cured with AI assistance, does it really matter if it was vibe-cured or state-of-the-art-lab-cured?
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.