• punrca@piefed.world
    link
    fedilink
    English
    arrow-up
    73
    ·
    2 days ago

    The software engineer acknowledged that AI tools can help improve productivity if used properly, but for programmers with relatively limited experience, he feels the harm is greater than the benefit. Most of the junior developers at the company, he explained, don’t remember the syntax of the language they’re using due to their overreliance on Cursor.

    Good luck for the future developers I guess.

    companies that’ve spent money on AI enterprise licenses need to show some sort of ROI to the bean-counters. Hence, mandates.

    Can’t wait for AI bubble to pop. If this continues, expect more incidents/outages due to AI generated slop code in the future.

    • FreedomAdvocate@lemmy.net.au
      link
      fedilink
      English
      arrow-up
      3
      ·
      6 hours ago

      Future developers will still have to learn the basics. Calculators existing doesn’t mean people aren’t taught basic maths, does it?

    • scarabic@lemmy.world
      link
      fedilink
      English
      arrow-up
      10
      arrow-down
      5
      ·
      edit-2
      1 day ago

      From what I see, the current is beginning to turn a little toward valuing senior devs more than ever, because they can deal with the downsides of AI. Junior devs, on the other hand, cannot, and their simpler coding work is also more easily replaced by AI. So we’ll see fewer junior dev jobs, but seniors might do fine. I’m not sure that’s good news for the profession as a whole, but its been an extremely long gold rush into software and online services so some correction probably won’t be the end of the trade.

      Oh and yes senior devs are still hounded to use AI, because it will get them further, faster. And there are no more junior devs to help. In the hands of a skilled dev, AI tools can be powerful, and they can spare some toil, and help them find their feet in less familiar frameworks and in foreign codebases.

      • FreedomAdvocate@lemmy.net.au
        link
        fedilink
        English
        arrow-up
        1
        ·
        6 hours ago

        💯💯💯💯💯💯💯💯

        A good developer learns the tools that are available and uses them appropriately. A bad developer refuses to learn new tools and will be replaced by someone who already did.

      • aesthelete@lemmy.world
        link
        fedilink
        English
        arrow-up
        25
        arrow-down
        1
        ·
        edit-2
        1 day ago

        The problems in software still remain the same though:

        (1) Bureaucracy

        (2) Needless process

        (3) Pointy headed managers

        (4) Siloed teams

        (5) Product people who have no idea what they want to build

        (6) Shitty, poorly performing legacy code nobody wants to touch

        Honestly, AI is just the latest thing that can boost your productivity at starting up some random app. But that was never the difficult part anyway.

        • scarabic@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          14 hours ago

          We are pushing our product managers to communicate their requirements with live prototypes rather than PRDs and mockups. It forces them to actually think their ideas through, and even allows them to get some hallway feedback before even bothering an eng. This might help with #5. But I’ve never had sympathy for engineers who think all the process around them is net negative, because nothings ever stopped engineers from striking out on their own, without all that, and making great businesses. If your PM and VPs are bringing you down, go it alone. If you can’t pull that together into a paycheck then maybe it’s not all as useless as some say.

          • aesthelete@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            edit-2
            3 hours ago

            But I’ve never had sympathy for engineers who think all the process around them is net negative, because nothings ever stopped engineers from striking out on their own, without all that, and making great businesses.

            Not all process is pointless, but needless process by definition is. There are also a shit ton of things that stop engineers from “striking out on their own”.

            If your PM and VPs are bringing you down, go it alone. If you can’t pull that together into a paycheck then maybe it’s not all as useless as some say.

            The whole talk of “go[ing] it alone” kinda strikes me as “bootstrapping”, libertarian non-sense.

            I don’t want to do marketing, sales, finance, legal, and product bullshit myself. That’s why I’m an employee.

            Two things can be true at the same time, for instance, a company can have a lot of bloated, needless process that stifles people and still pull in enough money to be able to pay for their employees to live a life.

            With the amount of market concentration there is in every sector as far as the eye can see, nearly every software-producing company has a cash cow of some sort, and then has a bunch of complete money losers that are subsidized by that cash cow.

            So, it’s completely possible that the company overall fully sucks and hasn’t developed anything new of value to someone in decades, but the legacy business keeps the miserable employees from the bread line.

            To return to the point, AI doesn’t solve any of this or even help with it.

        • squaresinger@lemmy.world
          link
          fedilink
          English
          arrow-up
          14
          ·
          1 day ago

          This, so much this.

          When I think about what limited my performance in the last year it was mostly:

          • Having to get 5 signatures before I am allowed the budget to install some FOSS software on my work PC that the corporation has already approved for use on work PCs
          • Spending 8 months working on a huge feature that was scrapped after 8 months of development
          • Being told that no, we cannot work on another large feature request (of which there are many in the pipeline) because our team said we can only fit that scrapped feature into this year and we are not allowed to replan based on the fact that the feature we were supposed to work on got scrapped by business

          And then they tell us to return to office and use AI for increasing efficiency.

          It’s all an elaborate play performed by upper management to feign being in control and being busy with something. Nobody is actually interested in producing a product, they all just want to further their own position.