Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

kanfa.macbudkowski.com

Post reply on HN
Print view View original

141–150 of 362 posts

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

#141

Post by wierdbytes »

ryandrake wrote: post #110
Aurornis wrote: post #98

Earlier quoted context omitted.

There’s a big gap between reality and the influencer posts about LLMs. I agree with you that LLMs do provide some significant acceleration, but the influencers have tried to exaggerate this into unbelievable numbers. Even non-influencers are trying to exaggerate their LLM skills as a way to get hired or raise their status on LinkedIn. I rarely read the LinkedIn social feed but when I check mine it’s now filled with c…

> 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…

> Where are all of the actual shipping vibecoded products that millions of users are using?

Claude Code and OpenClaw - they are vibecoded. And I believe more coming.

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

#142

Post by spacecadet »

qsera wrote: post #128
spacecadet wrote: post #123

Im an 20 year veteran of application development consulting. Contributor level... not talking head. I do more estimating than anyone you likely know. Consulting is cooked. I just AI native built (not vibe coding...) an application with a buddy, another Principal level engineer and what would cost a client 500-750k and 8-12 weeks, we did for $200 and 1 sprint. Its a passion project but highly complex mapping and navig…

>highly complex mapping Curious. Can you elaborate on this a bit?

Do you have a race car or race team? Happy to onboard you, otherwise, not here.

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

#144

Post by spacecadet »

spacecadet wrote: post #123

Im an 20 year veteran of application development consulting. Contributor level... not talking head. I do more estimating than anyone you likely know. Consulting is cooked. I just AI native built (not vibe coding...) an application with a buddy, another Principal level engineer and what would cost a client 500-750k and 8-12 weeks, we did for $200 and 1 sprint. Its a passion project but highly complex mapping and navig…

I realize this sounds one sided. Ive also founded companies and worked across the range of startup to faang. Everything has changed... For the better if you ask me.

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

#145

Post by WarmWash »

qsera wrote: post #108
WarmWash wrote: post #74

Earlier quoted context omitted.

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".

>most software used is created by the user You really believe that?

Yes, because the current software paradigm (a shed/barn/warehouse full of tools to suite every possible users every possible need) doesn't make sense when LLMs can turn plain English into a software tool in the matter of minutes.

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

#146

Post by benwaffle »

hmmmmmmmmmmmmmm wrote: post #16
risyachka wrote: post #2

>> 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.

obsidian isn't open source

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

#147

Post by WarmWash »

nly wrote: post #116
WarmWash wrote: post #74

Earlier quoted context omitted.

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".

Wont happen. The average user just has no interest in building things.

Which is why they will use AI to do the building...

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

#148

Post by atomicnumber3 »

nly wrote: post #111
FpUser wrote: post #70

Earlier quoted context omitted.

I am curious about what causes some to choose Java for HFT. From what I remember the amount of virgin sacrifices and dances with the wolves one must do to approach native speed in this particular area is just way too much of development time overhead.

"HFT" means different things to different people. I've worked at places where ~5us was considered the fast path and tails were acceptable. In my current role it's less than a microsecond packet in, packet out (excluding time to cross the bus to the NIC). But arguably it's not true HFT today unless you're using FPGA or ASIC somewhere in your stack.

The one person who understands HFT yeah. "True" HFT is FPGA now and also those trades are basically dead because nobody has such stupid order execution anymore, either via getting better themselves or by using former HFTs (Virtu) new order execution services.

So yeah there's really no HFT anymore, it's just order execution, and some algo trades want more or less latency which merits varying levels of technical squeezing latency out of systems.

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

#149

Post by youknownothing »

I'm having somewhat good experiences with AI but I think that's because I'm only half-adopting it: instead of the full agentic / Ralphing / the-AI-can-do-anything way, I still do work in very small increments and review each commit. I'm not as fast as others, but I can catch issues earlier. I also can see when code is becoming a mess and stop to fix things. I mean, I don't fix them manually, I point Claude at the messy code and ask it to refactor it appropriately, but I do keep an eye to make sure Claude doesn't stray off course.

Honestly, seeing all the dumb code that it produces, calling this thing "intelligent" is rather generous...

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

#150

Post by [deleted] »

paganel wrote: post #136
Aurornis wrote: post #98

Earlier quoted context omitted.

There’s a big gap between reality and the influencer posts about LLMs. I agree with you that LLMs do provide some significant acceleration, but the influencers have tried to exaggerate this into unbelievable numbers. Even non-influencers are trying to exaggerate their LLM skills as a way to get hired or raise their status on LinkedIn. I rarely read the LinkedIn social feed but when I check mine it’s now filled with c…

The “store on the chain” thing turned out to be a fad in terms of technology, even though it made a lot of money (in the billions and more) to some people via the crypto thing. That was less than 10 years ago, so many of us do remember the similarities of the discourse being made then to what’s happening now. With all that said, today’s LLMs do seem so provide a little bit more value compared to the bit chain thing,…

[deleted]
Post reply on HN