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 controversial new old
[–] [M] 2 points 31 minutes ago
[–] 4 points 4 hours ago

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

  • source
  • [–] 14 points 9 hours ago (1 child)

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

  • source
  • hideshow 1 child comment
  • [–] 2 points 7 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.

  • source
  • [–] 5 points 9 hours ago

    And the post is written with fucking AI lmao

  • source
  • [–] 12 points 11 hours ago (2 children)

    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

  • source
  • hideshow 2 child comments
  • [–] 5 points 11 hours ago (2 children)

    having ai do your homework for you is not a flex

  • source
  • hideshow 2 child comments
  • [–] 4 points 5 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.

  • source
  • parent
  • [–] 14 points 14 hours ago (1 child)

    Verify everything. Audit before production.

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

  • source
  • hideshow 1 child comment
  • [–] 43 points 21 hours ago (5 children)

    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.

  • source
  • hideshow 5 child comments
  • [–] 6 points 12 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.

  • source
  • parent
  • [–] 10 points 16 hours 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.

  • source
  • parent
  • [–] 11 points 21 hours ago (2 children)

    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

  • source
  • parent
  • hideshow 2 child comments
  • [–] 9 points 16 hours 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

  • source
  • parent
  • load more comments (1 reply)
  • [–] 10 points 19 hours ago (6 children)

    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.

  • source
  • hideshow 6 child comments
  • load more comments (6 replies)
    [–] 23 points 23 hours ago (7 children)

    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.

  • source
  • hideshow 7 child comments
  • [–] 4 points 14 hours ago (6 children)

    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

  • source
  • parent
  • hideshow 6 child comments
  • [–] 3 points 12 hours ago (5 children)

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

  • source
  • parent
  • hideshow 5 child comments
  • [–] 2 points 12 hours ago (4 children)

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

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 12 hours ago (3 children)
  • [–] 1 point 12 hours ago* (2 children)

    And using "AI" to write code or assignments will hinder a student from learning that more technical in the first place.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 12 hours ago (1 child)

    But the bit of the post I'm talking about isn't about students.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 12 hours ago

    This happens with students and professionals all the same. I did miss you specifying professionals in your comment but most of what I said is correct. I'm not a student and I'm still learning more just by forcing myself to do things on my own.

  • source
  • parent
  • [–] 144 points 1 day ago (51 children)

    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.

  • source
  • hideshow 51 child comments
  • load more comments (50 replies)
    [–] 24 points 1 day ago

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

  • source
  • load more comments
    view more: next ›