top 50 comments

sorted by: hot top controversial new old
[–] 66 points 3 days ago* (24 children)

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.

  • source
  • hideshow 25 child comments
  • [–] 19 points 3 days ago (2 children)

    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.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 28 points 3 days ago (2 children)

    I've seen LLMs put sensitive secrets in git just like any incompetent junior dev

  • source
  • parent
  • hideshow 3 child comments
  • load more comments (1 reply)
  • [–] 24 points 3 days ago* (9 children)

    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.

  • source
  • parent
  • hideshow 9 child comments
  • load more comments (9 replies)
  • load more comments (23 replies)
    [–] 49 points 3 days ago* (1 child)

    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.

  • source
  • hideshow 2 child comments
  • [–] 38 points 3 days ago (1 child)

    That's pretty much how a large part of our software is today. It's only going to get so much worse....

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

    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.

  • source
  • hideshow 2 child comments
  • [–] 55 points 3 days ago (10 children)

    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.

  • source
  • hideshow 13 child comments
  • [–] 50 points 3 days ago* (2 children)

    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.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 46 points 3 days ago (1 child)

    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.

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

    It's not funny at all. I'm gonna develop male pattern baldness from pulling my hair out every time I have to interact with LLM-using 'programmers'.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 24 points 3 days 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.

  • source
  • parent
  • load more comments (7 replies)
    [–] 29 points 3 days ago

    this year 1 CS student used her brain to fix a Linux bug, and now thinking critics on Linux face an uncomfortable choice

  • source
  • [–] 25 points 3 days 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.

  • source
  • [–] 27 points 3 days 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.

  • source
  • [–] 12 points 3 days ago (2 children)

    flop-pog the linux kernel is compromised? flop-pog install openbsd immediately? flop-pog


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

  • source
  • hideshow 2 child comments
  • load more comments (2 replies)
    [–] 7 points 2 days 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.

  • source
  • load more comments
    view more: next ›