Login
You're viewing the front-end.social public feed.
  • Jan 31, 2026, 5:17 PM

    "AI" is not actually a technology, in the way people would commonly understand that term.

    If you're feeling extremely generous, you could say that AI is a marketing term for a loose and shifting bundle of technologies that have specific useful applications.

    I am not feeling so generous.

    AI is a technocratic political project for the purpose of industrializing knowledge work. The details of how it works are a distant secondary concern to the effect it has, which is to enclose and capture all knowledge work and make it dependent on capital.

    💬 7🔄 330⭐ 521

Replies

  • Jan 31, 2026, 5:25 PM

    So, back to the paper.

    "How AI Impacts Skill Formation"
    arxiv.org/abs/2601.20245

    The very first sentence of the abstract:

    > AI assistance produces significant productivity gains across professional domains, particularly for novice workers.

    1. The evidence for this is mixed, and the effect is small.
    2. That's not even the purpose of this study. The design of the study doesn't support drawing conclusions in this area.

    Of course, the authors will repeat this claim frequently. Which brings us back to MY priors, which is that this is largely a political document.

    💬 5🔄 36⭐ 97
  • 💬 1🔄 0⭐ 12
  • Jan 31, 2026, 8:03 PM

    I have eaten. I may be _slightly_ less cranky.

    Ok! The results section! For the paper "How AI Impacts Skill Formation"

    > we design a coding task and evaluation around a relatively new asynchronous Python library and conduct randomized experiments to understand the impact
    of AI assistance on task completion time and skill development

    ...

    Task completion time. Right. So, unless the difference is large enough that it could change whether or not people can learn things at all in a given practice or instructional period, I don't know why we're concerned with task completion time.

    Well, I mean, I have a theory. It's because "AI makes you more productive" is the central justification behind the political project, and this is largely a political document.

    💬 3🔄 6⭐ 50
  • Jan 31, 2026, 8:13 PM

    > We find that using AI assistance to complete
    tasks that involve this new library resulted in a reduction in the evaluation score by 17% or two grade
    points (Cohen’s d = 0.738, p = 0.010). Meanwhile, we did not find a statistically significant acceleration in
    completion time with AI assistance.

    I mean, that's an enormous effect. I'm very interested in the methods section, now.

    > Through an in-depth qualitative analysis where we watch the screen recordings of every participant in our
    main study, we explain the lack of AI productivity improvement through the additional time some participants
    invested in interacting with the AI assistant.

    ...

    Is this about learning, or is it about productivity!? God.

    > We attribute the gains in skill development of the control group to the process of encountering and subsequently resolving errors independently

    Hm. Learning with instruction is generally more effective than learning through struggle. A surface level read would suggest that the stochastic chatbot actually has a counter-instructional effect. But again, we'll see what the methods actually are.

    Edit: I should say, doing things with feedback from an instructor generally has better learning outcomes than doing things in isolation. I phrased that badly.

    💬 5🔄 4⭐ 41
  • Jan 31, 2026, 8:26 PM

    They reference these figures a lot, so I'll make sure to include them here.

    > Figure 1: Overview of results: (Left) We find a significant decrease in library-specific skills (conceptual
    understanding, code reading, and debugging) among workers using AI assistance for completing tasks with a
    new python library. (Right) We categorize AI usage patterns and found three high skill development patterns
    where participants stay cognitively engaged when using AI assistance

    Two charts, with error bars on "The Impact of AI Assistance on Coding Speed and Knowledge Quiz"

First: Task Time. with a p = 0.391 confidence. With AI took 19.5 - 25.5 minutes. Without AI took 21.5 - 27.5 minutes.

Second: Quiz Score %, with a p = 0.010 confidence. With AI scored ~40% - 59%. Without AI scored ~59% - ~72%
    A chart of AI usage patterns, relative to quiz score and completion time.

