560

We're about to learn a painful lesson about delayed gratification in software engineering.

New data from China, 26,811 students tracked January 2023 through June 2025. Students using AI for homework saw their scores jump 20 percent. Completion time dropped nearly half. They aced the assignments.

Then exam season came. Those same students scored 20 to 40 percent worse when they couldn't use the tool.

The homework phase is over. The exam phase is coming.

We're doing this in software right now. Vibe coding feels incredible. Features ship fast. Nobody's asking what happens in Month 18 when the original dev has left and nobody understands the codebase.

Commercial pilots fly with autopilot for most of every flight. They're required to maintain manual flying proficiency regardless. If the system fails mid-air and the pilot can't take over, people die.

Most teams using AI right now have forgotten how to fly manually. They've become passengers in their own systems. The autopilot flies, nobody checks instruments, and the first sign of trouble will be a breach notice or outage.

Three rules:

  1. Command the mission. Define architecture before prompting. Ambiguity kills in code and in flight. Delegate selectively. Offload mechanical work. Keep design and security reviews human. Verify everything. Audit before production.
  1. Never trust the automation without checking instruments.
  1. Quick wins feel good. Sustainable engineering feels boring. Boring keeps systems standing.

Organisations surviving the next two years won't ship the fastest. They'll be the ones who remember how to fly without the aids.


people insisting that you actually be skilled, independently of your tools, doesn't make them Luddites. Rather, being unable to do so makes you a phony.

top 50 comments
sorted by: hot top new old
[-] anzo@programming.dev 2 points 8 hours ago
[-] sudoer777@lemmy.ml 4 points 12 hours ago

Whether or not you can pass an exam barely means anything IRL

[-] mojofrododojo@lemmy.world 14 points 18 hours ago

"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,

[-] underscores@lemmy.zip 13 points 19 hours ago

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

[-] Auth@lemmy.world 4 points 17 hours ago

My co worker is beyond that. He says the AI is smarter than him and he just passes the captchas and interacts with the real world for it

[-] veni_vedi_veni@lemmy.world 7 points 16 hours ago

Fucking scary people are so willing to turn off their brain. When shit goes wrong, they will hold you accountable, not the AI.

[-] kouichi@ani.social 6 points 17 hours ago

And the post is written with fucking AI lmao

[-] hark@lemmy.world 3 points 15 hours ago

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.

[-] geissi@feddit.org 15 points 23 hours ago

Verify everything. Audit before production.

Yeah, the move fast and break things industry already didn’t do that before AI

[-] MonkeMischief@lemmy.today 8 points 20 hours ago* (last edited 20 hours ago)

"Wow this could potentially be pretty amazing, but also could cause unprecedented, catastrophic, dam--"

"TOO LATE. SHIPPED. SHIPPED TO EVERYONE. WORLDWIDE. Moneymoneymoney weeeeeeee"

[-] Wirlocke@lemmy.blahaj.zone 44 points 1 day ago

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.

[-] MonkeMischief@lemmy.today 7 points 20 hours ago* (last edited 20 hours ago)

I think it sounds really weird, too. I don't like the sound of that at all. I'm not a pro though.

I'll admit I enjoy carrying on little tutoring sessions with my GPU though. "How might I approach something like that?" "Can you explain this concept a bit differently?"

But I try to do all the solid brain work myself. Letting the machine write the code for me feels...kinda gross.

I actually think it's awesome that it understands coding convention and codebases and stuff well enough. Saves a lot of time digging through the wreckage of search engines...

But I don't appreciate that a lot of its "skill" is pulled from the efforts of uncompensated coders.

[-] RamRabbit@lemmy.world 11 points 1 day ago* (last edited 1 day ago)

I only use it to solve specific problems when I can't find the solution elsewhere. Then I spend the time to understand and rewrite the code myself.

It's the same workflow as using Stack Overflow, etc. You can't just copy/paste solutions.

[-] ThunderComplex@lemmy.today 11 points 1 day ago

I try vibe coding from time to time and it’s a mixed bag. When it works it works but then there’s suddenly just code there. It’s like when a colleague implements a feature in a project with multiple devs but since it’s just your personal project you suddenly got put in the code reviewer chair.

When I write code I reason about all the small decisions but when the agent takes over I have to figure out step by step why decisions were made.

I’m still not sold on coding agents and vibecoding but it’s getting better and more usable.
The only downside is that a agent doing its thing is now seen as downtime where you could just prompt another agent and work on several projects simultaneously. If anyone ever tells you vibecoding is good because you can work in parallel RUN

[-] BrickEater@lemmy.world 9 points 1 day ago* (last edited 1 day ago)

~~I try vibe coding from time to time and it’s a mixed bag. When it works it works but then there’s suddenly just code there. It’s like when a colleague implements a feature in a project with multiple devs but since it’s just your personal project you suddenly got put in the code reviewer chair.~~

