2026-09-15 01:58 UTC
Replies (26)
-
@rumschlumpel@feddit.org 2026-09-15 02:07
The Luddites were right.
-
@reallykindasorta@slrpnk.net 2026-09-15 03:07
That’s what they’re doing for my SO’s big introductory class in the humanities. No homework, quizzes, or papers. Short answer exams done in a special testing center. Really sucks for people who were decent at essays and turning in assignments on time but not great at exams.
-
@FaceDeer@fedia.io 2026-09-15 03:11
Nobody's asking what happens in Month 18 when the original dev has left and nobody understands the codebase. Throughout my career, I've often had to sync a git repository for some random project that I've never worked with before and then had to muddle through whatever was in there hoping that the documentation was vaguely complete and accurate. Nowadays it's actually much easier. If the documentation isn't complete or accurate I just turn my coding agent loose on it and tell it to write the documentation. I get the impression that the guy writing this hasn't actually used modern coding agents, this is not a problem. I see coding AI as being similar to a compiler. Before compilers came along programmers had to work in assembly language. Nowadays very few programmers ever do anything in assembly and that's perfectly fine.
-
@FuglyDuck@lemmy.world 2026-09-15 03:15
The luddites had a point. They weren’t opposed to technology, but the use of technology to remove skilled labor to produce inferior products. Also, the pilot/autopilot argument is, kinda not applicable. The pilots aren’t just fucking around- autopilot systems only manage some aspects of flying, the pilots are still fully engaged.
-
@annoying_cyclist@programming.dev 2026-09-15 03:44
I have a hard time telling AI authored LinkedIn thought leadership apart from formulaic LinkedIn thought leadership sometimes, but this feels AI written, which makes it fairly amusing considering the point it’s making. (Does vibe coding feel incredible? Also, “Nobody’s asking what happens in Month 18 when the original dev has left and nobody understands the codebase” implies that the vibe coder original dev understood the codebase at any point, which isn’t an argument I’d feel comfortable making for any of the ones I’ve worked with)
-
@chunes@lemmy.world 2026-09-15 04:53
It’s funny watching this type of bellyaching play out like a loop over history. People went through this EXACT same bellyaching when compilers first started showing up. The machine coders considered themselves superior and their skills indispensable. Now those people are extinct and modern people consider their compiler skills to be elite, not realizing they’re using the baby mode that people railed against in the past.
-
@schnokobaer@feddit.org 2026-09-15 05:05
This is kind of like the “you won’t have a calculator with you all the time” argument by your 8th grade math teacher in 2003, except instead of making yourself dependent on a little solar powered device (that you could have with you all the time if you really wanted to, even before smartphones) you’re becoming dependent on a subscription service offered by a trillion dollar company that can increase the price tenfold at will, or cut you from the platform entirely, stripping you of all your professional expertise at once.
-
@farmgineer@nord.pub 2026-09-15 05:54
when the original dev leaves and nobody understands the code In my experience at work, no one cares about this. They assume the AI will be able to get there with enough tokens/time with the help of the human at the other end. They have done this and decided it was good enough. Meanwhile, people like me who don’t use AI coding agents and are PRing and modifying the code are having a hell of a time.
-
@wuphysics87@lemmy.ml 2026-09-15 06:00
This is largely an oversimplification because it depends on how you use AI in the first place. Are you building modularly and incrementally? Or are you letting it ride on black?
-
@mindbleach@sh.itjust.works 2026-09-15 06:40
Compilers would look the same. You give some people a tool that turns fiddly low-level repetition into relatively painless double-checking. Then you yank that tool away, and oh no, they’re not as good at the fiddly low-level repetition. What matters is - are these students worse-off, with the tool? It’s not going away. Foreverafter, a couple gigs of linear algebra will turn your to-do list into an actual running project. We have to ask if teaching the fiddly low-level repetition is the point… or just a means to an end. You can scoff that compilers are objectively better, but they weren’t! Sometimes they still aren’t! We were teaching kids to consider inline assembly well into the Windows Vista era. Even now, compilers with decades of active development can have bizarre corner cases, which any hardened bit-banger of machine code would never write. But they’re all good enough that plaintext assembly has become an arcane third-year topic, and hexadecimal machine code is the realm of bare-metal maniacs. Teaching math, kids have to know what numbers are, and how base ten works, and why the calculator says 11-3=8. But as you go up to college math it matters a lot less whether people can do shit in their heads… or even remember how. Open-book and open-calculator exams are still fuckin’ hard. They’re just hard because you’re trying to apply some obscure proof to a rat’s-nest of swooping symbols, instead of because you’re worried about having enough time to write out long division to umpteen places. The latter can be sufficiently approximated with two wooden sticks. We can assume anyone doing math professionally has two sticks. Continuously! As a given, for their job. Probably at home as well. Teaching programming, you have to break people a certain way. No gentle and charming syntax can disguise the mechanized nastiness of what code is. Whatever semi-readable text you’re looking at will be squinched through a flake of tortured sand in a bazillionth of a second. But only after getting transformed at least two times in processes you kinda have to trust will be computationally equivalent, unless you want to minor in a branch of mathematics haunted by Stephen Wolfram. Ultimately there is a shockingly small state machine designed to trick you into off-by-one errors. But once people can knock out fizzbuzz on a paper 6502… they’ve kinda got it. They’ve been inculcated. They will soon apply arcane patterns to a rat’s-nest of obtuse variable names. Ssshould they have to do that by hand? They’re not doing the assembly by hand. They’re not even looking at the assembly. They might never need to think about assembly again. So long as they’re playing spot-the-bollocks for a flurry of pull requests, that’s arguably a more useful skill than writing clean toy code from scratch. Especially in pen and ink.
-
@Awooooooga@lemmy.world 2026-09-15 07:23
Fuck software engineers
-
@HexesofVexes@lemmy.world 2026-09-15 08:27
The chart they didn’t post showed that time spent on homework correlated well with exam score regardless of AI use. Turns out using AI to avoid homework (in this scenario, replace work) might be the issue. Using it to improve the quality of work (e.g. when you’re done coding a block, getting an AI to help fuzz your inputs to test that block) is likely to be beneficial.
-
@soyslurper2@lemmy.dbzer0.com 2026-09-15 10:58
This isn’t programmer humor… post to the right comm like fuck_ai@lemmy.world
-
@FishFace@piefed.social 2026-09-15 12:03
This is probably overly pessimistic/optimistic (depending on your outlook) in terms of timing. You won’t forget how to code after 18 months of using AI to do it instead; if you decide to go cold turkey, or OpenAI turns the screws on pricing, or whatever, you’ll be back in the swing of things in no time. The lesson from schools is that junior programmers who are learning now are not going to gain the same ability we did. (Besides that they’re finding it difficult to get hired because the AI can do junior programming fairly OK, that is). So the problem won’t be in 18 months; it’ll be in a few years at least, from that point of view. There’s the separate question of architecture and code quality; by this point we’ve probably all seen the impenetrable morass that vibe coding leads to. That, I’m guessing, will cause problems much sooner.
-
@dandi8@fedia.io 2026-09-15 12:26
Nice message, but why use the slop machine to write it? Use your own words!
-
@Wirlocke@lemmy.blahaj.zone 2026-09-15 14:04
I agree with everything except for vibe coding feeling great. Am I the only one who gets incredibly anxious relying on AI to code? I still ask it for code when I really just want to move on from a problem but it always feels like voluntarily putting mold in my floorboards.
-
@dylanTheDeveloper@lemmy.world 2026-09-15 15:39
I know that when i started using AI i got over blocks much faster. A system from design to implementation that use to take a week now only takes a few hours with most of that is testing and reviewing the code. I don’t use agents to test and review code btw because i still want to know what’s going on but my colleagues are definitely using agents to build test large codebases. Im sorry but the truth is AI has changed how we build products in the same way intellisense and jet brains did but on a scale i haven’t seen in my lifetime.
-
@geissi@feddit.org 2026-09-15 20:31
Verify everything. Audit before production. Yeah, the move fast and break things industry already didn’t do that before AI
-
@Modern_medicine_isnt@lemmy.world 2026-09-15 14:48
I guess exams in school are supposed to represent real life??? Real life is open book. Exams are horseshit.
-
@Sam_Bass@lemmy.world 2026-09-15 23:37
having ai do your homework for you is not a flex
-
@underscores@lemmy.zip 2026-09-15 23:51
Goodluck arguing this with the AI bros “dude I have an agent of workflow that goes through the entire codebase. the agent is the expert and I am guiding it” alright man you have fun with that
-
@mojofrododojo@lemmy.world 2026-09-16 01:36
“AI is the asbestos we are shovelling into the walls of our society, and our descendants will be digging it out for generations.” - Cory Doctorow,
-
@kouichi@ani.social 2026-09-16 02:08
And the post is written with fucking AI lmao
-
@hark@lemmy.world 2026-09-16 04:09
Vibe coding at work lets you slack off and then secure your job when shit inevitably hits the fan and you have to untangle the mess. Seems like a win-win to me, assuming you know how to program to do the untangling part. The only bad part is not having any satisfaction in doing the job, but there was enough corporate bullshit in place all along to ensure that regardless.
-
@sudoer777@lemmy.ml 2026-09-16 07:26
Whether or not you can pass an exam barely means anything IRL
-
@anzo@programming.dev 2026-09-16 10:55
Off-topic.