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
The 100 hour gap between a vibecoded prototype and a working product
21–30 of 362 posts
Re: The 100 hour gap between a vibecoded prototype and a working product
#22Re: The 100 hour gap between a vibecoded prototype and a working product
#23Also 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
#24If 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
#25Re: The 100 hour gap between a vibecoded prototype and a working product
#26With 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.
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.
Re: The 100 hour gap between a vibecoded prototype and a working product
#28If 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
#29Re: 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.
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