News for hackers. Stuff that matters.
Re:The problem with "vibe coding" by rvz on Tuesday April 15, 2025 @12:11AM (#43688906)
‘Vibe coding’ isn’t software engineering.

It throws away decades of software engineering principles in favour of unchecked AI output by clicking “accept all” on the output.

You would certainly NOT use ‘vibe coded’ slopware that powers key control systems in critical infrastructure such as energy, banking, hospitals and communications.

The ones pushing “vibe coding” are the same ones who are all invested in the AI companies that power it.

An incident involving using ‘vibe coded’ slopware is just waiting to happen.

Re:The problem with "vibe coding" by mc3301 on Tuesday April 15, 2025 @01:42AM (#43689326)
It's like building a decorative bridge over a decorative pond in your backyard out of scrap wood versus building an actual bridge for public traffic.
Re:The problem with "vibe coding" by aglione on Tuesday April 15, 2025 @02:01AM (#43689441)
fun fact: nobody would never accept vibe coding software level for a 200$/month vibe coding software tools
Re:The problem with "vibe coding" by NitpickLawyer on Tuesday April 15, 2025 @02:12AM (#43689506)
‘OUTSOURCING’ isn’t software engineering. It throws away decades of software engineering principles in favour of CHEAP output by clicking “I AGREE” on a contract.

You would certainly NOT use ‘OUTSOURCED’ slopware that powers key control systems in critical infrastructure such as energy, banking, hospitals and communications systems.

An incident involving using ‘OUTSOURCED’ slopware is just waiting to happen.

... oh, wait...

Re:The problem with "vibe coding" by danparsonson on Tuesday April 15, 2025 @02:15AM (#43689524)
I mean that's not a great counterexample because outsourcing is famously difficult to get right, and from my own experience often results in exactly the kind of terrible code quality GP is talking about.
Re:The problem with "vibe coding" by NitpickLawyer on Tuesday April 15, 2025 @02:21AM (#43689568)
My point was that a blanket generalisation is bad because it's a blanket generalisation, the details are unimportant.

Yes, outsourcing is famously difficult to get right, and yet we've been doing it in every industry for decades now. And the famous examples become famous when something fails (boeing et. all) but there are also success stories out there. The trick, as always, is in the implementation.

My other point was that every "new thing" gets the same treatment. It doesn't work. Oh, it works but on toy problems. Well, it works on some complicated problems, but it's expensive. Ok, it works on a variety of problems, it's cheap, but it's unmaintainable. And so on, and so forth.

Re:The problem with "vibe coding" by pjmlp on Tuesday April 15, 2025 @07:39AM (#43691385)
I am yet to be part of any outsourcing project that was actually a sucess story, where everyone came unarmed without battlefield scars, in a timeframe of the last 25 years that outsourcing started to be a common thing in enterprise consulting.