Live data from Hacker News

“Vibe Coding” vs. Reality

cendyne.dev

151–160 of 312 posts

Re: “Vibe Coding” vs. Reality

#151

Earlier quoted context omitted.

Now, now, not with this mindset. You have to ask the Ai to fix the mess, and if it doesn't, try again!

As if the person struggling with the mess will have the requisite skill levels to even recognise a mess!

Ooh but don't you know we just need an extra language with abstractions that can be compiled into prompting statements. Maybe something like sql.

Re: “Vibe Coding” vs. Reality

#152

At this point in time, we're following the time corporate got on the outsourcing craze step for step. It had all the hype, hands off, cheaper for the same work, faster to market, every other argument you've all certainly heard. Then the reality hit. The whole discussion around LLM coding agents feels indistinguishable.

> It had all the hype, hands off, cheaper for the same work, faster to market, every other argument you've all certainly heard. Like some of the other responses, I'm baffled by your comment. Have you not seen what's happened in the past 5 years or so? Yes, there was an outsourcing craze to India after the .com bubble burst in the early 00s that largely failed - the timezone, cultural differences, and lack of good inf…

I think you're talking about a different phenomenon, having remote mixed teams is IMHO different from offshoring.

There's at least the crucial difference that you had devs in both western countries and traditional "third world", where the 90s view of offshoring was throwing whole processes abroad and only keep "heads" in-house while the remote teams/companies would deal with all the execution, making it inherently difficult to deal with production monitoring.

PS: to your point offshoring to India has become more common but Indian companies are also not that cheap, so we're past the initial framework. Perhaps the same way outsourcing production to China used to be about sweatshops, when it can now be about unrivaled expertise at a cost.

Re: “Vibe Coding” vs. Reality

#153
post #3

Vibe Coding is a trigger word for devs who insist it's a pointless exercise because it doesn't do 100% of the job. Devs don't seem to realize that's not the point - the point is you can hire less devs if you're only worried about the remaining 20%. Also this article is immensely distracting.

The problem is it's more work to figure out which 20% it did subtly wrong, than it is to just do things right in the first place. https://twitter.com/leojr94_/status/1901560276488511759 https://twitter.com/leojr94_/status/1902537756674318347 Good thing this guy wasn't in charge of an actual business, because if he was it would have been killed overnight.

[deleted]

Re: “Vibe Coding” vs. Reality

#154

I'll share a new wrinkle that casts more shade on the coding LLMs. We have a fair number of offshore resources that are used for dev. They developers are fully integrated into the team, are in all the stand-ups, and substitute for the usual role of junior programmers. They don't get the grunt-work shoveled on them, they get the same work as everyone else, they're just expected to not be as fast. In 6 months 2 out of…

BTW, Copilot is not the best at coding. With the quality LLM return exponentially grows. Bigger chunks, fewer bugs, less time checking. From my experience LLMs do not impress on complex algorithms and shine on small utilities. They can use libs I even don't want to learn about.

Re: “Vibe Coding” vs. Reality

#155
post #34

I hate how what is effectively a stupid meme phrase became an actual term in a few days. > "Vibe Coding" might get you 80% the way to a functioning concept. But to produce something reliable, secure, and worth spending money on, you’ll need experienced humans to do the hard work not possible with today’s models. The problem is that 80% of the job is a proof of concept at best. 80% is effectively a QA walking into a b…

80% mark means you just finished the happy flow and written 30% of the code bases. Now you need to handle the unhappy parts and need to write extra test code for covering all those edge cases.

Re: “Vibe Coding” vs. Reality

#156
post #41

Earlier quoted context omitted.

Open mind here. Spill more details please. We're the 9 good or was their dead weight. Could the 9 to 2 have been done without AI anyway (because less work to do).

They were good... probably a bit bloated. Without AI we could probably be 5 devs. With AI we can do it all in 1-2.

Trying to get my head around this. It must mean 90% of what they were doing was writing code. Like not even thinking, architecture, gathering requirements, make sure you built the right thing etc. Just generating syntax.

Re: “Vibe Coding” vs. Reality

#157
post #133

Earlier quoted context omitted.

Where we are now, I wonder if is similar to the early days of compiled languages existing, back when people still somewhat commonly wrote assembly by hand and didn't trust compilers. Sure, things like Roller Coaster Tycoon exist, but but writing in a compiled language is so much faster, easier, and more broadly accessible than writing in assembly that compilers took over.

My worry about this approach is: there is a reasonably popular saying that writing code is hard but debugging it is twice as hard (at least), which I think is an accurate description. LLMs will greatly increase code production, will they also increase debuggability to match?

LLMs don't just make it easy to accumulate code - they make it easy to throw code away and start again. This already enables taking a different approach to debuggability - if there's a bug and it can't be trivially solved, trash that bit of the code and write it again. It may not be broadly viable just yet, but it will be if the models keep getting cheaper and better.

This is also implied in the idea of "vibe coding" - don't bother understanding the code or debugging it yourself; if it doesn't work the way you like, just say it and have the model fix it until it gets it right (or you run out of money).

Re: “Vibe Coding” vs. Reality

#158

This is the go community saying a computer will never best human go players. We already have examples of a model finding more performant sorts [0], given the right incentives and time, and the right system for optimizing (LLMs trained on “average code” probably aren’t it) the computer will best us at creating things for the computer. Is “vibe coding” real today? Not in my experience, with even Claude code. My hand ha…

Vibe coding is 100% real. Or maybe we should call it code vibing when there is no coding ability. But I just taught 18 professionals with no coding ability to build functional software. Their minds were blown

If its something like "tic-tac-toe in Javascript", thats been done 1000x before, I wouldn't find it all that impressive.

Re: “Vibe Coding” vs. Reality

#159
post #100

> Cursor has some sort of "concise mode" (archived) that they'll turn on when there is high load where the model will still be rated at the normal price but behaves in a useless manner. This mode will omit details, drop important findings, and corrupt the output that is being produced. This is a real problem that I have experienced on and off. It's getting to the point where everyone on my team is actively looking fo…

> Generally, I've found Cursor works correctly after business hours. Interestingly the times I've experienced the most weirdness were during extremely not normal business hours (from the California perspective). For 3 nights in a row last week, I found myself coding at/after 2:30am during what were apparently periods of excessive load on Claude Sonnet. When asking Cursor to do things, it would fail, tell me about the…

> during extremely not normal business hours (from the California perspective). For 3 nights in a row last week, I found myself coding at/after 2:30am

That's morning business hours in Europe and afternoon in Asia.

Re: “Vibe Coding” vs. Reality

#160
post #139

Earlier quoted context omitted.

Vibe coding is 100% real. Or maybe we should call it code vibing when there is no coding ability. But I just taught 18 professionals with no coding ability to build functional software. Their minds were blown

Cursor? I finally got around to trying it this week and it exceeded my expectations.

No, if you have no coding ability and no interest in learning but want to just tell the computer what you want:

1. Lovable

2. Bolt.new

3. Replit agent

Or actually, I’d put Claude #1. You can make all kinds of cool stuff, just in their UI.

Post reply on HN