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

Vibe Coding and the Future of Software Engineering

alexp.pl

Post reply on HN
Print view View original

91–100 of 103 posts

Re: Vibe Coding and the Future of Software Engineering

#91

Post by linsomniac »

AlwaysRock wrote: post #87
linsomniac wrote: post #82

Earlier quoted context omitted.

AFAICT, OpenAI o3-mini-high, a couple days ago completely hallucinated functionality within systemd homectl that would mount a home directory from another machine using sshfs. It certainly wasn't available on Ubuntu 24.04, but searching the Internet I can't find those options documented anywhere. Though, I do agree that hallucinations have dropped dramatically.

I am not an expert in systemd homect but I have found that adding, "Show documentation for any methods or built in functions used" helps when I'm working on anything obscure or that is less likely to have a lot of publically availability code (that the LLM was likely to be trained on). That helps a lot whenever I am working off something I know will likely exist but just needs to be pulled from a company's documentat…

That did provide some more interesting results, seemingly getting closer to something that would actually work, but not quite. Perplexity, Claude, and ChatGPT all provided very different approaches. That addition to the prompt definitely did provide some useful additional information.

Re: Vibe Coding and the Future of Software Engineering

#92

Post by t-writescode »

Izkata wrote: post #69
t-writescode wrote: post #54

Earlier quoted context omitted.

"I wonder how many new developers will have legit panic attacks if: * Slack is down * StackOverflow is down * their default docs website is down * their IDE of choice is being buggy and so they have to use something without autocomplete Life gets harder when assistive tools are lost, no matter what the tool.

Harder yes for those, but the article is describing something that becomes impossible because there is no fallback, not just harder.

Yeah, after I saw what this person was doing, that's .... wow, that's a choice, given the current state of tools. They're far braver than I am.

Re: Vibe Coding and the Future of Software Engineering

#93

Post by gngoo »

namaria wrote: post #90
gngoo wrote: post #78

Earlier quoted context omitted.

I am getting paid significantly more than a year ago, but definitely not 4x as much. However, I have a lot more free time than I did before. And this while working on my own side projects as well; which are slowly growing into ramen-profitability. There are also other things to factor in, like living in South East Asia at a low cost of living and billing US and EU standard rates. > why are you doing this? Because I l…

Not why you build software man, why are you taking 3 jobs and foregoing receiving 3 salaries.

Because they are willing to pay my asking rate. Maybe it’s 3 jobs, but for me it’s still one. I can’t help that their 3 other devs aren’t as productive. I’m not here to defend them either. Absolutely quite some companies are going this route, it’s not a unique situation either. What should I do? Not adapt and complain about the job market? Using AI -IDEs since day one, I also see the writings on the wall, so I’m also taking advantage of these things (like anyone should).

Re: Vibe Coding and the Future of Software Engineering

#94

Post by re-thc »

sergiotapia wrote: post #81
re-thc wrote: post #55

Earlier quoted context omitted.

> these gains are compounding. It's not really. You could have done the same using no code tools in a similar time. Question is, would you? It's alarming the amount of trust/praise that goes into "AI". > if you're an experienced engineer > it took me 5 minutes with AI You'd at least read the code and fix things up so it wouldn't be 5 minutes.

this is a cope my friend. adapt or die.

> this is a cope my friend. adapt or die.

Adapt to? I'm not saying to not use AI but whether you use AI, do it manually or outsource it it's never 5 minutes. It's about being responsible. Double check what happens. Review it.

Re: Vibe Coding and the Future of Software Engineering

#95

Post by dkkergoog »

Karrot_Kream wrote: post #6

If you're writing one-off scripts though, I find vibe coding fantastic. I found myself in a work meeting where I was mostly there to let a junior present some joint work we did and answer any questions the junior couldn't. Since I wasn't really needed (the junior eng was awesome), I was fidgeting and wanted to analyze the results from an API I had access to. A few prompts from Claude and I was hitting the API, fetchi…

[dead]

Re: Vibe Coding and the Future of Software Engineering

#96

Post by makeitdouble »

mohsen1 wrote: post #71
makeitdouble wrote: post #38

Earlier quoted context omitted.

Compartmentizing the code only matters if it works in the first place. The main argument from senior folks is probably that vibe codes won't cut it for actual sizeable problem. There is complexity that can't be abstracted away just because we want to.

I think we're overestimating how much humans can keep in context. Throughout my career I've seen many instances that folks completely get it wrong and miss the context.

You're right, but it's also why vibe coding doesn't work IMHO.

We had the same situation with TDD: can we give out succinct specs and ignore what happens in the code if the specs are met ? For anything beside Hello world, the answer was no, absolutely not.

It still mattered that the logic was somewhat reasonable and you were not building a Rube Goldberg machine giving the right answers to the given tests 95% of the time. Especially as the tests didn't cover all the valid input/output nor all the possible error cases in the problem space.

It's because there's a lot happening that we need to have simple blocks that we can trust and not black boxes that were already beyond our understanding.

Re: Vibe Coding and the Future of Software Engineering

#97

Post by namaria »

gngoo wrote: post #93
namaria wrote: post #90

Earlier quoted context omitted.

Not why you build software man, why are you taking 3 jobs and foregoing receiving 3 salaries.

Because they are willing to pay my asking rate. Maybe it’s 3 jobs, but for me it’s still one. I can’t help that their 3 other devs aren’t as productive. I’m not here to defend them either. Absolutely quite some companies are going this route, it’s not a unique situation either. What should I do? Not adapt and complain about the job market? Using AI -IDEs since day one, I also see the writings on the wall, so I’m also…

You're absolutely right. The rational thing for you to do is to enable further exploitation of your own class and hand over the extra profit on a silver plate to others.

Re: Vibe Coding and the Future of Software Engineering

#98

Post by dakshbabbar »

CyberDildonics wrote: post #89
cadamsdotcom wrote: post #83

Vibe coding will eat software. Engineering - working to constraints, including user needs (ie Product Management) is forever.

This vague meaningless term that some blogger just made up based on how teenagers talk will "eat software" ?

Karpathy is just 'some blogger' who talks in teenage English, sure.

Re: Vibe Coding and the Future of Software Engineering

#99

Post by gngoo »

namaria wrote: post #97
gngoo wrote: post #93

Earlier quoted context omitted.

Because they are willing to pay my asking rate. Maybe it’s 3 jobs, but for me it’s still one. I can’t help that their 3 other devs aren’t as productive. I’m not here to defend them either. Absolutely quite some companies are going this route, it’s not a unique situation either. What should I do? Not adapt and complain about the job market? Using AI -IDEs since day one, I also see the writings on the wall, so I’m also…

You're absolutely right. The rational thing for you to do is to enable further exploitation of your own class and hand over the extra profit on a silver plate to others.

Either you adapt, or you don't. But this is what's coming for all software/web & IT jobs. I am not making up the rules of the game; neither am I sitting here and be bitter about it.

Re: Vibe Coding and the Future of Software Engineering

#100

Post by CyberDildonics »

dakshbabbar wrote: post #98
CyberDildonics wrote: post #89

Earlier quoted context omitted.

This vague meaningless term that some blogger just made up based on how teenagers talk will "eat software" ?

Karpathy is just 'some blogger' who talks in teenage English, sure.

The results speak for themselves. Here is clickbait trying to coin a nonsense word and you aren't defending it on substance, just on the fact that you recognize the name of the person who wrote it.

The most embarrassing part is everyone immediately going along with it. It is like an improv game or a man on the street interview where they ask a pedestrian about an event that didn't happen and the person being interviewed just acts like they were there and know all about it.

Post reply on HN