Don’t do what? Warn the users?
My predextion for the EU :
Apple will show the warning and increase the share you have to pay for AI apps...
Google will hide the apps
Sweeney will sue both
@nixCraft
Things will get interesting when AI companies are held liable for the shoddy work of their products. Kind of similar to the question of liability with self driving cars.
AI in its current form is not economically viable in the long term.
@womble
Nobody wants to take responsibility for fucking up. So someone will sue someone else.
That may end in the producers or users being held liable. Or it might end in a change of law. Or it will be the end customers' problem. But no matter what, the cost will become visible and be factored into purchase decisions.
That makes me believe that there is a reasonable chance that poor quality LLM output will have consequences either from the courts or from the market.
@womble But is the situation still the same? Up till now software was a tool and responsibility on how to use it was yours. If you bought the wrong tool that was on you. Now you could argue that you bought a machine that produces something. But the products are defective due to the design of the machine.
I do not not disagree with you. I just think that the discussion we are having here will also happen on a larger scale and - hopefully - have consequences.
@nixCraft vibe coding = shitehawks with no respect for expertise wanting to make money from a skill they haven’t taken the time to learn and thinking “how hard can it be?”
As it happens, quite hard, and hopefully they get sued even harder
@nixCraft AI is like asbestos. Put it in everything, damage people, first ignore that for a long time, then spend decades to safely remove.
*edit: now this post gets boosted so much I feel obliged to say my 13y old son came up with the analogy some time ago. But I do really agree.
@nixCraft I'm a consultant/freelancer and within the past like 3 to 4 months I've been getting contacted by a lot of places to essentially fix "vibe coder" slop. The closest thing I can compare it to is when several years ago companies were offshoring work to India and months to years later they need people to also come in and fix things that they offshored. History repeats itself.
The tech debt from what I'm seeing right now is massive. insanely massive. There's no refactoring here - this is "we need to rebuild from the ground up cause all this AI slop can't scale" Like I said most of my requests now are to essentially be a digital janitor for vibe coders so much so I'm having to now reference other devs I know to these places.
Honestly if you freelance as a dev be it front end, back end, software, whatever SERIOUSLY start advertising on linkedin or where ever saying you can clean this shit up. there are SO many places that need rescuing but are way to embarrassed to publicly admit they need saving from vibe coding. Just make a post on Linkedin and I guarantee you messages will start flooding in.
@Okuna @nixCraft yup, I remember those days well. The problem is now no one is doing quality checks on anything a vibe coder prompt monkey spits out. the "vibe coder" is the one that is supposed to be doing the checks and they're not. OR they "are" but they just don't have a clue what they're checking because they don't know it.
They can write a decent prompt, but they just hit tab and hope the AI knows what it's doing. The problem is the AI simply needs to provide a solution. doesn't matter if it's correct or not just as long as it provides something.
As an example looking over diff's of one place i'm currently consulting for they were "tabbing" on things that were simply removing a couple words from a comment and the AI would call that "a fix". the "dev" or vibe coder would then push this to production. Literally one commit had a diff of "-- //this is" and it got PUSHED with the commit message of "fix for such and such function" IT WAS THE REMOVAL OF TWO WORDS FROM A COMMENT!
@rozodru @nixCraft Nice advise! I have been cleaning code written by a junior dev using LLM. It is worse than if he had written it by himself.
I think I am going to start advertising trainings on how to develop without AI. There will be a huge need of developers that will need to learn to write software by themselves.
@RosaCtrl @rozodru @nixCraft I worry that this won't be quite as fun. I really enjoy inheriting a code base that's "bad" because the developers were rushed or inexperienced. These code bases are still planned out - even if the plan was flawed, even if it wasn't always followed, even if there was more than one competing for supremacy.
Vibe coding is not that. There is no plan.
@NicolasRinaudo @rozodru @nixCraft yeah, but if things are that bad, I feel actual engineers will have leverage.
But honestly I’m more worried about the effect these things will have on the field once the delusion of vibe coding fades away. I’ve never been forced to use and specific IDE, for example, but I can imagine being forced to use agents on the hopes I’ll become faster, and that’s what makes more anxious
@parsingphase @nixCraft
This is what I was going to ask.
And does vibe coding now include the privacy settings for a database in production? Because "coding" and production deployments are two different things.
@nixCraft Also cf:
An anonymous reader quotes a report from Ars Technica: Two recent incidents involving AI coding assistants put a spotlight on risks in the emerging field of "vibe coding" -- using natural language to generate and execute code through AI models without paying close attention to how the code works und...