this post was submitted on 06 May 2025
706 points (97.8% liked)

Fuck AI

2635 readers
1534 users here now

"We did it, Patrick! We made a technological breakthrough!"

A place for all those who loathe AI to discuss things, post articles, and ridicule the AI hype. Proud supporter of working people. And proud booer of SXSW 2024.

founded 1 year ago
MODERATORS
706
skills for rent (lemmy.blahaj.zone)
submitted 16 hours ago* (last edited 7 hours ago) by not_IO@lemmy.blahaj.zone to c/fuck_ai@lemmy.world
 
top 50 comments
sorted by: hot top controversial new old
[–] forrcaho@lemmy.world 19 points 3 hours ago (2 children)

Having been a coder for decades before AI came on the scene, I don't understand how inexperienced programmers could possibly write a serious amount of working code with AI.

It's wrong, like, at least half the time, but as an experienced coder, I can look at the "code" it generated and know what it was trying to do, and then write it correctly. I do find AI useful when I'm not sure how to go about solving a particular code-related issue, but ... it just gives me something to think about, not an answer I can use directly.

[–] Taleya@aussie.zone 1 points 54 minutes ago

I tried using chatgpt to write a basic batch file, it ended up such a horrendous mess that i gave up halfway through. Fucker got told four times, still kept putting the REM on the same line as actual code.

[–] geekgrrl0@lemmy.ca 7 points 2 hours ago (1 children)

It's like google-coding in 2010; nothing you search for is exactly what you need, but it could help you see why your code isn't working.

[–] iarigby@lemmy.world 3 points 2 hours ago (2 children)

I really don’t dig that comparison. When you look up a snippet on stackoverflow, for example, you can immediately see the quality of the answer, as well as feedback from real people

[–] grrgyle@slrpnk.net 2 points 1 hour ago* (last edited 1 hour ago)

Yeah like if you start coming across snippets that aren't even properly indented, you know you're digging the real bottom of the barrel (been there while struggling to fix email templating I know nothing about back in the day). Now, the code you get from the LLM looks totally legit to the untrained eye, and it may even generate a convincing explanation.

But you won't have any indication when it's dead wrong until you try to run it. And even then, it may be "working" in a way unintended because you don't actually understand what you copy+pasted, because neither does the LLM ofc.

I can't even imagine the spaghetti bowl you can get yourself into if you just keep vibe coding yourself deeper and deeper, while understanding nothing.

[–] geekgrrl0@lemmy.ca 2 points 1 hour ago

You can see the quality if you're an experienced coder. My comment lacks personal context in that I was in school in 2010 and there were plenty of my classmates who would plug snippets into their projects without fundamentally understanding what it did or learning what the project was supposed to teach us. Similar to a shortcut with AI in 2025.

[–] merc@sh.itjust.works 2 points 2 hours ago (1 children)

It's not possible to make you unskilled if you're skilled. At worst, you'd get rusty. It is possible that your skills might not be in high demand anymore though.

The only thing that would make programmers not be in demand is if "vibe coding" were truly producing a better product than traditional programming. So far, the only ones making that claim are the ones desperately trying to sell "AI" before the bubble bursts. It's true that there are some companies that really want to believe it. But, companies are always desperately hoping for something that can allow them to fire their expensive workers. It's rare that that works out.

[–] Evotech@lemmy.world 2 points 1 hour ago (1 children)

You are thinking to short term

This is not about you, but the next generations

[–] merc@sh.itjust.works 1 points 1 hour ago

In that case it's not talking about "deskilling", it's about "not skilling in the first place".

But, those are completely different things. I was never skilled in riding horses, the way I assume my great grandparents were. I didn't learn how to use a sliderule like my grandfather did. But, I still learned skills that were valuable for the moment in history where I grew up. There's never any guarantee that a baby born today will get to the age of 20 with skills that are useful enough that someone will pay them to use those skills.

As for programming, it isn't some kind of nefarious goal to make sure that tomorrow's children won't know how to do it. It's an immediate short-term goal to try to save money by not having to hire people with specialty skills. If that gamble pays off, then it will be like using a sliderule. Kids won't learn it because it isn't a skill that's in demand anymore. If AI turns out to be a niche thing, rather than a massively transformational technology, then tomorrow's kids will learn to be programmers in whatever languages are hot in 20 years.

[–] azertyfun@sh.itjust.works 26 points 6 hours ago (1 children)

