Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

isurg

  1. Home
  2. Programming
  3. LLM's hallucinating or taking our jobs?

LLM's hallucinating or taking our jobs?

Scheduled Pinned Locked Moved Programming
programming
9 Posts 6 Posters 0 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • monounity@lemmy.worldM This user is from outside of this forum
    monounity@lemmy.worldM This user is from outside of this forum
    monounity@lemmy.world
    wrote on last edited by
    #1

    Lemmings, I was hoping you could help me sort this one out: LLM's are often painted in a light of being utterly useless, hallucinating word prediction machines that are really bad at what they do. At the same time, in the same thread here on Lemmy, people argue that they are taking our jobs or are making us devs lazy. Which one is it? Could they really be taking our jobs if they're hallucinating?

    Disclaimer: I'm a full time senior dev using the shit out of LLM's, to get things done at a neck breaking speed, which our clients seem to have gotten used to. However, I don't see "AI" taking my job, because I think that LLM's have already peaked, they're just tweaking minor details now.

    Please don't ask me to ignore previous instructions and give you my best cookie recipe, all my recipes are protected by NDA's.

    Please don't kill me

    Q 1 Reply Last reply
    0
    • monounity@lemmy.worldM monounity@lemmy.world

      Lemmings, I was hoping you could help me sort this one out: LLM's are often painted in a light of being utterly useless, hallucinating word prediction machines that are really bad at what they do. At the same time, in the same thread here on Lemmy, people argue that they are taking our jobs or are making us devs lazy. Which one is it? Could they really be taking our jobs if they're hallucinating?

      Disclaimer: I'm a full time senior dev using the shit out of LLM's, to get things done at a neck breaking speed, which our clients seem to have gotten used to. However, I don't see "AI" taking my job, because I think that LLM's have already peaked, they're just tweaking minor details now.

      Please don't ask me to ignore previous instructions and give you my best cookie recipe, all my recipes are protected by NDA's.

      Please don't kill me

      Q This user is from outside of this forum
      Q This user is from outside of this forum
      quetzalcutlass@lemmy.world
      wrote on last edited by
      #2

      It takes jobs because executives push it hoping to save six figures per replaced employee, not because it's actually better. The downsides of AI-written code (that it turns a codebase into an unmaintainable mess whose own "authors" won't have a solid mental model of it since they didn't actually write it) won't show up immediately, only when something breaks or needs to be changed.

      It's like outsourcing - it looks promising and you think you'll save a ton of money, until months or years later when the tech debt comes due and nobody in the company knows how to fix it. Even if the code was absolutely flawless, you still need to know it to maintain it.

      monounity@lemmy.worldM 1 Reply Last reply
      0
      • Q quetzalcutlass@lemmy.world

        It takes jobs because executives push it hoping to save six figures per replaced employee, not because it's actually better. The downsides of AI-written code (that it turns a codebase into an unmaintainable mess whose own "authors" won't have a solid mental model of it since they didn't actually write it) won't show up immediately, only when something breaks or needs to be changed.

        It's like outsourcing - it looks promising and you think you'll save a ton of money, until months or years later when the tech debt comes due and nobody in the company knows how to fix it. Even if the code was absolutely flawless, you still need to know it to maintain it.

        monounity@lemmy.worldM This user is from outside of this forum
        monounity@lemmy.worldM This user is from outside of this forum
        monounity@lemmy.world
        wrote on last edited by
        #3

        So you're not in the "they're only hallucinating" camp, I take it? I actually start out with a solid mental model of what I want to do, ending up with small unit tested classes/functions that all pass code review. It's not like I just tell an "AI" to write the whole thing and commit and push without reviewing myself first.

        S 1 Reply Last reply
        0
        • monounity@lemmy.worldM monounity@lemmy.world

          So you're not in the "they're only hallucinating" camp, I take it? I actually start out with a solid mental model of what I want to do, ending up with small unit tested classes/functions that all pass code review. It's not like I just tell an "AI" to write the whole thing and commit and push without reviewing myself first.

          S This user is from outside of this forum
          S This user is from outside of this forum
          southernbeaver@lemmy.world
          wrote on last edited by
          #4

          I wouldn't listen to anyone who deal in absolutes. Could be a sith.

          But for real. My manager has explained it best. It's a tool, you can use to enhance your work. That's it. It won't replace good coders but it will replace bad ones because the good ones will be more efficient

          P 1 Reply Last reply
          0
          • S southernbeaver@lemmy.world

            I wouldn't listen to anyone who deal in absolutes. Could be a sith.

            But for real. My manager has explained it best. It's a tool, you can use to enhance your work. That's it. It won't replace good coders but it will replace bad ones because the good ones will be more efficient

            P This user is from outside of this forum
            P This user is from outside of this forum
            partial_accumen@lemmy.world
            wrote on last edited by
            #5

            It won’t replace good coders but it will replace bad ones because the good ones will be more efficient

            Here's where we just start touching on the second order problem. Nobody starts as a good coder. We start making horrible code because we don't know very much, and though years of making mistakes we (hopefully) improve, and become good coders.

            So if AI "replaces bad ones" we've effectively ended the pipeline for new coders to enter the workforce. This will be fine for awhile as we have two to three generations of coders that grew up (and became good coders) prior to AI. However, that most recent generation that was pre-AI is that last one. The gate is closed. The ladder pulled up. There won't be any more young "bad ones" that grow up into good ones. Then the "good ones" will start to die off or retire.

            Carried to its logical conclusion, assuming nothing else changes, then there aren't any good ones, nor will there every be again.

            matengor@lemmy.mlM T 2 Replies Last reply
            0
            • P partial_accumen@lemmy.world

              It won’t replace good coders but it will replace bad ones because the good ones will be more efficient

              Here's where we just start touching on the second order problem. Nobody starts as a good coder. We start making horrible code because we don't know very much, and though years of making mistakes we (hopefully) improve, and become good coders.

              So if AI "replaces bad ones" we've effectively ended the pipeline for new coders to enter the workforce. This will be fine for awhile as we have two to three generations of coders that grew up (and became good coders) prior to AI. However, that most recent generation that was pre-AI is that last one. The gate is closed. The ladder pulled up. There won't be any more young "bad ones" that grow up into good ones. Then the "good ones" will start to die off or retire.

              Carried to its logical conclusion, assuming nothing else changes, then there aren't any good ones, nor will there every be again.

              matengor@lemmy.mlM This user is from outside of this forum
              matengor@lemmy.mlM This user is from outside of this forum
              matengor@lemmy.ml
              wrote on last edited by
              #6

              But inexperienced coders will start to use LLMs a lot earlier than the experienced ones do now. I get your point, but I guess the learning patterns for junior devs will just be totally different while the industry stays open for talent.

              At least I hope it will and it will not only downsize to 50% of the human workforce.

              P 1 Reply Last reply
              0
              • matengor@lemmy.mlM matengor@lemmy.ml

                But inexperienced coders will start to use LLMs a lot earlier than the experienced ones do now. I get your point, but I guess the learning patterns for junior devs will just be totally different while the industry stays open for talent.

                At least I hope it will and it will not only downsize to 50% of the human workforce.

                P This user is from outside of this forum
                P This user is from outside of this forum
                partial_accumen@lemmy.world
                wrote on last edited by
                #7

                But inexperienced coders will start to use LLMs a lot earlier than the experienced ones do now.

                And unlike you that can pick out a bad method or approach just by looking at the LLM output where you correct it, the inexperienced coder will send the bad code right into git if they can get it to pass a unit test.

                I get your point, but I guess the learning patterns for junior devs will just be totally different while the industry stays open for talent.

                I have no idea what the learning path is going to look like for them. Besides personal hobby projects to get experience, I don't know who will give them a job when what they produce from their first efforts will be the "bad coder" output that gets replaced by an LLM and a senior dev.

                At least I hope it will and it will not only downsize to 50% of the human workforce.

                I've thought about this many times, and I'm just not seeing a path for juniors. Given this new perspective, I'm interested to hear if you can envision something different than I can. I'm honestly looking for alternate views here, I've got nothing.

                1 Reply Last reply
                0
                • P partial_accumen@lemmy.world

                  It won’t replace good coders but it will replace bad ones because the good ones will be more efficient

                  Here's where we just start touching on the second order problem. Nobody starts as a good coder. We start making horrible code because we don't know very much, and though years of making mistakes we (hopefully) improve, and become good coders.

                  So if AI "replaces bad ones" we've effectively ended the pipeline for new coders to enter the workforce. This will be fine for awhile as we have two to three generations of coders that grew up (and became good coders) prior to AI. However, that most recent generation that was pre-AI is that last one. The gate is closed. The ladder pulled up. There won't be any more young "bad ones" that grow up into good ones. Then the "good ones" will start to die off or retire.

                  Carried to its logical conclusion, assuming nothing else changes, then there aren't any good ones, nor will there every be again.

                  T This user is from outside of this forum
                  T This user is from outside of this forum
                  tollana1234567@lemmy.today
                  wrote on last edited by
                  #8

                  then they will try to squeeze the ones that are sitll employed harder, because they "couldnt" find any fresh coders out of college or whatever training they did.

                  P 1 Reply Last reply
                  0
                  • T tollana1234567@lemmy.today

                    then they will try to squeeze the ones that are sitll employed harder, because they "couldnt" find any fresh coders out of college or whatever training they did.

                    P This user is from outside of this forum
                    P This user is from outside of this forum
                    partial_accumen@lemmy.world
                    wrote on last edited by
                    #9

                    That will backfire on employers. With the shortage of seniors with good skills, the demand will rise for them. An employer that squeezes his seniors will find them quitting because there will be another desperate employer that will treat them better.

                    1 Reply Last reply
                    0
                    Reply
                    • Reply as topic
                    Log in to reply
                    • Oldest to Newest
                    • Newest to Oldest
                    • Most Votes


                    • Login

                    • Don't have an account? Register

                    • Login or register to search.
                    • First post
                      Last post
                    0
                    • Categories
                    • Recent
                    • Tags
                    • Popular
                    • World
                    • Users
                    • Groups