logoalt Hacker News

sfjailbirdtoday at 10:44 AM3 repliesview on HN

We already have the business side come with requirements in the form of 'solutions' that they have thought up, which more often than not are Rube Golberg-esque contraptions, that you have to conversationally reverse engineer to arrive at the actual requirements.

In the future they will come with their 'ready' solution, already 'working' and be even less receptive to look at design and architecture holistically. Just make it like that. And why do you need to spend X man hours? The thing is basically already done!


Replies

gwerbintoday at 11:10 AM

I have seen this already. Vibecoded top to bottom.

The downside is that the business people don't understand why you can't just put their app in production as is. And then there's a lot of pressure to make it happen quickly "because we can use AI to move fast". This is going to come down to healthy organization dynamics, and hopefully represents a learning opportunity for leadership.

The upside is that the idea has already been proven out much more thoroughly than a sketch on a napkin. Claude has already prompted them about edge cases and design decisions. It's very likely that at some point they had to explicitly tell Claude "don't worry about that and just make an assumption", or "I actually don't like that interaction after trying it a few times, can you do a differently". They had to write out much of their idea in clear and direct language in order to prompt the AI. They've probably been playing with their own toy because it's fun to play with toys you summoned from thin air, so they've had a chance to discover the experience and refine their own preferences.

It's probably a net negative right now because the "ship it what's the problem team" pressure is intense and stupid and demoralizing and miserable to work under. But I think it will stabilize and it might be a net positive in future projects.

show 4 replies
frde_metoday at 12:05 PM

I honestly much prefer this to the old way where the only mode of communication was speech or text. I now often understand a lot more holistically what the person coming with their product wants with just a demo + a conversation.

Of course you need the person making that vibe product to understand it's just a mockup of their idea and that it'll change. But I would argue this has always been a necessary quality for a product person.

show 1 reply
ex-aws-dudetoday at 12:03 PM

I’ve seen that play out already as well

Then your job as SE just becomes reviewing and untangling vibe-coded stuff