It's the same cycle since the '70s. Whether it's COBOL or VB.NET or vibe coding, the premise hasn't changed.

There's three broad categories of code:

  1. Monkey code (random applets that are almost entirely business logic and non-critical)
  2. Actual code (most things)
  3. Crazy shit like kernel or browser code.

I can see vibe coding, situationally, lower the barrier to entry of (1). But also that's no different from COBOL or VB.NET which both promise "MBAs can now write code", which conveniently never extends to maintaining said code. And vibe coding doesn't help with that either, ChatGPT is an awful debugger.

Your boss thinks ChatGPT will help with (2), but it either won't or only very slightly as an advanced autocomplete. For any problem-solving that requires more specific domain knowledge than can automatically find its way into their tiny context windows, LLMs are essentially useless.

.... So I'm not worried. Today's vibe coders are yesterday's script kiddies.

[–] xor@lemmy.dbzer0.com 8 points 6 hours ago (1 children)

the amount of mistakes and and hallucinations ai has makes it actually take longer to code.

it’s the same old garbage in, garbage out….

it can kinda help you get started but that only saves you 10 minutes of reading documentation that you have to read anyway to make sure it didn’t make something up.

[–] Blackmist@feddit.uk 2 points 3 hours ago (1 children)

It seems OK at spewing out a bit of code it found on StackOverflow, or even joining two bits of code together, but it really falls apart when you poke at the edges of it's knowledge.

And the problem is, neither you nor it knows where those limits are, and it very quickly goes from confident copy and paste to confident bullshit.

It even knows what excuses smell like, so it'll give you one at random when you call it out.

[–] xor@lemmy.dbzer0.com 2 points 2 hours ago

yep. i’ve tried it a bit and the errors are blended in so well and seem so plausible, it’s worse than stack overflow….
even when just getting default arguments for a function it makes stuff up.
i do see it getting better at errors like that, but not much better….

[–] anarchiddy@lemmy.dbzer0.com 7 points 5 hours ago

I think this so much less convincing than selling AI as a replacement for skilled labor, not as a way to intentionally deskill actual software engineers.

Capitalism already has a way of preventing you from making your own commodities - you sell your time, and the less they pay you for it relative to how much you need to live, the less time you have for yourself to put towards self sufficiency. We don't have many FOSS products, not because nobody has the knowledge or skill to make them, but because nobody has the time to make them.

There are plenty of reasons to hate corporate-owned AI products, we don't need to be hallucinating new ones.

[–] vane@lemmy.world 1 points 3 hours ago* (last edited 3 hours ago)

I still think that local models in places without internet are better then offline documentation.

[–] LovableSidekick@lemmy.world -1 points 2 hours ago (1 children)

Looks like they don't understand what "vibe coding" means beyond that it involves AI and therefore has a black hat and is bad. That's what happens when people learn everything from memes.

[–] grrgyle@slrpnk.net 1 points 1 hour ago

As I understand it, it was originally meant for "throwaway weekend projects", but then the MBAs got a hold of the term and if you look at job postings nowadays, some companies are really pushing for "AI-first" workers.

The desire obviously isn't just to increase existing dev velocity, but the devalue skills and experience that come from formal education and years of practical learning. Basically to reduce the bargaining power / cost of programmers.

[–] kibiz0r@midwest.social 37 points 9 hours ago* (last edited 9 hours ago) (1 children)

It’s worse than that.

The goal isn’t to sell coding superpowers to programmers. It’s to drive a wedge between employer and employee. Make both of them dependent on an intermediary instead of each other.

Think DoorDash but for coding gigs. You don’t have a job, but a series of push notifications offering a chance to review an 18-line PR for $3.81.

Remember to respond within the next 90 seconds to maintain your priority status, and don’t decline too many offers.

Edit: See also, chickenized reverse-centaurs.

[–] andros_rex@lemmy.world 1 points 4 hours ago

I’m a digital gardener!

This 11 year old adult swim comedy video doesn’t even feel that ridiculous anymore.

[–] Ofiuco@lemmy.cafe 9 points 7 hours ago

It's exactly the opposite of teaching a man to fish, this is telling that man to depend on whatever floats down the river and just pick whatever seems edible, of the man gets enough or poisons himself nobody will know, because the skill to fish would have been lost.

Like people who only had a smartphone for everything, they'll never know the advantages of an actual computer and will struggle with it when they need to use one.