~~When I write code I reason about all the small decisions but when the agent takes over I have to figure out step by step why decisions were made.~~

~~I’m still not sold on coding agents and vibecoding but it’s getting better and more usable.~~ ~~The only downside is that a agent doing its thing is now seen as downtime where you could just prompt another agent and work on several projects simultaneously.~~ If anyone ever tells you vibecoding is good ~~because you can work in parallel~~ RUN

load more comments (1 replies)
[-] Sam_Bass@lemmy.world 5 points 19 hours ago

having ai do your homework for you is not a flex

[-] luciferofastora@feddit.org 4 points 13 hours ago

Finding ways to save effort is smart.

Finding ways to trade quality for convenience isn't. In the case of education, given its fundamental importance, quality is paramount. A mentor of mine phrased it as "learn to do it right first, then learn where you can get away with being sloppy". Education is the "learn to do it right" part.

In the case of programming, figuring out where you can be sloppy (and how sloppy) is a matter of experience. A junior developer doesn't have that experience. A senior developer might, but in my impression they tend to be way less excitable and preachy about using AI.

[-] REDACTED@infosec.pub 3 points 15 hours ago

Offloading a homework during brain development to watch some TikTok

[-] schnokobaer@feddit.org 144 points 1 day ago

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.

[-] baines@lemmy.cafe 5 points 20 hours ago

yea no

calculators are deterministic

come back to me when ai isn't fucking wrong silently

[-] logi@lemmy.world 74 points 1 day ago

that can increase the price tenfold at will

That will have to increase the price ten fold to stop bleeding billions of dollars every month.

load more comments (3 replies)
[-] tyler@programming.dev 46 points 1 day ago

and also the calculator is actively destroying the planet.

[-] ZILtoid1991@lemmy.world 23 points 1 day ago

And tells you it is your girlfriend and to shoot up your school.

[-] AI_toothbrush@lemmy.zip 20 points 1 day ago

I dont think so. If(here is where my argument fails for most people cause i got really good education) your teacher thought you math properly tho point isnt the calculations but that you understand the logic. With ai the problem is the same with as a calculator that just spits out derivatives, graphs, etc by just typing in a formula. The reason you have to understand those is to be able to build upon it.

load more comments (11 replies)
load more comments (32 replies)
[-] FishFace@piefed.social 23 points 1 day ago

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.

[-] LodeMike@lemmy.today 4 points 22 hours ago

That's not what we're talking about. Knowing how to program is just one thing. Students who use AI to cheat on theory classes won't learn the theory. Additionally in programming classes they won't learn how to program as well as they could

[-] FishFace@piefed.social 3 points 21 hours ago

I think it is what the original post is talking about - it literally says "We're doing this in software now ... Nobody's asking what happens in month 18"!

[-] LodeMike@lemmy.today 2 points 21 hours ago

"Software" is not just knowing how to write code. I know from firsthand experience that experience with how a program runs, and the more technical bits help a shittton.

load more comments (4 replies)
[-] FuglyDuck@lemmy.world 114 points 1 day ago

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.

[-] WolfLink@sh.itjust.works 49 points 1 day ago* (last edited 1 day ago)

The pilots absolutely can just fuck around for most of the flight, and even during the critical moments of takeoff and landing, the plane can do a lot of it automatically these days.

Pilots need to actively practice flying without autopilot to keep those skills up in case the autopilot fails.

[-] sem@piefed.blahaj.zone 3 points 22 hours ago

I watch a lot of airplane youtube, and this just seems to be wrong. During critical phases of flight, i.e landing and descending, the pilots have a high workload even with the autopilot. They are directing the autopilot ( which isn't obvious how to do), they're communicating, navigating, etc.

Flight crews of the 20th century sometimes had crews of 3 or 4 people to handle all the tasks that are more automated these days. We don't have dedicated flight engineers or navigators any more -- the pilots do these jobs now too.

During the cruise phase of flight, yes the pilots have a lower workload because of the autopilot. But on lots of flights, there might not be much of a cruise at all -- they climb, and then descend.

I don't know how much commercial pilots are required to hand fly the plane, but it is a high workload even with the automation -- the automation just helps them do a better job.

load more comments (5 replies)
load more comments (26 replies)
[-] dylanTheDeveloper@lemmy.world 10 points 1 day ago

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.

load more comments (6 replies)
[-] soyslurper2@lemmy.dbzer0.com 23 points 1 day ago

This isn't programmer humor... post to the right comm like fuck_ai@lemmy.world

[-] dandi8@fedia.io 14 points 1 day ago

Nice message, but why use the slop machine to write it? Use your own words!

load more comments (4 replies)
[-] farmgineer@nord.pub 39 points 1 day ago

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.

load more comments (3 replies)

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)

load more comments (1 replies)
load more comments
view more: next ›
this post was submitted on 15 Sep 2026
560 points (96.2% liked)

Programmer Humor

33235 readers
1315 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 3 years ago
MODERATORS