• Sabbo [it/its]@hexbear.net
    link
    fedilink
    English
    arrow-up
    5
    ·
    5 hours ago

    Alright everybody! It was a good run. This time let’s account for the Y2K issue from the start, and I’m thinking we try trinary again, I think we can do it this time.

  • none [none/use name]@hexbear.net
    link
    fedilink
    English
    arrow-up
    23
    arrow-down
    2
    ·
    10 hours ago

    I really dislike how everything this man says or does is interpreted like it is instruction from god.

    If Linus torvalds jumped off a bridge, half the Linux nerds would line up to do the same.

  • queermunist she/her@lemmy.ml
    link
    fedilink
    English
    arrow-up
    46
    arrow-down
    1
    ·
    edit-2
    14 hours ago

    I can’t wait for no one to know how any of our software works in ten years, why it’s so bloated, or why it breaks all the time.

  • Awoo [she/her]@hexbear.net
    link
    fedilink
    English
    arrow-up
    60
    ·
    edit-2
    15 hours ago

    I actually disagree with a lot of people here.

    If you allow llm to infect code, you will have no programmers that can code once your pre-ai ones (like linus) phase out.

    It’s not really ai that is the problem but the skills it eliminates. You can’t properly fix bad ai code if you don’t do code without ai, you will not gain the experience of decades of manually coding properly.

    The most experienced coders that exist today are the equivalent of artisanal stone carvers and wood workers who built some of the most beautiful buildings that exist of older times. Modern construction methods phased them out and now the number of people with their skill is tiny worldwide compared to thousands of them in every country in the past.

    The tech industry is going to eat itself and won’t realise until it’s too late.

    • Ekranoplane [none/use name]@hexbear.net
      link
      fedilink
      English
      arrow-up
      22
      arrow-down
      5
      ·
      13 hours ago

      Okay but 99% of corporate codebases are already insane crap. The LLMs write boring, overly safe code, but at least they don’t make obvious IDOR bugs like my human coworkers.

      • Awoo [she/her]@hexbear.net
        link
        fedilink
        English
        arrow-up
        22
        arrow-down
        1
        ·
        edit-2
        12 hours ago

        Yeah but when you’re gone nobody is going to even be able to tell the difference between one set of code or the other. Instead the competent programmers will be replaced with tech priests preaching to the machine.

        Embracing this technology eliminates competency. Consider how the art industry is currently refusing to embrace it and instead fighting it, what does this do? It ensures that the future has artists who remain competent and does not turn the field of art into a bunch of people who give prompts to an AI.

        To really understand this you need to imagine a future where the art field embraced AI and all manual art stops, instead being replaced by people that give prompts to AI to make art. This is the future of the programming field by embracing AI. All future programmers when the manual programmers phase out will just be people that only know how to prompt.

        It is incredibly shortsighted and only the realisation that everyone in the field will become like ai “artists” once the current experience phases out really makes this clear. It will suffer a total skill collapse.

        • Ekranoplane [none/use name]@hexbear.net
          link
          fedilink
          English
          arrow-up
          8
          arrow-down
          1
          ·
          11 hours ago

          But the art field is making final products that have no formal correctness. The programming field is making infrastructure that never gets seen by end users, and we do have formal verification. Two completely different things.

          The skill collapse already happened after the 90s which is why all the software is so shit right now. Now the competent people can take over again and rewrite everything in immutable functional languages with complete unit test coverage and viral copyleft licenses.

    • zedcell@lemmygrad.ml
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      2
      ·
      12 hours ago

      But hidden in what you’ve said about construction is that the world moves on and we can now build things faster and more affordably than ever.

      This is a very aristocratic ‘Marxist’ take, denying the value of a technology because of its deskilling potential. Truth is every major technological revolution was accompanied by the same misguided doomerism.

      And I hate like 95% of what LLMs are being used for and what they produce, for what it’s worth. I just think this argument is a bad and potentially dangerous one to make.

      • Awoo [she/her]@hexbear.net
        link
        fedilink
        English
        arrow-up
        13
        ·
        11 hours ago

        That argument makes sense for construction, it does not make sense for technology.

        What do you value more? Innovating new things or mass producing already-existing things?

        I particularly don’t enjoy the argument I’m being “aristocratic”. The skills in this field currently exist incredibly broadly, making them accessible even to the average person with huge communities of people capable of teaching and helping one another advance in the craft. When you deskill the field you make it so that the only people with access to those skills are the bourgeoisie, in the future the extreme few people with those skills will be buried away in highly advanced private research institutes and no such community will exist anymore. Those people will be doing much the same thing that this field is currently doing at even the average level of programmer, except it will be prestigious and overblown due to the rarity of the skill, and the quantity of genuinely new things will be far far smaller because they will only be coming out of those organisations, and they will only be private.

        If you deskill the entire field say goodbye to anything new and innovative being open source ever again.

        • zedcell@lemmygrad.ml
          link
          fedilink
          English
          arrow-up
          4
          arrow-down
          2
          ·
          11 hours ago

          Again, held in your statement smuggled in behind the argument is another important wedge. The unmoving and unchanging state of ownership and the permanence of bourgeois rule is presupposed by your argument. Not very communist, and not particularly dialectical in approach.

          • infuziSporg [e/em/eir]@hexbear.net
            link
            fedilink
            English
            arrow-up
            2
            ·
            2 hours ago

            The unmoving and unchanging state of ownership and the permanence of bourgeois rule is presupposed by your argument.

            You are trying to prove the insufficiency of an argument by making a counterargument that is even more insufficient.

            We have seen centuries of proto-capitalism, centuries of early capitalism, a century of conflict between hegemonic capitalism and socialism in which the majority of communist gains and inroads were turned back by the bourgeoisie. Bourgeois rule is chaotic and systematically self-reproducing (like the rule of nobility was), but the historical sample and trajectory does not suggest its imminent defeat by the proletariat.

            As technology advances, so too do the mechanisms of social control. Global capitalism has proven its ability to adapt to change and subsume any threats, and we are now facing a potentially species-ending polycrisis. You can’t simply wave your hand and say “Marx assures us this specific outcome will happen, therefore the workers will be in control over AI”. It’s 100% counterfactual.

            Having a fully informed perspective, or a clear foundation, for all of human technology is what Awoo is arguing for.

          • Awoo [she/her]@hexbear.net
            link
            fedilink
            English
            arrow-up
            6
            arrow-down
            2
            ·
            8 hours ago

            This argument is just longtermism, and Elon Musk cites it regularly to defend against any and all criticisms of newly developing technology. All harms in the present are fine and good because in the inevitable future we are going to create everything will be better!

            You want to claim I’m not thinking like a communist and I’m not being dialectical. Yet your yourself are supporting a position that opposes struggle whereas I stand with using struggle in all of its forms, and the radical change of a form of production such as the mass automation of previously manual labour in programming that AI represents is certainly a theater of struggle.

          • none [none/use name]@hexbear.net
            link
            fedilink
            English
            arrow-up
            9
            ·
            10 hours ago

            unmoving and unchanging state of ownership and the permanence of bourgeois rule is presupposed

            Are you saying that Awoo has a negative attitude towards AI because they aren’t taking into account a possible future where we have revolutions, or otherwise seize the means of production? They are negating the agency of the working class to become organized, then fix the problems they raise? And since this might happen, it is treasonous against the future society to raise and perhaps even attempt to address the problems as they present themselves now?

            It reminds me of that tech ideology (effective altruism? Or another one?) where they consider all potential future people as valuae as currently living people. So anything done today can be justified if in their theoretical future, it might result in an increase of humans.

            • zedcell@lemmygrad.ml
              link
              fedilink
              English
              arrow-up
              3
              arrow-down
              2
              ·
              8 hours ago

              Is this how you read Capital? Snarking at any time Marx saw the silver lining in the creation of the industrial proletariat and the massive improvement in the concentration and power of industry like the chapter on cooperation?

              I just find it really short sighted and un-marxist, clinging to a version of the world now instead of fighting for a better one that is possible if we work together. You all have a very pessimistic view of the world.

                • zedcell@lemmygrad.ml
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  7 hours ago

                  I assume you want me to say labour.

                  But Communism is meant to stand above the battle for supremacy between the proletariat and the bourgeoisie, which, taken alone, is the realm of chartism and trade unionism.

                  Taken dialectically, the mass unemployment of a strata of workers also causes massive repercussions for the stability of the capitalist system. Without workers earning wages, an integral part of the the circulation of capital, that of the reproduction of variable capital I.e. the consumption of goods and services by the proletariat is interrupted. This then causes shockwaves in the form of crises of overproduction that throw even more people into poverty, joblessness and disarray. This then produces opportunities for the proletariat to fight back against a weakened system that is no longer functioning to keep them fed and placid. The attack against labour invokes its opposite, an attack of labour against capital. It is at this point the communists put forth their argument - it is not enough to wring concessions from the ruling class that put you in this mess, you must seek to transform society by their overthrowal and by the collective and democratic ownership of the means of production.

                  I can assure you that while a strike is a powerful weapon against the bourgeoisie, an uprising and revolt is certainly a greater power that doesn’t rest simply on labour downing tools and not showing up to work.

                  I understand the frustration against the way capital is wielding LLMs and similar technologies as a cudgel against tech and art workers in particular, but we have to think a level above the current clash between labour and capital. We have to think about the war not just the battle.

      • WokePalpatine [he/him]@hexbear.net
        link
        fedilink
        English
        arrow-up
        14
        arrow-down
        2
        ·
        edit-2
        11 hours ago

        They’re trying to say, in a roundabout way, that LLM bullshit is heightening alienation of workers and there are bad effects that’s going to have on the workers and society.

        Artists, more proletariat consciousness, resist LLMs, desire to not be alienated from their labour processes, care about quality of output, will likely not scapegoat political minorities for why society is worse under LLM-sloptocracy

        Dipshit tech workers, more bourgeois consciousness, embrace LLMs, accepting of alienation from the labour process, don’t care about quality of output, will project blame onto scapegoats as things get worse

        The synthesis would be non-alienated labour process where people still care about developing themselves and not just shitting out code for the market - maybe using LLMs as like a doublecheck like Spellcheck in word processors - but how long that would take IDK. China likely hasn’t even hit that stage of worker consciousness/development.

      • Awoo [she/her]@hexbear.net
        link
        fedilink
        English
        arrow-up
        14
        ·
        edit-2
        12 hours ago

        Yeah but if they don’t write code they won’t learn. A lot of coding isn’t really like learning to drive a car and once you know how you’re done, it’s a persistent lifelong accumulation of experience in architecture.

        The field absolutely will suffer a skill collapse when the existing generations of experienced pre-ai programmers phase out. There is no replacement mechanism in the system and the industry is young enough to have never even had to think about this problem ever occurring.

        • Chana [none/use name]@hexbear.net
          link
          fedilink
          English
          arrow-up
          9
          arrow-down
          1
          ·
          11 hours ago

          I’m not pro-LLM but this already happens all the time at corporate levels when the bean counters decide to fire (usually constructively dismiss) their senior talent. They have a complex codebase that captures domain specific logic well and uses good practices but then they try to have a dev team that’s half the size and 1/10th as experienced try and fail to maintain it. Then customers complain and it gets poorly patched over and over again until something important breaks and they have to stop touching entire parts of the stack or they leak a db dump or get ransomed or the site goes from 99.9999% uptime to 90%.

          I do understand that at an industry level you’re describing something like the memes where only millennials can edit a pdf because the boomers/gen x never tried to learn tech and the zoomers were never exposed to non-mobile-app workflows as kids. Where the skill itself is mostly generationally bound. But I do think the skillet will remain, just not at the corporate shovelware factories where it was already actively despised as a cost center to be done away with at the earliest opportunity. Because they already deskill there! And outsource with zero investigation of competency (not a dig at workers getting the outsourced jobs, even the ones that don’t know their stuff, because hell yeah I salute that).

          • none [none/use name]@hexbear.net
            link
            fedilink
            English
            arrow-up
            2
            ·
            10 hours ago

            Makes me think it is also representative of the trend in physical production and construction. In the US there were decades of high output. Starting nineteenth century, even more after WW2. But then everything became complacent, outsourced, unmaintained, deregulated.

            It is a general trend for sure, not a new innovation. Like elon musk doging the government. Same effect. Now all that skill is gone. Did you see the post that FBI now can now hire people with criminal records of bestiality?

            All the stuff about Iran vs US military production and capacity also. Iran was exempted from the trend due to circumstances.

            Maybe they try to eliminate the middle class as much as possible so it will not be an annoyance for them in the future.

  • Letztertod [he/him, comrade/them]@hexbear.net
    link
    fedilink
    English
    arrow-up
    24
    ·
    15 hours ago

    I don’t think it changes much of anything if linux doesn’t crash, Linus already said he will allow llm based code if it has been fully reviewed and he already said he considers it a neutral tool which is good in some instances, the fact he used it for troubleshooting isn’t that surprising or groundbreaking tbh from what was already public knowledge.

  • comrade_pibb [comrade/them]@hexbear.net
    cake
    link
    fedilink
    English
    arrow-up
    53
    arrow-down
    2
    ·
    19 hours ago

    I’ve been in software for nearly two decades. The industry has fundamentally changed with the advent of language model tools. I don’t like it, but Pandora’s box is wide open and I want to understand what the path forward is.

    I don’t write code for work anymore, I babysit a language model. Maintaining a sense of code ownership and comprehension is a real risk, and we are pushed to use tools that turn our brains into pudding.

    Is this what the old timers thought when fancy pants compilers showed up? The reason I disagree with this analogy is that the new tooling is fundamentally incompatible with software freedom that cannot be solved with gcc et al. I can’t afford a $10k computer to run local models.

    • Snort_Owl [they/them]@hexbear.net
      link
      fedilink
      English
      arrow-up
      47
      ·
      edit-2
      17 hours ago

      The idea is you’re basically expected to be a manager so the LLM is now your junior engineer except you don’t get the joy of building someone up and watching them grow you get an expensive robot that never learns and can’t remember what you said yesterday.

    • pongo1231 [none/use name]@hexbear.net
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      1
      ·
      edit-2
      12 hours ago

      I can’t afford a $10k computer to run local models.

      Tbh you don’t really need to either. With models like Qwen 3.6 35B A3B (which is quite close to the performance of frontier models from a year ago) enough of it fits onto a 8GB GPU - with the rest sitting in RAM or swapped out - to have it running at a speed that is very workable with. On my work laptop with a 4060 equivalent and llama.cpp + CUDA I get around 15-20 t/s for coding tasks. The equivalent Qwen 3.8 variant should be even better once that releases. I strongly believe small models like these running locally is going to be the way to go once the bubble bursts.

    • insurgentrat [she/her, it/its]@hexbear.net
      link
      fedilink
      English
      arrow-up
      44
      arrow-down
      1
      ·
      18 hours ago

      It’s pretty funny watching software go from arguing about functional programming, total test coverage, side effect free code, and mathematical proofs of correctness to “eh just sorta run your eyes over code you didn’t write and hope that 6 hours into your shift you’re not letting anything critical by”

      Erlang, Haskell, my beloved. I will still love you while the others are lost to a storm of madness.

    • space_comrade [he/him]@hexbear.net
      link
      fedilink
      English
      arrow-up
      23
      ·
      16 hours ago

      The reason I disagree with this analogy is that the new tooling is fundamentally incompatible with software freedom that cannot be solved with gcc et al. I can’t afford a $10k computer to run local models.

      That’s actually a good point but if we consider history the barrier to entry to software engineering was huge 40-50 years ago, not many people could afford to do it locally. Then again it’s different because software as a whole wasn’t really that important 50 years ago.

      Then again “software freedom” as we know it may just as well be a coincidental transient phenomenon because capitalist markets arranged themselves in such a way to make the hardware and software required to build and maintain software accessible enough to the general public, that “right” can conceivably be taken away by the same system again, there is no reason to assume it’s here to stay.

      Honestly I’m just rambling at this point I have no idea where any of this leads I’m pretty much hoping the whole thing is gonna be a dud and we’ll return to the same old way of doing things, capitalism is a fuck, death to america.

    • RobotToaster@mander.xyz
      link
      fedilink
      English
      arrow-up
      10
      arrow-down
      1
      ·
      18 hours ago

      I can’t afford a $10k computer to run local models.

      Hopefully that is only temporary.

      I imagine few people could afford a Unix system in 1987 when Stallman first wrote GCC.

      • Snort_Owl [they/them]@hexbear.net
        link
        fedilink
        English
        arrow-up
        20
        ·
        edit-2
        17 hours ago

        It’s not magic these models are big and you can’t just squeeze them onto smaller devices. Quantisation isn’t magic either it’s literally reducing the accuracy of a larger model to fit on a smaller device reducing its performance. If the data doesn’t exist in the model weights then the model will perform worse and you can only compress data so much. The only meaningful tech shift in the space is unified memory but it’s not going to be enough for anything this is fundamentally going to need silly quantities of ram for any effective model to run.

        • Chana [none/use name]@hexbear.net
          link
          fedilink
          English
          arrow-up
          5
          ·
          11 hours ago

          The main limitation is just RAM on the GPUs. Unfortunately the bubble itself drove up prices on that exact thing dramatically but this not a particularly expensive thing normally.

          • ashinadash [she/her]@hexbear.net
            link
            fedilink
            English
            arrow-up
            7
            ·
            10 hours ago

            normally.

            GPU prices shot up in ~2018 and 2020 and [etc] and never came back down. Nowadays a 9060XT (the useful version, mind) costs on its own what a decent entry level PC used to. We are never going back to normal.


            Remember to enable JPEG-XL support in your browser, even on your phone!

      • insurgentrat [she/her, it/its]@hexbear.net
        link
        fedilink
        English
        arrow-up
        21
        ·
        18 hours ago

        We’re at a really different point technologically and given the whole thing of Google’s paper and the architecture is more data more layers more good there is a huge incentive to run on as much ram as possible which is expensive.

        We’re not going from hand soldered resistors to nanoscale transistors again. We’re looking at some serious physics walls. Even if photonic chips leave the lab.

  • chgxvjh [he/him, comrade/them]@hexbear.net
    link
    fedilink
    English
    arrow-up
    27
    arrow-down
    1
    ·
    17 hours ago

    I don’t really care that much about whether the code I use has been made with LLMs. I don’t like working with LLMs and I don’t like working with people who heavily rely on LLMs. And since this is a matter of me volunteering my time it’s an easy decision to distance myself from projects with an everything goes LLM policy.

  • StalinistApologist [he/him]@hexbear.net
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    3
    ·
    17 hours ago

    Writing correct software, especially at a lower level, is like 10x harder than people think. It’s always been hard, and now llms can actually fix the obscure concurrency and memory safety bugs. I’m all for it.

    • space_comrade [he/him]@hexbear.net
      link
      fedilink
      English
      arrow-up
      32
      arrow-down
      1
      ·
      edit-2
      17 hours ago

      The problem is LLMs always sound very confident when “fixing” things and will very rarely report that it’s out of its depth and refuse to work, and yeah sometimes they genuinely just do good but also unless you’re really vigilant it’s easily possible it’s gonna introduce more bugs than it fixed.

      I’m not saying Torvalds is stupid enough to just uncritically let this thing loose on the kernel but I understand the trepidation of open source maintainers about this stuff.

      • Chana [none/use name]@hexbear.net
        link
        fedilink
        English
        arrow-up
        12
        arrow-down
        1
        ·
        11 hours ago

        LLMs will actually double down on incorrectness and make even wilder mistakes unless you bully them until they go, “I admit I don’t know how to do it”. Unless a reviewer really knows their stuff they can easily fall victim to trusting a bullshitting LLM.

      • comrade_pibb [comrade/them]@hexbear.net
        cake
        link
        fedilink
        English
        arrow-up
        16
        arrow-down
        2
        ·
        16 hours ago

        This is on point. You’ve got to keep pushing back until it realizes some overlooked assumptions and shit like that. I cope by architecting my codebase in a way where I know I have guardrails in place for bad LLM guesses

        • insurgentrat [she/her, it/its]@hexbear.net
          link
          fedilink
          English
          arrow-up
          29
          arrow-down
          1
          ·
          15 hours ago

          It doesn’t realise anything. It just generates a single token, appends that to its input, outputs that, ends, and starts again with the new input.

          The anthropomorphising muddies discussion.

          • space_comrade [he/him]@hexbear.net
            link
            fedilink
            English
            arrow-up
            4
            ·
            edit-2
            5 hours ago

            How do you know you’re not just generating the next token and appending it to your input? smuglord

            Nah just kidding I kinda tend to agree because techbros are already starting to speak about LLMs like they’re actual conscious beings and it’s getting super weird but saying stuff like “the text predictor that is used as a simulacrum of human reasoning is deficient in such and such ways” is kind of a mouthful and also most non-technical people are gonna stare through you if you talk to them like that.

        • Collatz_problem [comrade/them]@hexbear.net
          link
          fedilink
          English
          arrow-up
          15
          arrow-down
          1
          ·
          13 hours ago

          LLM is a statistical model, it does not reason. It is not capable of neither honesty nor deliberate lies. It works sometimes, because it was trained on thousand standard case analyses by human programmers, but it is also prone to hallucinations, which are unavoidable by design.

          • invalidusernamelol [he/him]@hexbear.net
            link
            fedilink
            English
            arrow-up
            6
            ·
            edit-2
            11 hours ago

            I know, the reason I shared that example is because there is no humanizing the LLM and it’s used exclusively for its ability to pretty effectively parse syntax to find common higher level bugs in specific C frameworks.

            For context: I never use LLMs when programming because I find them to be more of a hassle. They show me down and muddy the water on design principles.

            Even a “bad” design pattern that you’re consistent with is 1000x better than a “good” design pattern that is inconsistently applied. LLMs are fantastic at the later. Things that look great in isolation, but begin to fall apart when they come up against the weight of a larger project.

            Especially when it’s a new project without a ton of existing code for it to kinda copy/paste.

            Using one to find minor use after frees that are almost impossible to hit, or duplicated calls is fine by me though. Those are usually a pain to find anyways, and there’s almost always 100 more important things to spend time on. If someone wants to burn tokens creating a backlog of easily fixed, reproducible errors like that all while disclosing exactly what they’re using to find them sure. That’s not annoying at all, especially when they only open the PRs after discussion with the project maintainers.

          • queermunist she/her@lemmy.ml
            link
            fedilink
            English
            arrow-up
            10
            ·
            13 hours ago

            Well if you’re going to be pedantic, they don’t hallucinate either. They just repeat patterns, and sometimes false patterns can emerge in large data sets.

            • NewOldGuard@lemmy.ml
              link
              fedilink
              English
              arrow-up
              10
              ·
              11 hours ago

              Well thats not always why they give an incorrect prediction. It’s also because statistics are inherently never going to reflect reality perfectly (“all models are wrong, some are useful”), but also we intentionally inject randomness into LLMs and other ML programs to ensure the output isn’t over fitting and spitting out raw training data. Usually adjustable via seed values, temperature, etc