[–] finitebanjo@lemmy.world 1 points 4 hours ago (1 children)

TBH I always felt the same way with "Blueprint" programming where you plug nodes into nodes.

To this day never once used them.

[–] YourMomsTrashman@lemmy.world 2 points 4 hours ago

It's basically the same as programming, just very indirect and slow- but it still requires you to fundamentally understand the concepts of the 'modules' you are using. Vibe coding has borderline random elements.

[–] Zacryon 2 points 6 hours ago

Are there seriously scientists who think AI assistants are good enough for the job?

[–] Unlearned9545@lemmy.world 12 points 10 hours ago (2 children)

I run free local models...

[–] DogOnKeyboard@lemmy.dbzer0.com 7 points 6 hours ago

This, i hope we just dislike the monopolization of AI here and not the technology in general. Self hosting is the way.

[–] DScratch@sh.itjust.works 4 points 10 hours ago
[–] surph_ninja@lemmy.world 1 points 6 hours ago

No. Not really. “Computer” also used to refer to a human profession. I believe “programmer” will be exclusively referring to an AI role in a generation or two.

But that will enable more people to become software designers and architects. Like a mathematician, they’ll need to understand how to perform programming tasks manually, but won’t need to do so in day to day work.

[–] Damage@feddit.it 16 points 12 hours ago (2 children)

I'll go against the grain here: I'm not worried. If you actually care about what you do, even vibe coding can teach you something, it could be a starting point. The internet is not going away, and just looking up this or that thing the AI spit out will help you learn what you're working with.

Is it the same as an uni CS course? No of course, but how many of us got our start just tinkering with stuff we didn't understand?

[–] queermunist@lemmy.ml 4 points 6 hours ago (1 children)

The internet is not going away, and just looking up this or that thing the AI spit out will help you learn what you’re working with.

I think you mean "sifting through several pages of worthless search results while looking for something the AI spit out"

The internet is worse and it can still get worse.

[–] aeshna_cyanea@lemm.ee 1 points 3 hours ago* (last edited 3 hours ago) (1 children)

Bad search results and Bad documentation specifically are a different problem tho

[–] queermunist@lemmy.ml 1 points 1 hour ago

They're a problem being made worse by AI.

[–] DanVctr@sh.itjust.works 2 points 8 hours ago (1 children)

While I agree with you, the unfortunate trend of common folks is to take the easiest path to accomplish their goal.

If that means using a tool they don't understand to achieve a solution instead of being forced to learn from tinkering, I think most people will opt for that route.

They won't take that extra step to comprehend what the AI spits out.

[–] Damage@feddit.it 2 points 7 hours ago

Those kind of people would have behaved the same anyway, copy pasting from the internet or wasting others' time some different way.
I guess we could argue whether giving them AI will act as a multiplier for their damage output or will reduce it because the AI will be savvier than them, but personally I don't see things changing much.

[–] fubarx@lemmy.world 46 points 14 hours ago (9 children)

Here's a fun thing. Using the latest AI to code backend and front-end code. Every couple of weeks, have to stop, go through every line and module, and throw out pretty much 90% of the code, manually refactor, and rewrite it.

It offers a good starting point, but the minute things get slightly complicated, you have to step in. I feel bad for people who think this will make it so they don't need experienced developers and architects. They're in for a rough ride.

[–] Barbarian@sh.itjust.works 28 points 10 hours ago (1 children)

An interesting point I heard the other day: if AI can replace entry level jobs, doing simple scripts that AI can definitely do (because it essentially just spits out the stack overflow/Reddit/etc training data verbatim), then companies no longer need entry level programmers.

If they don't need entry level programmers, how do you get future senior programmers? Skipping directly to advanced stuff without getting practical experience on the simple stuff is incredibly hard.

What happens when the current senior programmers retire in larger numbers, and there's very few replacements because the ladder is gone?

[–] makeshiftreaper@lemmy.world 14 points 8 hours ago

That's a problem for Q72 and they're incapable of looking past Q4. Besides, they'll have already jumped ship by then, what do the execs care if they make this quarter just ever so slightly more profitable

[–] spankmonkey@lemmy.world 7 points 9 hours ago

Every couple of weeks, have to stop, go through every line and module, and throw out pretty much 90% of the code

It offers a good starting point

It doesn't sound like a good starting point if you have to throw out 90% of it every couple of weeks.

load more comments (7 replies)
load more comments
view more: next ›