"Generation-then-comprehension": 24 minutes, 86% score.
"Hybrid-code-explanation": 24 minutes, 68% score.
"Conceptual Inquiry": 22 minutes, 65% score.
"AI Delegation" 19.5 minutes, 39% score.
"Progressive AI reliance": 22 minutes, 35% score.
"Iterative AI Debugging": 31 minutes, 24% score.

There are no ranges or confidence intervals given.
    💬 2🔄 2⭐ 22
  • Jan 31, 2026, 8:34 PM

    > As AI development progresses, the problem of supervising more and more capable AI systems becomes more difficult if humans have weaker abilities to understand code [Bowman et al., 2022]. When complex software tasks require human-AI collaboration,
    humans still need to understand the basic concepts of code development even if their software skills are
    complementary to the strengths of AI [Wang et al., 2020].

    Right, sure. Except, there is actually a third option. But it's one that seems inconceivable to the authors. That is to not use AI in this context. I'm not even necessarily arguing* that's better. But if this is supposed to be sincere scholarship, how is that not even under consideration?

    *well, I am arguing that, in the context of AI as a political project. If you had similar programs that were developed and deployed in a way that empowers people, rather than disempowers them, this would be a very different conversation. Of course, I would also argue that very same political project is why it's inconceivable to the authors, soooo

    💬 1🔄 6⭐ 47
  • Jan 31, 2026, 8:55 PM

    And then we switch back to background context. We get a 11 sentences of AI = productivity. Then 3 sentences on "cognitive offloading". 4 sentences on skill retention. And 4 on "over reliance". So, fully 50% of the background section of the "AI Impacts on Skill Formation" paper is about productivity.

    💬 2🔄 1⭐ 26
  • Jan 31, 2026, 9:12 PM

    Chapter 3. Framework.

    Finally.

    Paraphrasing a little: "the learning by doing" philosphy connects completing real world tasks with learning new concepts and developing new skills. Experiental learning has also been explored to mimic solving real world problems. We focus on settings where workers must acquire new skills to complete tasks. We seek to understand both the impact of AI on productivity
    and skill formation. We ask whether AI assistance presents a tradeoff between immediate productivity and longer-term skill development or if AI assistance presents a shortcut to enhance both.

    Right. There it is again: productivity. Even within this framing, there are at least 3 more possibilities. That AI does not actually increase productivity; that AI has no effect at all; or that AI improves learning only. I think it's very telling that the authors don't even conceive of these options. Particularly the last one.

    But I'm becoming more and more convinced that the framing of productivity as an essential factor to measure and judge by is itself the whole purpose of this paper. And, specifically, productivity as defined by production output. But maybe I'm getting ahead of myself.

    💬 1🔄 3⭐ 26
  • Jan 31, 2026, 9:18 PM

    And now we have actual research questions! It feels like it shouldn't take this long to get these, but w/e

    1. Does AI assistance improve task completion productivity when new skills are required?
    2. How does using AI assistance affect the development of these new skills?

    We'll learn how the authors propose to answer these questions in the next chapter: Methods.

    But first, there is a 6 year old in here demanding I play minecraft, and I'd rather do that.

    To be continued... probbaly

    💬 2🔄 0⭐ 35
  • Feb 1, 2026, 1:24 AM

    Chapter 4. Methods.

    Let's go

    First, the task. It's uh. It's basically a shitty whiteboard coding interview. The assignment is to build a couple of demo projects for an async python library. One is a non-blocking ticker. The other is some I/O ("record retrieval", not clear if this is the local filesystem or what, but probably the local fs) with handling for missing files.

    Both are implemented in a literal white board coding interview tool. The test group gets an AI chatbot button, and encouragement to use it. The control group doesn't.

    /sigh

    I just. Come on. If you were serious about this, it would be pocket change to do an actual study

    Anthropic increased the target for their current fundraising round from $10B to $20B, according to Tech Crunch
    💬 2🔄 3⭐ 22
  • Feb 1, 2026, 5:27 AM

    Found it! n=52. wtf. I reiterate: 20 billion dollars, just for this current funding round, and they only managed to do this study with 52 people.

    But anyway, let's return to the methods themselves. They start with the design of the evaluation component, so I will too. It's organized around 4 evaluative practices they say are common in CS education. That seems fine, but their explanation for why these things are relevant is weird.

    1. Debugging. According to them "this skill is curcial for detecting when AI-generated code is incorrect and understanding why it fails.

    Maybe their definition is more expansive than it seems here? But it's been my experience, professionally, that this is just not the case. The only even sort-of reliable mechanism for detecting and understanding the shit behavior of slop code is extensive validation suites.

    💬 1🔄 5⭐ 35
  • Feb 1, 2026, 5:32 AM

    2. Code Reading. "This skill enables humans to understand and verify AI-written code before deployment."

    Again, not in my professional experience. It's just too voluminous and bland. And no one has time for that shit, even if they can make themselves do it. Plus, I haven't found anyone who can properly review slop code, because we can't operate without the assumptions of comprehension, intention, and good faith that simply do not hold in that case.

    💬 3🔄 10⭐ 68
  • Feb 1, 2026, 5:37 AM

    3. Code writing. Honestly, I don't get the impression they even understand what this means. They say "Low-level code writing, like remembering the syntax of functions, will be less important with further integration of AI coding tools
    than high-level system design."

    Neither of those things is a meaningful facet of actually writing code. Writing code exists entirely in-between those two things. Code completion tools basically eliminate having to think about syntax (but we will return to this). And system design happens in the realm of abstract behaviors and responsibilities.

    💬 2🔄 4⭐ 36
  • Feb 1, 2026, 5:42 AM

    4. Conceptual. As they put it, "Conceptual understanding is critical to assess whether AI-generated code uses appropriate design patterns that adheres to how the library should be used.

    IIIIIII guess. That's not wrong, exactly? But it's such a reverse centaur world view. I don't want to be the conceptual bounds checker for the code extruder. And I don't understand why they don't understand that.

    💬 1🔄 4⭐ 34
  • Feb 1, 2026, 5:46 AM

    So anyway, all of this is, apparently, in service to the "original motivation of developing and retaining the skills required for supervising automation."

    Which would be cool, I'd like to read that study, because it isn't this one. This study is about whether the tools used to rapidly spit out meaningless code will impact one's ability to answer questions about the code that was spat. And even then, I'm not sure the design of the study can answer that question.

    💬 2🔄 0⭐ 27
  • Feb 1, 2026, 6:11 AM

    I guess this brings me to the study design. I'm struggling a little to figure out how to talk about this. The short version is that I don't think they're testing any of the effects they think they're testing.

    So, they start with a warmup coding round, which seems to be mostly to let people become familiar with the tool. That's important, because the tool is commercial software for conducting coding interviews in a browser. They don't say which one, that I've seen.

    Then they have two separate toy projects that the subjects should complete. 1 is a non-blocking ticker, using a specific async library. 2 is some async I/O record retrieval with basic error handling, using the same async library.

    And then they take a quiz about that async library.

    But there's some very important details. The coding portion and quiz are both timed. The subjects were instructed to complete them as fast as possible. And the testing platform did not seem to have code completion or, presumably, any other modern development affordance.

    💬 1🔄 0⭐ 22
  • Feb 1, 2026, 6:21 AM

    Given all of that, I don't actually think they measured the impact of the code extruding chatbots at all. On anything. What they measured was stress. This is a stress test.

    And, to return to their notion of what "code writing" consists of: the control subjects didn't have code completion, and the test subjects did. I know this, because they said so. It came up in their pilot studies. The control group kept running out of time because they struggled with syntax for try/catch, and for string formatting. They only stopped running out of time after the researchers added specific reminders for those 2 things to the project's instructions.

    💬 1🔄 3⭐ 29
  • Feb 1, 2026, 6:26 AM

    So. The test conditions were weirdly high stress, for no particular reason the study makes clear. Or even acknowledges. The stress was *higher* on the control group. And the control group had to use inferior tooling.

    I don't see how this data can be used to support any quantitative conclusion at all.

    Qualitatively, I suspect there is some value in the clusters of AI usage patterns they observed. But that's not what anyone is talking about when they talk about this study.

    💬 1🔄 7⭐ 30
  • Feb 1, 2026, 6:32 AM

    And then there's one more detail. I'm not sure how I should be thinking about this, but it feels very relevant. All of the study subjects were recruited through a crowd working platform. That adds a whole extra concern about the subject's standing on the platform. It means that in some sense undertaking this study was their job, and the instruction given in the project brief was not just instruction to a participant in a study, but requirements given to a worker.

    I know this kind of thing is not unusual in studies like this. But it feels like a complicating factor that I can't see the edges of.

    💬 2🔄 1⭐ 21
  • Feb 1, 2026, 6:58 AM

    But now it's 1am. I may pick this up tomorrow, I'm not sure. If I do, the next chapter is their analysis. Seems like there would be things in there that merit comment

    💬 2🔄 0⭐ 4
  • Jan 31, 2026, 5:48 PM

    @jenniferplusplus I like the fact that their own research doesn't fit their lazy claim you reference, and they spend a lot of time trying to work out how the claim can be true, even though their own evidence is against it (and more in line with the mixed evidence in the literature, as you say).

    💬 1🔄 1⭐ 8
  • Jan 31, 2026, 5:57 PM

    @jenniferplusplus it reminds me a bit of the famous thing with the Flat Earth Society people who spent $20k on an expensive laser gyroscope to "prove" that the Earth was not a rotating sphere... and then spent a lot of time being very confused and upset when, of course, it measured precisely what you'd expect from a rotating spherical Earth.

    💬 1🔄 0⭐ 3
  • Feb 7, 2026, 7:46 PM

    @aoanla @jenniferplusplus I was baffled that Anthropic published this paper, let alone promoted it on their blog. Cos even their headline results say "AI coding bots are shit, don't use them, they're no faster and they make you stupid". But yeah, they thought they were saying things about productivity.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 1
  • 💬 2🔄 18⭐ 27
  • 💬 0🔄 0⭐ 4
  • 💬 1🔄 0⭐ 0
  • Feb 1, 2026, 2:17 PM

    @mirabilos @jenniferplusplus

    Yes, just the usual dreary confirmation of what we mostly know about "LLMs don't work for fact-based professions."

    The surprise, if any, is just how *hard* managers fantasize otherwise.

    💬 0🔄 1⭐ 0
  • Feb 1, 2026, 2:31 AM

    @jenniferplusplus thank you so much for doing this. I skimmed and just couldn’t bring myself to read it all, and it’s nice to see someone doing a much deeper read but coming to largely the same conclusions.

    💬 1🔄 1⭐ 11
  • Feb 1, 2026, 2:49 AM

    @glyph i would do this more, but the format of academic papers is so cumbersome. The time I actually have available for it is on the couch, after the kid's in bed. But reading these things on a phone is basically impossible

    💬 2🔄 0⭐ 10
  • Feb 1, 2026, 3:03 AM

    @jenniferplusplus @glyph I had only read the anthropic summary. I was struck by how even if all their methods and study design were great (& a good sample etc) the results seemed to very much indicate LLM use isn't as transformative as the hype with major risks of deskilling impacts. I was surprised they published it just reading their own summary. I guess they had to make lemonade from lemons??

    💬 2🔄 0⭐ 8
  • 💬 0🔄 1⭐ 5
  • Feb 1, 2026, 5:17 AM

    @r343l @glyph
    As I've learned, they did some preregistration for the study. That might have influenced them.

    And, a whole bunch of these ai researchers really do seem to think of themselves as serious scientists doing important work. Particularly at anthropic, as that's where a lot of the true believers ended up

    💬 0🔄 0⭐ 9
  • 💬 0🔄 0⭐ 2
  • Feb 1, 2026, 5:35 AM

    @jenniferplusplus the latter part is especially true and i don't have any sort of strategy for handling it. i have to read every single line of LLM code because the space of possible mistakes it can make is so large. with humans, even if someone really doesn't know what they are doing, there are only so many kinds of things that could conceivably screw up.

    💬 0🔄 1⭐ 8
  • Feb 1, 2026, 6:01 AM

    @jenniferplusplus That paper is _extremely damning_ of the use of AI for all that it bends over backwards and ties itself into knots to try to find some way of making it seem less catastrophically bad.

    💬 1🔄 1⭐ 8
  • Feb 1, 2026, 6:02 AM

    @hrefna it certainly doesn't make them look good. But I'm honestly not sure we can draw *any* conclusion from this study. Which I'm getting into now

    💬 0🔄 1⭐ 5
  • 💬 0🔄 0⭐ 3
  • Feb 1, 2026, 5:53 AM

    @jenniferplusplus Kind of a funny statement given that the whole point of abstraction, encapsulation, high level languages, etc. is to provide a formal basis for much of a program to be designed in terms of high level concepts

    💬 1🔄 0⭐ 1
  • Feb 1, 2026, 6:53 AM

    @jsbarretto That's not what people mean when they say system design.

    They mean which way do dependencies flow. What is the scope of responsibility for this thing. How will it communicate with other things. How does the collection of things remain in a consistent state.

    For example.

    💬 1🔄 0⭐ 1
  • Feb 1, 2026, 10:43 AM

    @jenniferplusplus Yeah, I get that. I've been around the block. I'm saying it's bizarre that the paper seems to be implying that AI might be a route towards automating the production of lower level code when this has been the goal of pretty much every form of developer tooling since forever.

    💬 0🔄 0⭐ 1
  • Feb 2, 2026, 1:04 AM

    @jenniferplusplus
    Why is that any different from reviewing slop code written by incompetents? Most foss maintainers have to deal with some of that too...

    [Agreeing with most of what you're saying, btw]

    💬 0🔄 0⭐ 0
  • Jan 31, 2026, 9:14 PM

    @jenniferplusplus

    I love how the introduction already frames the industrial revolution all wrong. Product lines were all about de-skilling people, by turning artisans into factory workers.

    Then comparing factory work with software development. When software development is the exact opposite.

    Maybe those authors should visit a real factory and talk to some real engineers.

    And I find it absolutely fascinating how they talk about "professional domains", when all they mean is "software development".

    (Not even through the first page and already feeling the need to vent, sorry.)

    💬 0🔄 0⭐ 6
  • Jan 31, 2026, 8:26 PM

    @jenniferplusplus

    > Learning with instruction is generally more effective than learning through struggle.

    I don’t think this is necessarily a true statement? Guided learning beats unproductive struggle, but learning through struggle that eventually succeed produces far better retention etc than guided learning that becomes passive/receptive. There’s a huge literature on this that I’m not up on at all, but I’m pretty sure it doesn’t break cleanly along that particular line.

    (I don’t think my quibble derails your larger train of thought here)

    💬 3🔄 1⭐ 12
  • Jan 31, 2026, 8:34 PM

    @inthehands @jenniferplusplus I would say that regardless whether guided learning from an entity that actually knows the material or independent learning tested against reality both best working with jumped-up autocorrect. The machine will tell you that you’re doing great things while spitting out garbage—counter-instructional is certainly one way to put it.

    💬 1🔄 1⭐ 3
  • Jan 31, 2026, 8:38 PM

    @c0dec0dec0de @inthehands @jenniferplusplus I think the problem is actually *engagement* - as well as correct challenge, learning requires active engagement with material (and effort to internalise it). Getting an LLM etc to "help" tends to reward disengagement (as well as potentially allowing you to "reduce the challenge" to the point where you're not actually doing anything hard yourself).

    💬 0🔄 0⭐ 4
  • Jan 31, 2026, 8:38 PM

    @inthehands @jenniferplusplus One of my personal hesitance to use the LLM tools much (despite incredible professional pressure to do so) is that my use of it (again, under professional necessity) has re-enforced my pre-existing belief that struggling through a problem, debugging and digging through source and so on has been CRITICAL to my skill development. It is something I have for (uh) 15+ years told less experienced software developers is critical to getting better / faster!

    💬 2🔄 1⭐ 12
  • Jan 31, 2026, 8:40 PM

    @inthehands @jenniferplusplus Maybe there is a way to use things like Claude Code in ways that don’t disrupt this struggle learning pattern. This is one thing I’ve been trying to work out for myself! But so far I’ve not seen much about this concern or how the tools could be used in a way that results in the equivalent learning.

    💬 0🔄 0⭐ 1
  • Jan 31, 2026, 9:18 PM

    @r343l @inthehands @jenniferplusplus
    “struggling through a problem, debugging & digging through source & so on has been CRITICAL to my skill development” … because the “cognitive struggle” is like doing physical exercise or activity to get your body and brain better + faster doing it.
    Making a request & waiting for the output result is like ordering a meal from a restaurant menu & somehow expecting that action to make you an expert Chef. At most, you become an expert at ordering off a menu.

    💬 0🔄 0⭐ 9
  • 💬 1🔄 0⭐ 4
  • 💬 0🔄 1⭐ 4
  • Jan 31, 2026, 9:05 PM

    @jenniferplusplus "Learning with instruction is generally more effective than learning through struggle"

    I'm not sure I agree! Desirable difficulties literature and metacognition lit both agree short term failures can lead to better long term retention (people's lack of belief in this is often pointed to as a reason we engage in inefficient problem solving). That is one reason project based learning can sometimes beat sage on a stage lectures

    Eg classic lit here: bjorklab.psych.ucla.edu/wp-con

    💬 1🔄 0⭐ 9
  • Jan 31, 2026, 9:26 PM

    @grimalkina I think I phrased that badly. I'm aware and agree that doing a thing, mistakes and all, is very often has better learning outcomes than lectures from experts.

    What I meant was doing a thing with guidance and feedback from an expert has better outcomes than doing it in isolation.

    💬 0🔄 0⭐ 5
  • Jan 31, 2026, 9:36 PM

    @jenniferplusplus I think the 'control group' here didn't use AI at all. At least that's how I read it. And they completed the task in more or less the same time and two grades better results.

    💬 1🔄 0⭐ 2
  • 💬 0🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Feb 1, 2026, 6:41 AM

    @realn2s Lower grades are, indeed, worse.

    The AI did seem to speed things up, but not enough to achieve statistical significance. And as I describe further down the thread (just now, not suggesting you didn't read far enough), the AI chatbot seems to have been the only supportive tooling that was available. So it's not so much the difference between AI or not, as the difference between support tools or not.

    💬 1🔄 0⭐ 1
  • Feb 1, 2026, 7:03 AM

    @jenniferplusplus
    🙏🏻
    I indeed asked the question before i had finished the thread 😬
    I was very confused and in some ways still are.
    How can the authors of the paper think all this is an argument for AI (which I believe they do)?

    💬 1🔄 0⭐ 1
  • Feb 1, 2026, 7:11 AM

    @realn2s I said elsewhere that I think the main goal of the paper is to reinforce the notion that the speed and volume (regardless of quality or correctness) of production is a necessary factor to consider related to AI, and that more is necessarily and unambiguously better.

    So, that it seems to interfere with learning must be a "tradeoff" and not a "deal breaker". To the extent this study can support any conclusion at all, that is. I think it's a quite a bad study.

    Additionally, it seems like a move toward blaming people for their own deskilling. If there's a way to use these things and _not_ suffer learning loss, then anyone who _does_ must be individually to blame.

    💬 0🔄 0⭐ 2
  • Jan 31, 2026, 8:44 PM

    @jenniferplusplus you have inspired me to read it as well (over beer and pizza) and .. yeah, what she said. I think i gave up before the results section. i did feel that the prep-work to calibrate the experiment (e.g the local item dependence in the quiz) was pretty well done, but i will defer to any sociologist who says otherwise.

    Why is all the so-called productivity in the paper at all?

    💬 0🔄 0⭐ 1