Login
You're viewing the discuss.systems public feed.
  • Oct 15, 2026, 5:30 PM

    It's also very frustrating to constantly have my opposition to AI be taken as an opposition to abstraction, or to automation, and a desire to do every little thing by hand. But it's the opposite. For a whole bunch of reasons, AI anti-abstracts. It adversarially creates oceans of duplication to process. It creates a situation where the AI user gets to set the terms of some ecosystem with synthetic productivity but then everyone else needs an AI to figure out what's going on in that new ecosystem.

    💬 12🔄 46⭐ 0

Replies

  • Oct 15, 2026, 5:32 PM

    Abstraction is leverage. Automation is the amplification of power. Abstraction is democratization. Automation repeats a duplicative process so you can stop thinking about it and focus on something higher level. Abstraction elides so architecture can expand.

    AI is anti-leverage. Where an abstraction will elide duplication with semantic compression, AI steamrolls the duplication by copying and pasting faster than a human can.

    💬 6🔄 15⭐ 0
  • Oct 15, 2026, 5:35 PM

    Linus is saying the quiet part out loud: AI-native projects are environments where the key ingredient is _capital_. Abstraction can be performed by a quiet appreciation. True automation can be disruptive.

    AI-based architectures (again, assuming that the AI works reliably, which is a highly contingent proposition) translate all that stuff into capital flows. A "machine speed" project requires _money_ to participate in, regardless of their complexity.

    💬 4🔄 16⭐ 0
  • Oct 15, 2026, 5:38 PM

    Right now it looks like AI can do "disruption" because you can apparently do things that require a team, as an individual, by taking advantage of highly subsidized token rates, or (at best) taking advantage of highly subsidized training regimes and stolen training data. But those rates will go up and while you'll still be able to nominally command those resources as an individual, doing so will still require the capital flow required to hire a team.

    💬 1🔄 5⭐ 0
  • Oct 15, 2026, 5:40 PM

    AI does not disrupt. AI entrenches. AI turns money into more money; AI turns investment into dependency. We are living in a funhouse mirror of that right now where the combination of overly-plausible demos and first-one's-free incentives are swamping the actual balance-sheet math. But the economics require that this stabilize, that the capital flows reverse direction. The wave has come in and we are just starting to feel the undertow.

    💬 3🔄 40⭐ 103
  • Oct 15, 2026, 6:12 PM

    This is an attempt to address the growing number of "oh, so you don't like automation when it comes for *you*? checkmate, programmers" articles out there, but there's so much more to say. Overall I think this idea that computer programmers just destroyed jobs is largely false. One of the weird corollaries of the Productivity Paradox is that we mostly *did* expand possibilities and make things better and more fun.

    (Until all the Gig Economy stuff. But that's still a minority of tech history.)

    💬 7🔄 8⭐ 45
  • Oct 15, 2026, 6:28 PM

    Also this is a big argument in the alternative. For technical reasons related to context limits and training data, none of this shit actually works well enough to replace software at any meaningful scale. To paraphrase @pluralistic by way of Jensen Huang: AI will not take your job. A boss using AI to fake their quarterly KPIs will take your job.

    💬 3🔄 37⭐ 87
  • 💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Oct 15, 2026, 5:41 PM

    @mos_8502 I'm not talking about "duplication" like disruption. I'm talking about "duplication" like hundreds of "toUpperCase" methods scattered throughout your codebase, far enough from each other that the context window can never quite reach between them. Fifty different data structures for doing the exact same things and the eventual introduction of the cartesian product of functions to convert from one to the other.

    💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Oct 15, 2026, 5:37 PM

    @glyph I've assumed well over a decade ago that eventually we'd engineer around most instances of writing code by hand. This current approach just feels like a bad way to do that. We're definitely not at the end of history, just like we weren't any of the past times engineers thought that.

    💬 2🔄 0⭐ 0
  • Oct 15, 2026, 7:11 PM

    @thomasjwebb

    I doubt we ever will.

    Computers do exactly what you tell them to. If you program them in inexact terms, they'll do something other than what you actually intended, as vibe coders are now rediscovering.

    Any reliable method of programming a computer must be logical, thorough, and unambiguous, and is therefore by definition a programming language. You'll never reliably program a computer in plain English, because plain English does not meet those requirements.

    @glyph

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Oct 15, 2026, 5:57 PM

    @glyph these were my answers for why the finance guys weren't calling bullshit on the tech guys from early into this bubble. (harder - to be fair, some did, but it didn't lead to mass consciousness bc neither of those camps really think of themselves as participating in society.) ultimately capital is very very tolerant of anything that multiplies capital, no matter how many bad consequence dominoes it's setting out ahead of the current moment. this is also why we're now at +1.5°C and rising.

    💬 1🔄 4⭐ 22
  • 💬 2🔄 1⭐ 4
  • 💬 0🔄 0⭐ 1
  • Oct 15, 2026, 6:36 PM

    @glyph "nothing about this requires that anyone be stupid or evil or unusually greedy" is great; the particular system-affinities + the optimization pressures + the accountability void is the real recipe.

    💬 0🔄 1⭐ 5
  • Oct 15, 2026, 6:16 PM

    @glyph I mean, yes and no. Reading about the final days of the typesetter trade here in Denmark is decidedly painful for a programmer with Luddite sympathies.

    💬 1🔄 1⭐ 9
  • Oct 15, 2026, 6:17 PM

    @datarama "mostly" is load-bearing. Industrial control systems also have some, uh, interesting labor relations implications.

    💬 2🔄 0⭐ 5
  • Oct 15, 2026, 6:18 PM

    @datarama But the simplistic narrative that Computers Are Just A Tool Of Capital is quantitatively incorrect overall. When you weigh the destruction of the typesetting trade against the growth of desktop publishing and the artistic possibilities of online media, the simple story of "programmers made typesetters poor so they could get rich off the difference" is a wildly reductive take on the whole thing.

    💬 1🔄 1⭐ 8
  • Oct 15, 2026, 6:26 PM

    @glyph @datarama Overall I think it's wrong to deem automation as anti-social when the processes being automated have rigorous objective metrics for whether they're being done right, and where a human operator is necessarily going to have a higher error rate. The entire perspective comes from a perverse "work ethic" worldview where it's Good for humans to be doing labor. Reducing the overall amount of labor we need is a good thing!

    Where automation is harmful is where it's replacing complex judgements, interpretations that have a lot of hidden context, and roles where there is an imperative for someone to be able to say no on ethical grounds with sloppy heuristics.

    These principles predate "AI".

    💬 1🔄 2⭐ 12
  • Oct 15, 2026, 6:42 PM

    @dalias @datarama there's a thing buried in here too where our society refuses to properly invest in retraining and employment disruption insurance programs. if you invent a miserable-shit-shoveling machine that perfectly and immaculately does the work of a miserable-shit-shoveler, immediately freeing them to do something other than miserably shoveling shit for a job, and in the course of doing this you make them homeless and despised, you can't really fix the *machine* to address that

    💬 2🔄 6⭐ 12
  • Oct 15, 2026, 6:43 PM

    @dalias @datarama everybody who does a properly obsoleted job SHOULD be given a substantial bonus, emotional hazard pay for having to reformulate their sense of self, and maybe a parade to thank them for their service for getting society to that point, instead of quiet desperate irrelevance and a probable ignominious death. but I don't know if it's quite fair to heap all that at *programmers'* feet

    💬 2🔄 9⭐ 12
  • 💬 1🔄 0⭐ 0
  • Oct 15, 2026, 9:18 PM

    @wronglang
    @glyph @dalias @datarama
    hi, it's this world. it makes sense for capitalists because the visible fate of the obsolete workers is an important part of the system that disciplines the as-yet-unobsoletr e workers. we can talk about the ethics and meaning of labor and all, but most discourse on these subjects in this society does not address this central reality, that if you fail to somehow make yourself useful to capital or its handmaiden the state, you will likely be social-murdered

    💬 0🔄 1⭐ 2
  • 💬 1🔄 1⭐ 1
  • Oct 15, 2026, 11:28 PM

    @wronglang @glyph @dalias @datarama that wasn't the intent, but it does seem to be what the incentive structure selects for. still, i know sociopaths who are good people, who scorn to ascend within that structure. the structure's the problem, and the class that it serves.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 1⭐ 1
  • Oct 15, 2026, 7:03 PM

    @glyph @dalias When I was in my late teens, if I went to a public park there'd sometimes be a bunch of people mowing the grounds, doing simple weeding work and the like. Most of them had mild-to-moderate cognitive disabilities, and this sort of "menial" work was the only thing left for them to do.

    Now they've been replaced with robot mowers - but many of them, now in their senior years, still hang around the parks, picking up bottles to collect the bottle return fee, and sometimes just cleaning up trash if they find it. They're not economically desperate or homeless (and you don't make *that* much from a day's worth of bottle returns) - virtually all of them are on disability pensions, which is a livable income here. I've talked to many of them (as I also did when they were employed and I was some young delinquent smoking weed in the park, so some of them instantly recognize the older and at least outwardly more respectable me). They do it because they like to feel useful. That at least they're contributing *something* to the community. They don't like to feel "useless".

    And honestly, this is *the same thing* I feel when I'm staring down the barrel of unemployment.

    Now, I should mention that I live in a culture with a social-democratic work ethic, which is perhaps the only thing that's even harsher than a protestant one. But it generally seems to me that many people genuinely like feeling that they're contributing something to the fellowship, and often feel bad if they're deprived of a way to do so.

    I'm not saying we should take Enoch's hammer to the robot mowers! But I'm saying that something that *to me* looks like miserable shit-shoveling might well be the thing that makes someone else feel like there's at least a small thing they can do to keep the community running. And if the last 30 years have taught me anything, it's that programmers are not necessarily the right people to make these judgment calls.

    And certainly, programmers organized in privately-owned corporations aren't.

    💬 1🔄 5⭐ 11
  • Oct 15, 2026, 7:18 PM

    @glyph @dalias Now, humans are not tools and are not made for any particular purpose, so "useless" and "useful" are not really terms that make sense to apply to people. And much as I struggle with the now-near-constant intrusive thought of viewing myself as "soon useless" because LLMs are being deployed to do things that used to be meaningful parts of my work, it is not a term I would ever apply to anyone else. So obviously there's some cognitive and emotional distortion going on here, for reasons that are probably as much personal as anything else.

    But I do think the wish to be "useful" - in the sense of providing some kind of contribution to the well-being of the community, however small - is something that sticks deeper than culture - and therefore, also deeper than the constructs of wage labour and productivity.

    Personally, aside from *seriously* not liking the thought of no longer being able to meaningfully contribute - regardless of whether I was economically comfortable on an adequate UBI - I find a very strong motivation in doing a job well. I enjoy writing good code, I take a craftsman's pride in it. This is another reason why LLMs feel like a straight-up insult - and why I was already extremely frustrated with my trade before they showed up, because the entire incentive structure has long been arrayed against the struggle for quality.

    💬 1🔄 0⭐ 6
  • 💬 0🔄 0⭐ 0
  • Oct 15, 2026, 6:33 PM

    @glyph They certainly do.

    Even things like modern shipboard instrumentation does - they don't *precisely* replicate any one particular job someone might have had in the past (a sensor readout doesn't do the same thing as a lookout did), but they do collapse enough tasks down to a point where all the residue of them can be handled by a single stressed-out person rather than a small crew.

    💬 0🔄 0⭐ 3
  • Oct 15, 2026, 7:18 PM

    @glyph @pluralistic Great summary, clarifies a lot of thoughts I've been mulling over.

    The bill that is going to come due in a year or two is going to be a real wake-up call. I suspect many codebases will be bit rotted beyond repair. It's going to make Y2K look like a walk in the park.

    💬 1🔄 1⭐ 9
  • 💬 0🔄 2⭐ 3
  • Oct 15, 2026, 8:07 PM

    @glyph thank you for the text!

    It puts substance in my feelings that AI "automation" is wrong for lack of a better word even though I think everyone's highest goal in a job should be to automate oneself away. But that is massively at odds with how jobs work, sadly, so you try that for a year, then realize you are rewarded more for creating tech debt and hiding knowledge from colleagues until some rando CEO says "no no no we're not replacing you, AI will _support_ you". It's all so fatiguing

    💬 0🔄 0⭐ 2
  • 💬 0🔄 0⭐ 0
  • Oct 15, 2026, 6:43 PM

    @glyph i have to point out that even the gig economy stuff isn't exactly of the form "automation destroying jobs", but "tech companies trying to use technology to circumvent labor laws", much like genAI effectively circumvents copyright law, but it's in this weird form that the laws were never written for, and by the time courts and laws catch up it is difficult to enforce (aka the entire shape of this "disruption" business scheme, move fast and break things, use the chaos to install yourself in essential positions so no one can easily go after you by the time the dust settles).

    programming *as a discipline* is much closer to the "it will change some jobs, and create new ones for the ones it takes" that gets often claimed for genAI (when talking to regular people, that is, to investors it's "you will soon be able to stop paying pesky humans"). engineering and science also contributed (and frankly, a lot more) to automation, but calling either engineers or scientists some sort of enemy of working people isn't a usual battle cry of the labor movement. automation is a resource *distribution* issue, where capitalists would like to pretty please like to take the lions share of the benefits (and since genAI, apparently also giant bills for hardware and energy+water usage, since how else do we get everyone to use this thing if not by selling it for a fraction of the producton price).

    💬 0🔄 2⭐ 2
  • Oct 15, 2026, 6:47 PM

    @glyph okay but ignoring all that useful shit, "oh, so you don't like automation when it comes for *you*? checkmate, programmers" is legitimately true and funny.

    💬 1🔄 0⭐ 0
  • Oct 15, 2026, 6:55 PM

    @cancername It is … not *entirely* wrong, sure. But most of the people saying it right now are only partially correct about this particular point in a broken-clock sort of way

    💬 0🔄 0⭐ 1
  • Oct 15, 2026, 7:46 PM

    @glyph

    So many programmers regularly joked about automating themselves out of a job, really it was "automate myself out of the job of 'do the thing' and into the job of 'maintain the automation that does the thing' and then 'maintain the automation that maintains the automation that does the thing'" until genAI boosters started thinking that they solved abstraction by throwing plausible words at it and started the layoffs.

    💬 0🔄 0⭐ 5
  • Oct 15, 2026, 11:09 PM

    @glyph Remember when compilers and other such foundational developer tools cost money and a lot of it? And then gcc and llvm came around and the bottom dropped out and anyone could have a high quality compiler for free. And that was seen as a good thing.

    💬 0🔄 0⭐ 0
  • Oct 16, 2026, 6:41 AM

    @glyph lucklily, I never heard that reasoning yet. When I think about automating stuff, my first instinct is to look for repeatable, "boring" stuff. So that the people doing that can do the fun, exciting stuff.

    automation is enhancement, never replacement in my opinion

    💬 0🔄 0⭐ 0
  • Oct 15, 2026, 7:08 PM

    @glyph I had a great morning reading Cedric Durand, he had no idea THIS particular flavour of it was around the corner, I bet, when he was writing. Picking up where Shoshana Zuboff leaves off.

    💬 0🔄 0⭐ 0
  • Oct 15, 2026, 5:40 PM

    @glyph Linus along with his top deputies are probably being given free access to any AI models they want.

    💬 1🔄 0⭐ 1
  • Oct 15, 2026, 5:44 PM

    @adx when a technology empowers, entrenches, and elevates the powerful at the expense of everyone else, if you're "the powerful" it starts to look like a great idea and you're not sure why everyone wouldn't be on board

    💬 1🔄 3⭐ 0
  • Oct 15, 2026, 7:16 PM

    @glyph

    Sure you are, if you bother to ask yourself whether everyone else has the same access.

    There was no call for Butlerian Jihad against microcomputers in the 1980s. Why? Because anyone could buy one!

    And Linus clearly did ask himself, because he outright said that he doesn't want people to contribute unless they have the resources to function in today's world, or something like that. It was a painfully elitist take, given that the resource in question is, first and foremost, money.

    @adx

    💬 1🔄 2⭐ 0
  • 💬 0🔄 0⭐ 1
  • Oct 15, 2026, 9:23 PM

    @0x2ba22e11

    Hmm? The VIC-20's launch price was $299.95, equivalent to $1226.52 today. Not dirt cheap, but not completely unreasonable either. You didn't need big corporate money to buy one.

    💬 1🔄 0⭐ 0
  • Oct 16, 2026, 6:46 AM

    @argv_minus_one well, my definition of "cheap" gets met a while later when it becomes possible to buy obsolete machines for peanuts secondhand, or even to dumpster dive.

    💬 0🔄 0⭐ 1
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Oct 15, 2026, 5:38 PM

    @glyph heh, funny: I've often gone for "automation is a force amplifier" but your turn of phrase there allows addressing a subtly different lens on it

    💬 0🔄 0⭐ 0
  • Vmiss_rodent@girlcock.club
    Oct 15, 2026, 5:50 PM

    @glyph LLMs also break the standard 'interchangable parts' of programming... they often end up writing whole new bespoke subroutines, systems, libraries, rather than reuse existing ones...

    Like - imagine you are automating building a car, but, every component of every car is being procedurally generated and manuactured for that speciffic car. It's the dumbest possible way to automate *building* things.

    💬 2🔄 1⭐ 0
  • Vmiss_rodent@girlcock.club
    Oct 15, 2026, 5:53 PM

    @glyph In the car example, it means you can't have, say, a mechanic come fix your engine - he's never seen any of the parts, he might be able to figure out what does what, with time, and maybe even fix it, but every single engine he tries to fix is restarting from 'figure it out from first principals',
    there's no way to easily replace a part - it's the only one, and you'd need to try to remake a new one each time it needs replacing, etc.

    💬 0🔄 0⭐ 2
  • Vmiss_rodent@girlcock.club
    Oct 15, 2026, 5:56 PM

    @glyph And each one would have it's own failure profile - "common issues" concentrated at known weak-points are a problem of standardized designs, but also become heuristics for diagnosing and fixing problems - with bespoke parts per-car, every one has it's own distinct weak points, you don't have a checklist of common issues to run through.

    💬 0🔄 0⭐ 2
  • Vmiss_rodent@girlcock.club
    Oct 15, 2026, 5:59 PM

    @glyph (and on the computers side - a weakness in a shared library, or widely-reused function means you can potentially fix it all at once, for everything using it, while bespoke code means every break needs to be done at an individual level.)

    💬 0🔄 0⭐ 2
  • Oct 15, 2026, 6:15 PM

    @miss_rodent good news! just pour an UNLIMITED amount of money on the money fire, and you can "just" have your agents fix all the duplicated bugs!

    💬 1🔄 0⭐ 0