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 98 comments

sorted by: hot top controversial new old
[–] 42 points 1 month 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
  • [–] 12 points 1 month ago* (last edited 1 month 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
  • [–] 12 points 1 month 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
  • [–] 7 points 1 month ago* (last edited 1 month 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
  • [–] 0 points 1 month 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
  • [–] 7 points 1 month ago* (last edited 1 month 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
  • [–] 37 points 1 month ago (3 children)

    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.

  • source
  • hideshow 3 child comments
  • [–] 14 points 1 month ago (2 children)

    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.

    Or if it does break, just hit it with the AI stick until it works again.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 110 points 1 month ago (30 children)

    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.

  • source
  • hideshow 30 child comments
  • [–] 26 points 1 month ago* (1 child)

    I feel like their point was that the gains of technology were not distributed fairly, which is largely the concern today. It’s not “technology is bad”, or “technology make bad thing”; rather, “the owners of the machine undercut our labor, and we lose our jobs”, which I think was true. In the modern world, there are likely less tailors, as a percentage of the working population, certainly in first world countries. Sweatshops still exist, and it’s people’s labor competing against a production line, in terms of ROI for a business.

    I get the sense we all know AI isn’t going to bring about a uptopia for all people, because the economic systems don’t incentivize that. There’s some hypothetical world where this sort of technological advance could benefit all people, but it’s not the one we live in. That’s a reality & major problem for the technology (among other issues).

    I certainly think the cost of labor for tech development is going to drop significantly due to the market pressures; look at all the tech layoffs. At the same time, the upside is these tools make certain projects accessible & possible, because prior, would have needed significant funding, amazing solo skills, etc. There’s new opportunities available, but it’ll come at the cost of cratering tech position compensation & job security.

    I don’t know anyone in my field right now who feels safe (game dev), and I have many talented friends out of work.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 44 points 1 month ago* (6 children)

    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.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 3 points 1 month 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.

  • source
  • parent
  • [–] -5 points 1 month ago (2 children)

    They did have a point. The printing press still changed the way information works

  • source
  • parent
  • hideshow 2 child comments
  • [–] 23 points 1 month ago (1 child)

    Luddites weren’t concerned about the printing press. Their fight was over mechanized looms and knitting frames.

    Their concerns were mostly about losing their jobs, as well as the absolute dog shit quality the mechanical machines produced at the time.

    In 1814, printers in London did have similar conniptions over the steam press, though.

  • source
  • parent
  • hideshow 1 child comment
  • [+] -20 points 1 month ago (17 children)

    the luddites had a point… in the moment… kinda… but i think have largely been pretty conclusively proven wrong… clothing is now plentiful, and i doubt anyone would want to go back to paying taylors to make all their clothes for 10x more, even if the clothing would be much higher quality, which i even doubt: clothing quality doesn’t come down to artisan skill any more, it comes down to choices you make, and an artisan can still make cost cutting decisions on fabric, construction, etc

  • source
  • parent
  • hideshow 17 child comments
  • [–] 26 points 1 month ago (4 children)

    Maybe. I think a sizable group of people would rather put fast fashion back in the bag.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 1 month ago (1 child)

    Fast fashion is a different topic from the machine produced vs tailor point they're making.

    Made to order is getting more and more traction, because we have machines able to fully automate it. Making higher quality clothing more available than ever

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

    Eeh. High quality fabric is decently hard to get still, and the ability to recognise the quality of fabric is a more or less lost art for laypeople, when in times past this was something most everyone could tell.

  • source
  • parent
  • [–] -2 points 1 month ago (1 child)

    i definitely agree, but plenty leading to waste doesn’t mean that plenty is a bad thing

    having enough food to not worry about food waste is definitively a good problem to have. ideally we don’t have food waste because we don’t have enough food for everyone, but just because plenty leads to waste at least initially isn’t an argument against plenty

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 1 month ago

    what are you agreeing with you dummy? you definetly agree to disagree or what? fast fashion clothes become waste because people don't actually want to wear them after a few times, or even if they do the clothes are so bad they get damaged very soon.

    its also not just about the waste products, its about the pollution and the destruction of our environment

  • source
  • parent
  • [–] 17 points 1 month ago (3 children)

    So...have you not heard the damage fast fashion did to the planet? Sure, it make making cloth quicker and cheaper and widely available, but in the end it's a huge source of chemical waste, landfill waste, and microplastic. Because clothing are so much cheaper to buy new than fixing it, we lost a lot of skilled labour to automation.

    The same thing happened everywhere, automation take away human agency, and that take away skill learning. In the end humanity will suffer because less and less people gonna learn how to fix the shit that they rely on. That didn't happen on accident, that's by design. We all thought AI gonna upskill a lot of people, but i feels like instead of making a nation of artisan it gonna make a nation of 7/11. Just look at Destin's struggle to make a fucking bbq brush fully American, the nation of 300millions people can't even provide parts that fully made within the nation.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 1 month ago (2 children)

    Fast fashion would be the other end of an extreme. Another way is for stores to have one of each size, you try the one you want and place an order. The store delivers in batches and enough orders are placed.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 month ago

    That’s not how clothes work, these days you either get fast fashion or tailored. There’s basically nothing left in between because of the economics of the industry. If you’re doing readymade clothing, you gotta do it at scale (and it’s never going to fit a lot of people). This is exactly what the Luddites predicted; tailored clothes for very rich people, slop for everyone else.

  • source
  • parent
  • [–] 16 points 1 month ago (4 children)

    No. They weren't proven wrong, pauperism was the consequence and it was horrible. Luckily we shifted that back to regimes that don't like to report much on terrible living and environmental conditions so we don't have the filth at our doorstep.

  • source
  • parent
  • hideshow 4 child comments
  • [+] -9 points 1 month ago (3 children)

    yeah… as i said, they had a point in the moment

    in 2026 we have retraining programs and social security programs… these are the solutions to industrialisation; not ignorance… the longer you fight industrialisation the harder it hits because rather than happening gradually it happens all at once and society has a harder time absorbing it

  • source
  • parent
  • hideshow 3 child comments
  • [–] 6 points 1 month ago (2 children)

    Stupid Uyghurs, should just make use of their "retraining programs and social security programs" instead of being forced to produce our cheap shit.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 1 month ago (1 child)

    china having human rights abuses is not an argument against retraining people when technology starts to make jobs redundant

  • source
  • parent
  • hideshow 1 child comment
  • [–] 5 points 1 month ago

    Their point is that the people being abused in sweatshops aren’t the same people who are benefiting from retraining and social security. Because the Luddites were basically correct about everything

  • source
  • parent
  • [–] 5 points 1 month ago* (last edited 1 month ago)

    It’s the sweatshops, man. The sweatshops suck. I would absolutely rather have one set of tailored clothes, vs. endless variety from sweatshops where Bangladeshi children work for pennies an hour.

  • source
  • parent
  • [+] 5 points 1 month ago* (last edited 1 month ago) (1 child)
  • [–] 2 points 1 month ago

    The one glimmer of hope is open models and especially fully open source ones like K2 Horizon. Open models and tooling for running them locally are rapidly evolving such that the tech will be democratized instead of a couple capitalists having a stranglehold on the tech.

  • source
  • parent
  • [–] 36 points 1 month ago (11 children)

    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.

  • source
  • hideshow 11 child comments
  • [–] 22 points 1 month ago (10 children)

    yeah, but it's great for those that hated busywork and were good at exams

  • source
  • parent
  • hideshow 10 child comments
  • [–] 9 points 1 month ago (5 children)

    I'm the "good at exams" type, I find paper writing (or novel writing... 😢) unpleasantly tedious. If we lose the "good at structuring complex thoughts in a way that can be coherently decoded by other humans" types, the "good at exams" types will suffer. We need people who can write good papers and people who can recall diverse facts and arrange them into simple shapes quickly.

  • source
  • parent
  • hideshow 5 child comments
  • [+] 9 points 1 month ago (4 children)
  • [–] 5 points 1 month ago* (last edited 1 month ago) (3 children)

    we were talking about the need for radical education reform over a decade ago

    Education, and especially critical thinking, has been systematically gutted by conservative governments for at least 4 decades in the Western world. The goal is the absolute minimum knowledge and thinking skills (preferably without learning skills) necessary to complete the wage slavery tasks.

  • source
  • parent
  • hideshow 3 child comments
  • [+] 3 points 1 month ago* (2 children)
  • [–] 2 points 1 month ago (1 child)

    Hard agree on Prussian-style education (which had similar goals of wage slavery when it was introduced). Unfortunately the pessimist in me thinks reform will likely have to wait until after this round of fascism has run its course, but it absolutely need to be a high priority when the time comes. Best time to plant a seed is twenty years ago...

  • source
  • parent
  • hideshow 1 child comment
  • load more comments (1 reply)
  • [–] 3 points 1 month ago (1 child)

    I wasn't great at exams, but I think if I re-did university today I'd still do much better because my personal learning style is best when I talk through the material with someone. Sitting in a lecture listening to someone monologue at me, reading a static textbook, those weren't great. But with LLMs every student now has full-time access to a "live tutor" with infinite patience and no sense of social risk from asking it dumb questions. It's absolutely my perfect learning environment.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 1 month ago

    https://www.youtube.com/watch?v=VwZi58u1FjI - The Dragon Speech

    All the higher mammals learn by playing, by doing, by interacting. And indeed, the higher the mammal, the more of its life it spends in play to prepare itself for adulthood. So you can see, this active role of the mind is fundamental to the way we think. It’s wired into our brains.

    It's a really great speech, and a lot of it is about the failures of our educational system.

  • source
  • parent
  • [–] 49 points 1 month ago (1 child)

    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)

  • source
  • hideshow 1 child comment
  • [–] 15 points 1 month 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,

  • source
  • [–] 12 points 1 month 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
  • [–] 23 points 1 month 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
  • [–] 3 points 1 month 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 1 month 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 1 month 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 1 month ago (3 children)
  • [–] 1 point 1 month ago* (last edited 1 month 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 1 month ago (1 child)

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

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

    And the post is written with fucking AI lmao

  • source
  • [–] 24 points 1 month ago

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

  • source
  • [–] 10 points 1 month ago (4 children)

    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?

  • source
  • hideshow 4 child comments
  • [–] 10 points 1 month ago (1 child)

    ive personally found LLM coding to be pretty effective if i adhere to very strict "engineering best practices" like TDD, good documentation, thorough API design, systems design, etc.

    im very afraid that the next generation of software engineers will never develop the skills needed to make the most out of it because they skipped the rudiments of good software engineering.

    to me it feels like playing jazz without learning scales. it's possible to be an incredible jazz musician without formal training if you're a savant... but you're probably not.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 1 month ago

    I have a little more hope for future generations. Regardless of if you are primarily using ai to speed up a traditional work flow or vibe coding, there still are more and less effective ways to get things done. I've found if I write sonething I'm familiar with like bash or Python, I "know enough" to write functions and refactor incrementally. It's a methodical process which produces code better than I can write by myself in less time.

    Compare that to when I write Lisp. There it's more or less throw shit at the wall until I somewhat get what I want. It takes longer and can be next to impossible to extend or effectively refactor.

    Based on that observation of myself, I think we'll find two (and probably more) kinds of programmers in the future. Ones who use it as an assistant to speed up a traditional workflow, and those who produce the slop that we are afraid of.

    Perhaps to give us any amount of additional hope/comparison to now. There still have been people who have programmed now who create slop. And that comes to the way we use references like stack exchange or the Arch Wiki. Are you copy and pasting while learning what things mean and learning in the process? Or are you just stringing things together to get results at all? I don't think we would argue those references made all of us worse.

    So I think it's an apt concern, but we'll have to wait to see what it's like whole sale. I was a doubter for a long time, but I've come to understand where Torvalds et al are coming from.

  • source
  • parent
  • [–] 5 points 1 month ago (1 child)

    having ai do your homework for you is not a flex

  • source
  • hideshow 1 child comment
  • [–] 14 points 1 month ago (4 children)

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

  • source
  • hideshow 4 child comments
  • [–] 11 points 1 month ago (5 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 5 child comments
  • [–] -4 points 1 month ago (4 children)

    Agreed. If you don't use AI in coding you are not competitive with someone who does. It really is that simple. You won't be able to keep up, your bosses will see, you will get fired and that's that.

    Even if the quality you deliver without AI is better, quality is not everything. Time is always a factor and AI beates you ten times over. The rest is sane flows with lot's of testing etc.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 13 points 1 month ago (1 child)

    This isn't One Hour Hot Dog. If you need a big huge fix right the hell yesterday, you fucked up last week. Possibly last year. And what's gonna prevent that sort of company-liquidating blunder is a layer of crotchety obsessives who can spend a day reading and then commit one line. 'Hit engine with hammer: $1. Knowing where to hit: $9,999.'

    A system that's pretty good at guessing a hundred places to try hitting has obvious value. Especially when undo is a thing. But this attitude of 'the future is now, old man!' is almost as off-base as the folks insisting a magic coding robot won't help anybody.

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

    I agree with you. I'm not even 100% anti-AI even though a lot of how it is used absolutely reeks.

    Of course Big Business is gonna be all about shipping it fast and cheap to the detriment of all else as long as it "works right now." The ridiculous farce of capitalism as we know it now is that their real goal is to sell off and bail at a profit just before all that vibe-debt comes due and things implode.

    It doesn't mean it's the best way to create software.

    It reminds me of how homes nowadays are thrown together and so ridiculously shoddy because it's all about speed and holding together just long enough to sell.

  • source
  • parent
  • [+] 2 points 1 month ago (2 children)
  • [–] -1 points 1 month ago* (last edited 1 month ago)

    You should give it another go, it has evolved disturbingly since last year. It out performs a junior level software engineer in both design, implementation, testing and debugging.

    The hybrid model of a senior engineer using AI to produce code while the rest of the time allocation is spent on reviewing is the new normal.

    You get 4 weeks to build x feature, you spend maybe a day with the help of AI then use the rest of the allotted time testing and debugging. What's happening now is your allotted time is shrinking because managers understand how much faster engineers are working so its a cycle of shorter deadlines which pushes everyone to use AI.

    I wouldn't worry about software engineers going extinct. The role is changing but those core skills are really important to catch mistakes from both humans and AI.

    Right now theirs two types of people using AI, software engineers who learned computer science and built software products and Joe MBA who struggles to write a bat file with the latter struggling to build cohesive products

  • source
  • parent
  • load more comments (-1 replies)
  • [–] 3 points 1 month 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
  • [–] 4 points 1 month ago

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

  • source
  • [–] [M] 4 points 1 month ago*
    [–] 5 points 1 month ago (2 children)

    I guess exams in school are supposed to represent real life???
    Real life is open book. Exams are horseshit.

  • source
  • hideshow 2 child comments
  • [–] 3 points 1 month ago* (last edited 1 month ago)

    I kinda agree. Although, I think the logic is nuanced. There is value in being able to know your stuff when your advanced tools and reference materials aren't readily available or have failed.

    ... But then again I'm sure most of these kids aren't going to be needing to emergency land a spacecraft by doing complex math from their head, Apollo 13 style... so... :p

    But the cynic in me agrees "exams are horseshit." It feels like they're often used as a filter to keep the degree/cert/whatever "valuable."

  • source
  • parent
  • [–] 1 point 1 month ago

    It is a metaphor, not a representation.

    What it is saying is that structural qualitative improvement holds out longer and will give better results compared to trying to improve as fast as possible regardless of quality.

    Kind of.

  • source
  • parent
  • [–] 2 points 1 month ago

    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.

  • source
  • [–] 1 point 1 month ago (3 children)

    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.

  • source
  • hideshow 3 child comments
  • [–] 4 points 1 month ago* (last edited 1 month ago) (2 children)

    The main problem with AI is that it's pretending to understand more than it actually does right now. It can't do software architecture. It can't really write maintainable code without a lot of re-prompting and corrections. And yet it will happily make a bunch of those decisions for you when you ask it to write you an app.

    Compilers are well-defined tools. "Human-readable" code goes in, "machine-readable" code comes out, according to some spec somewhere. Yes, compilers can be nondeterministic and they do a lot of weird stuff sometimes and they choose the wrong approach often, so some developers still need to understand assembly and CPU cache and SIMD and other features of the hardware our code runs on. At the very least every developer needs to understand the performance tradeoffs they're making, or we end up with a JS-based start menu in Win11. But at least compilers have a well-defined class of inputs and outputs.

    For AI these issues are amplified a lot. They are non-deterministic and unbounded in what layer of software they operate on or produce. I'd argue every developer who uses AI needs to understand software architecture, approaches to software development, and actually read and understand the code that the AI produced, at a minimum. Otherwise the whole industry will become saturated with and built on top of code no-one understands or can maintain, and it will literally collapse in on itself at some point. Carefully reviewed, selected, maintained code has always been precious, it will become a golden nugget in a sea of pig manure.

  • source
  • parent
  • hideshow 2 child comments
  • [–] -1 points 1 month ago

    It can’t really write maintainable code without a lot of re-prompting and corrections.

    Which is a skillset being learned. One which users are presumably better at than non-users, since they're practicing it. If the chatbot-that-codes Just Worked, there'd be nothing to discuss; we could consider human coding successfully completed. The people who don't move up to proper computer science can get on with whatever they wanted software for. We only teach them all of this because they've got shit to do, and up until now, it's been really really hard. Like if beginner astronomy meant telescope engineering.

    Already the key complaint has become "maintainability." That's quite a high-level criticism. When I sass specific compilers, it's for using register-juggling macros that could have been one hardware instruction... not for adding a feature from a one-sentence description, but in a way that will complicate any future refactor. Or would, if refactoring was not also something you can tell the chatbot to do.

    Compiler developers are a hardened core of ultranerds. I couldn't do it above a toy level. If I needed to understand how they work, in detail, then I would be in trouble. Thankfully it is sufficient to abstract all of their work into 'C goes in ARM comes out.' Or at least to mumble about intermediate representations and distract people with Godbolt before running away. Sure, 'add a button above the widget' is more pluripotent than a K&R-standard Hello World, but even the foundation you celebrate is layer upon layer of Don't Worry About It.

    AI coding right now is a blunt instrument. Those often suffice. And this one can already be used to remove layers. To obviate a fat framework. To translate to a faster language. To golf. Or it could format your hard drive if a website tells it to, IDFK. It is a higher class of footgun. We take those.

  • source
  • parent
  • load more comments
    view more: next ›
    13 comments in c/fuck_ai@lemmy.world view that post