• T156@lemmy.world
    4·
    1 year ago

    Has that ever historically been the case? It’s usually been that a technological development results in loss of jobs, as businesses simply reduce their wage expenditure, whilst expecting the same amount, or more work.

    Like how computerisation has massively increased productivity, but wages and working hours haven’t changed to match.

  • Phoenix3875@lemmy.world
    2·
    1 year ago

    Salary and working hours have little to do with productivity though. It’s all about the workers’ negotiation power. We have many technology breakthroughs in computers that have nothing to do with AI and see where we are now.

    • Wats0ns@sh.itjust.worksOP
      1·
      1 year ago

      I’m not arguing that they haven’t little do to with productivity, I’m arguing that they shouldn’t have little to do with productivity

      • MajinBlayze@lemmy.world
        1·
        1 year ago

        Whether or not they should doesn’t matter. So long as the only real metric for success is growth of profit, these things will not happen

        There has never been a single time in the history of capitalism where improved productivity has reduced hours or increased pay for the working class.

    • b3nsn0w@pricefield.org
      1·
      1 year ago

      which language do you work with? also, what kind of code do you write?

      i do web apps in typescript, fullstack, and so many things are just layers upon layers on the same thing. you make a model, then you make a migration for that model, then a controller for a dead simple crud with just enough custom validation and shit that it’s hard to autogenerate, then swagger docs, then factories and unit tests. most of the time, i just write the model, paste it to the top of the file in a comment, then start writing the thing and the ai immediately wants to take it and do it by itself, so i just let it. there are usually a few mistakes, exactly in those hard to autogenerate places, so i fix a few and then the ai can help fix the rest with little intervention. (i do need to delete the mistake and palce the cursor, but it tends to know how to fix it). it’s been a huge time-saver for me.

      but i noticed that it’s also damn good at just generic typescript/javascript. i have it enabled pretty much all the time now and i have yet to find a task where it doesn’t speed me up, even with the weird shit i do for fun.

      however, i heard similar complaints quite a few times working with other languages. the amount of open source code that’s out there for your specific language seems to have a large effect on copilot’s effectiveness

  • r00ty@kbin.life
    0·
    1 year ago

    Same as every other technological innovation though. Productivity goes up. Revenue goes up. Pay goes… No wait, I must have got something wrong here.

  • b3nsn0w@pricefield.org
    11·
    1 year ago

    me. i slack off 6-7 hours a day and use copilot to do the tasks in the remaining 1-2 hours. (at least i think that’s the ai and not my untreated adhd…)

    in a few years, some genius will do a four day workweek experiment, people like me will forget to only work 4-8 hours instead of 5-10 per week because the amount of tasks is the same, they will conclude that there’s no reduction in productivity, a benefit of four day workweek will work as an incentive instead of a raise to keep people around a bit longer, and it will start becoming a standard. and voila, we got the working hours reduction officially.

    i’ve already heard buzz that negotiating a four-day work week doesn’t tend to involve a 20% salary cut (probably because people are already slacking off a lot). i’ll have to research that more though, because at some point i’d do it even if it did result in a 20% cut, and time is so much more valuable tbh.