[flagged]
... writing the code was never the slow part. correctness (according to what people actually needed) has always been the slow part.
The 100 hour gap between a vibecoded prototype and a working product
301–310 of 362 posts
Re: The 100 hour gap between a vibecoded prototype and a working product
#302Earlier quoted context omitted.
I thought everyone realized by now that a digital image made available via block chain or any other mechanism, can be duplicated indefinitely. The only thing you get is a copyright on some generated image or set of bits. And what are the chances any random digital image is going to be appreciated as art? You can't hang it in a living room or sit it on a coffee table. It's beanie babies, but without even a hill of bea…
Isn't the same true of any intellectual property? A movie can be duplicated indefinitely. There's no guarantee your song will be appreciated as art. I'm not sure why you say you can't print out an image and hang it in your living room; we do that all the time at home. I've personally never dabbled in NFTs, but I don't think it's fair to ascribe the inherent conflict between information and scarcity uniquely to them.
The difference is, there is a person or many people collaborating who created the song, movie, etc. there's a dipshit with an RNG who created the NFT.
Re: The 100 hour gap between a vibecoded prototype and a working product
#303Earlier quoted context omitted.
It's good enough for the folks who choose to do it that way. Many of them do things that are quite "serious"... Databases, kafka, the lmax disruptor, and reams of performance critical proprietary code have been and continue to be written in java. It's not low effort, you have to be careful, get intimate with the garbage collector, and spend a lot of time profiling. It's a totally reasonable choice to make if your tea…
> Databases, kafka, the lmax disruptor, and reams of performance critical proprietary code have been and continue to be written in java. those have low bar of performance, also they mostly became popular because of investments from Java hype, and rust didn't exist or had weak ecosystem at that time.
[deleted]
Re: The 100 hour gap between a vibecoded prototype and a working product
#304Earlier quoted context omitted.
Crypto has very narrow usage unless you're a criminal or a bro, NFT has essentially 0 non-bro activity, surely AI attracts bros, but also some of the smartest people I've known have been working on it a long time to build truly useful things. AI can be really attractive to bros but also be incredibly useful. In other words, AI isn't a trend that's going to pass, it's permanently going to reshape the tech scene and ec…
> AI isn't a trend that's going to pass, it's permanently going to reshape the tech scene and economy in a way that cryptocoins and NFTs absolutely did not. This exact wording was used for crypto. "It isn't a trend that's going to pass" and "It's going to reshape everything." Why are we sure of it now for AI (and that we're going to be right), when they were also sure of it before for crypto (and they ended up wrong)…
>The AI people have the exact same feelings of absolute certainty as the crypto people had.
Yes, this is what hype is like. Something being hyped doesn't automatically mean it's going to go bust.
Again, everyone smart was making fun of NFT at its peak. People who accomplish things are excited by LLMs, not just teenagers, grifters, bros, and your weird uncle.
Re: The 100 hour gap between a vibecoded prototype and a working product
#305[dead]
Re: The 100 hour gap between a vibecoded prototype and a working product
#306Earlier quoted context omitted.
> AI isn't a trend that's going to pass, it's permanently going to reshape the tech scene and economy in a way that cryptocoins and NFTs absolutely did not. This exact wording was used for crypto. "It isn't a trend that's going to pass" and "It's going to reshape everything." Why are we sure of it now for AI (and that we're going to be right), when they were also sure of it before for crypto (and they ended up wrong)…
People's grandmothers know what AI is and many have used it, even outside the west. Probably zero grandmothers outside the west, and very few grandmothers within the west, know what NFT even stands for.
But they do know what crypto is for and several of them would have lost money on it.
Re: The 100 hour gap between a vibecoded prototype and a working product
#307Earlier quoted context omitted.
Related anecdote: My 12yo son didn't like the speed cubing online timer he was using because it kept crashing the browser and interrupted him with ads. Instead of googling a better alternative we sat down with claude code and put together the version of the website that behaved and looked exactly as he wanted. He got it working all by himself in under an hour with less than 10 prompts, I only helped a bit putting it…
I don't think people are grasping yet that this is the future of software, if by no metric other than "most software used is created by the user".
Outside of small niches, no-one wants to maintain and host their own software.
This is not the future of software.
Re: The 100 hour gap between a vibecoded prototype and a working product
#308Earlier quoted context omitted.
> I rarely read the LinkedIn social feed but when I check mine it’s now filled with claims from people about going from idea to shipped product in N days (with a note at the bottom that they’re looking for a new job or available to consult with your company). This always seems to be the pattern. "I vibe coded my product and shipped it in 96 hours!" OK, what's the product? Why haven't I heard of it? Why can't it repla…
I found one example of this going very wrong on reddit the other day - https://www.reddit.com/r/selfhosted/comments/1rckopd/huntarr... One redditor security reviews a vibe coded project
The self hosted reddit has been inundated with slop and is trying to ban it. It's not a good idea to run anyone else's vibe code!
Re: The 100 hour gap between a vibecoded prototype and a working product
#309I’ve had a similar experience. I’ve been vibecoding a personal kanban app for myself. Claude practically one-shotted 90% of the core functionality (create boards, lanes, cards, etc.) in a single session. But after that I’ve now spent close to 30 hours planning and iterating on the remaining features and UI/UX tweaks to make the app actually work for me, and still, it doesn’t feel "ready" yet. That’s not to say it has…
Was a kanban board ever that hard?
Trello was written by interns as a summer project, when SPAs were just becoming a thing and React didn't even exist.
With 30 hours I bet I could get a pretty good one up without vibe coding it.
In a single afternoon I could get boards, cards, lanes, etc done. React, MaterialUI uaing Grid + Card and you're almost done.
Re: The 100 hour gap between a vibecoded prototype and a working product
#310The 100 hours aren't a vibecoding tax. They're an engineering knowledge tax.
I built 4 AI products to hundreds of thousands of users, working with AI agents as collaborators, not autopilots. The difference isn't the tool. It's whether you can tell the AI is wrong and stop it before it wastes 10 hours going down the wrong path.
The author watched Claude create new S3 buckets for several rounds before catching it. An experienced engineer catches that on the first diff. Most of those 100 hours were spent not knowing you're lost.
"Vibecoding" as a concept is the problem. It implies you can vibe your way through engineering. You can't. AI is a force multiplier, not a replacement for knowing what good looks like.