Live data from Hacker News

Vibe code is legacy code

blog.val.town

181–190 of 473 posts

Re: Vibe code is legacy code

#181
post #4

I think you are not going far enough though: All code is legacy code. So vibe coding's ability to make writing more code faster isn't special because it's code nobody understands: Your hand-rolled code is also bad. Once you embrace the fact that all the code is legacy, then it's clear how writing more code, faster cannot be helpful from a maintenance POV: You are just creating more work for yourself. And no, librarie…

That's not what legacy means. Legacy means the people who understood it are gone and you're left with code that's hard to maintain because it's hard to understand because the people who understood it are gone.

I find this a bit like saying that we can't understand East of Eden because Steinbeck is dead.

Re: Vibe code is legacy code

#182
I’ll never cease to be amazed about this industry. Programming for the web is a thing, sure. I’ve made a small fortune having never written a single line of JavaScript.

The ecosystem is bigger than the internet.

Re: Vibe code is legacy code

#183

Earlier quoted context omitted.

Yeah I think its over, it will take a while for the effects to ripple through society, but writing code will be seen as something like wood working

I'm more curious how society will look when half the population is living in tents.

what a time to be alive!

Re: Vibe code is legacy code

#184

Earlier quoted context omitted.

I don't see how any of that implies that an incumbent did it.

If you were a criminal trolling the Internet for vulnerable servers and found stripe keys... would your first instinct be to refund customers rather than do some other sort of crime? Like what's the motivation you envision here?

[dead]

Re: Vibe code is legacy code

#185

Earlier quoted context omitted.

The fact your friend is suffering no consequences and is able to just carry on is exactly what is wrong with this industry. In a perfect world the creation of software would have been locked down like other engineering fields, with developers and companies suffering legal consequences for exposing customer information.

People really want to bring down the growth of the USA's software industry to EU level.

> People really want to bring down the growth of the USA's software industry to EU level.

The EU is the only place hiring software engineers right now. Everyone in the U.S. just keeps laying them off.

Re: Vibe code is legacy code

#186

A story about a non-technical friend: friend vibe coded a SaaS last year and started generating revenue with almost no marketing; all word of mouth and inbound in a niche industry. Used Replit and Supabase to build the thing; I am still really impressed by what he was able to do given how complex the app ended up becoming as he interacted with customers. What I think happened: there are two incumbents in this space t…

> Was it worth it? Yes, it is terrible, shoddy, insecure code, but he proved out a viable business with just a few hundred dollars of investment.

and the vital ingredient? complete contempt for his customers

Re: Vibe code is legacy code

#187

Earlier quoted context omitted.

> Was it worth it? Yes, it is terrible, shoddy, insecure code, but he proved out a viable business with just a few hundred dollars of investment. This feels like less of a win for the customers though. They're paying money and exposing their data insecurely, all for a product that maybe does what it's trying to do. > Now he's hiring a developer to shore it up. This is going to be way harder than it sounds... I'm all…

It's a win for the customers. From what he's told me, there's zero churn so far despite the hacks ( including one where the hacker emailed every customer about the hack ). It's because the software is that much of an improvement over the incumbents at a fraction of the cost. Better features, more flexible, easier to use, faster, etc. Everything about it is better than the two major vendors. The rebuild will likely en…

> The rebuild will likely end up easier, IMO, because the screens and the logic is all done. Most of it just has to be moved to strict backend and then have the APIs secured correctly.

How to draw an owl…

Step 1. Draw a circle. Step 2. Draw the rest of the owl…

Re: Vibe code is legacy code

#188

Earlier quoted context omitted.

Will his customers trust him a second time though?

They trusted him more after he got hacked. He actually got more signups from inbound.

> ZUCK: people just submitted it

> ZUCK: i don’t know why

> ZUCK: they “trust me”

> ZUCK: dumb fucks

Re: Vibe code is legacy code

#189
post #61

Don't you think the next step is a programming language that isn't even meant to be human readable? What's the point of using an LLM to generate python or Swift or whatever? The output of the LLM should be something that runs and does whatever it's been asked to do... why should the implementation be some programming language that was designed for humans to grok? Once that's true the idea of it being maintainable bec…

Yeah it does seem like a game of telephone to train LLMs on code optimized for human cognition, then have them create behavior by parrotting that code back into a compiler. Could they just create behavior directly?
Post reply on HN