Live data from Hacker News

The 100 hour gap between a vibecoded prototype and a working product

kanfa.macbudkowski.com

21–30 of 362 posts

Re: The 100 hour gap between a vibecoded prototype and a working product

#21

With sufficiently advanced vibe coding the need for certain type of product just vanishes. I needed it, I quickly build it myself for myself, and for myself only.

I dont want that though, I want someone to spend much more time than I can afford thinking about and perfecting a product that I can pay for and dont worry about it

If we could return to one-off payments without dark patterns I would agree. Hopefully at least the software that rely on grift will start to vanish.

Re: The 100 hour gap between a vibecoded prototype and a working product

#22
I can't say I'm impressed by this at all. 100+ hours to build a shitty NFT app that takes one picture and a predefined prompt, then mints you a dinosaur NFT. This is the kind of thing I would've seen college students slam out over a weekend for a coding jam with no experience and a few cans of red bull with more quality and effort. Has our standards really gotten so low? I don't see any craftsmanship at play here.

Re: The 100 hour gap between a vibecoded prototype and a working product

#23
If you ask for something complicated this headline is more than true. But why complicate things, keep it simple and keep it fast.

Also this article uses 'pfp' like it's a word, I can't figure out what it means.

I'm able to vibe code simple apps in 30 minutes, polish it in four hours and now I've been enjoying it for 2 months.

Re: The 100 hour gap between a vibecoded prototype and a working product

#24

If you ask for something complicated this headline is more than true. But why complicate things, keep it simple and keep it fast. Also this article uses 'pfp' like it's a word, I can't figure out what it means. I'm able to vibe code simple apps in 30 minutes, polish it in four hours and now I've been enjoying it for 2 months.

I noticed this as well. I had to look it up. Apparently ‘pfp’ means ‘profile picture’.

Re: The 100 hour gap between a vibecoded prototype and a working product

#26

With sufficiently advanced vibe coding the need for certain type of product just vanishes. I needed it, I quickly build it myself for myself, and for myself only.

This is a pipe dream and “sufficiently advanced” is doing a lot of heavy lifting. You really think people would rather spin up and debug their own self-made software rather than pay for something that has been tested, debugged, and proven by thousands of users? Why would anyone do that for anything more than a very simple script? It makes zero sense unless the LLM outputs literally perfect one-shot software reliably.

Re: The 100 hour gap between a vibecoded prototype and a working product

#27

>> people who say they "vibecoded an app in 30 minutes" are either building simple copies of existing projects, those are not copies, they aren't even features. usually part of a tiny feature that barely works only in demo. with all vibe coding in the world today you still need at least 6 months full time to build a nice note taking app . If we are talking something more difficult - it will be years - or you will nee…

>with all vibe coding in the world today you still need at least 6 months full time to build a nice note taking app. Bad example, note apps loaded with features are anti-productive and are for people who treat note taking as a hobby itself. You have Obsidian anyway if you want something open source to work with.

Ah, note taking as hobby finally explains to me why these apps seem so popular. I don't think I have ever considered that I need one. And it to be something that shouldn't be fully solved multiple times now. But it really being hobby does kinda make the point for me.

Re: The 100 hour gap between a vibecoded prototype and a working product

#28

If you ask for something complicated this headline is more than true. But why complicate things, keep it simple and keep it fast. Also this article uses 'pfp' like it's a word, I can't figure out what it means. I'm able to vibe code simple apps in 30 minutes, polish it in four hours and now I've been enjoying it for 2 months.

Apparently it means profile photo.

Re: The 100 hour gap between a vibecoded prototype and a working product

#29
If you hear someone spouting off about how vibe coding allows for creation of killer apps in a fraction of the time/cost, just ask them if you can see what successful killer apps they’ve created with it. It’s always crickets at that point because it’s somewhere between wishful thinking and an outright lie.

Re: The 100 hour gap between a vibecoded prototype and a working product

#30

>> people who say they "vibecoded an app in 30 minutes" are either building simple copies of existing projects, those are not copies, they aren't even features. usually part of a tiny feature that barely works only in demo. with all vibe coding in the world today you still need at least 6 months full time to build a nice note taking app . If we are talking something more difficult - it will be years - or you will nee…

You seem to be making the assumption that "app" means "sellable product", rather than "one off that works for me". It doesn't. When everyone is able to make their own one off prototype in 30 minutes, no one will pay for the thing that took someone 6 months.

whatever you prototype - the one who built it in 6 month will have economy of scale to make it cheaper than your diy solution, and because they serve many customers and developed it for 6 months - their product will be 100x better than the one you diy

there is very very rare use case when diy makes sense. in 99% of cases its just a toy that feels nice as you kinda did it. but if you factor in the time etc it is always costs 100x more than $5/month you could usually buy

Post reply on HN