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

Vibe code is legacy code

blog.val.town

Post reply on HN
Print view View original

451–460 of 473 posts

Re: Vibe code is legacy code

#451

Post by [deleted] »

doesnt_know wrote: post #119
CharlieDigital wrote: post #67

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…

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.

[deleted]

Re: Vibe code is legacy code

#452

Post by 1718627440 »

encom wrote: post #404
1718627440 wrote: post #397

Earlier quoted context omitted.

I'm surprised there is no root there? In my experience this is by far the most common.

I'm almost certain SSH does not allow root login by default.

Yes, and it is disabled on my servers and I'm glad for this, because it still seams to be the most common in my logs.

Re: Vibe code is legacy code

#453

Post by chromanoid »

pydry wrote: post #382
zerkten wrote: post #248

Earlier quoted context omitted.

>> It was crazy just how fast it was exploited. People underestimate the speed, but also the number of pivots that advanced attackers will make. Sure, these kinds of problems are easy to exploit, but with major organizations that employ reasonable defenses, the attackers will pivot through 50+ exploits/machines/layers to get to the target(s). This can take place over weeks or months.

It still doesn't make sense that advanced attackers would go to those lengths in order to... refund the customers.

Vibe hacking is much older than vibe coding.

Re: Vibe code is legacy code

#454

Post by ozgrakkurt »

mr_donk wrote: 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…

Building complex things requires deterministic, reliable and understandable abstraction.

Don’t see where current AI fits in this except being a better intellisense for an IDE.

Re: Vibe code is legacy code

#455

Post by [deleted] »

ChrisMarshallNY wrote: post #77
stevekrouse wrote: post #36

Earlier quoted context omitted.

Vibe coding is allowing everyone (including me!) to make way more apps in my personal life that are very throwaway. I think some folks are doing this in business contexts too. But this is a real game-changer for non-technical folks

Yes and no. If you ship, and charge money for it, you are responsible for maintaining it. Can’t treat it as throwaway, even if you meant it as such.

[deleted]

Re: Vibe code is legacy code

#456

Post by bulginess2173 »

ChrisMarshallNY wrote: post #77
stevekrouse wrote: post #36

Earlier quoted context omitted.

Vibe coding is allowing everyone (including me!) to make way more apps in my personal life that are very throwaway. I think some folks are doing this in business contexts too. But this is a real game-changer for non-technical folks

Yes and no. If you ship, and charge money for it, you are responsible for maintaining it. Can’t treat it as throwaway, even if you meant it as such.

Unfortunately this is common, especially if something is dev facing. Whenever I have to talk to devs from card processors, video services, etc. They seem more confused that their app is broken than anything else.

Re: Vibe code is legacy code

#457

Post by sunnybeetroot »

user3939382 wrote: post #47

When you have 100+ tables and 100k+ loc you’re incapable of the context needed to write features without bugs which is why we have tests. LLMs are capable of like 5% of the context you are: Full context > human context capacity > LLM context capacity. We should all be able to agree on this and it should settle the debates around the efficacy of vibe coding.

We’ve gone from tiny context windows to 1 million tokens in a couple of years. At this rate LLMs will exceed human context and grow to have full context.

Re: Vibe code is legacy code

#458

Post by sysmax »

throawaywpg wrote: post #444
sysmax wrote: post #438

Earlier quoted context omitted.

Most of the AI hiccups come from the sequential nature of generating responses. It gets to a spot where adhering to code structure means token X, and fulfilling some common sense requirement means token Y, so it picks X and the rest of the reply is screwed. You can get way better results with incremental refinement. Refine brief prompt into detailed description. Refine description into requirements. Refine requiremen…

hello, im interested in the GUI options you mentioned!

Cool. The part that is released already is described here [0]. You can point at some code and give brief instructions, and it will ask the model to expand them, giving several options.

E.g. if you point at a vector class and just "Distance()" for prompt, it will make assumptions like "you want to add a function calculating distance from (0,0)", "function calculating distance between 2 vectors", etc. It runs pretty fast with models like LLaMA, so you can get small routine edits done much faster than by hand.

The part I am currently experimenting with are one-click commands like "expand" or "I don't like the selected part. Give me other options for it". I think, I'll get it to a mostly usable state around Monday. Feel free to shoot an email to the address in the contact page and I'll send you a link to the experimental build.

[0] https://sysprogs.com/CodeVROOM/documentation/concepts/planni...

Re: Vibe code is legacy code

#460

Post by justanotherunit »

I actually foreshadowed this about 6 months ago when Lovable was starting to gain heat here in Sweden. It was quite obvious that for a start and prototype, these kind of applications are good. But if you are going full SaaS, hire an engineer to set the app in stone.

This might be a new branch of software developers on the rise. Those that take sloppy AI code and turn them into real applications for customers.

Post reply on HN