• doleo@lemmy.one
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 day ago

    even if that eventually costs me a job I mean it’s kind of a ‘damned both ways’ situation, here. Right? Lose your job if you refuse to use it, lose your job if you end up training it how to do your job.

    • zbyte64@awful.systems
      link
      fedilink
      English
      arrow-up
      10
      ·
      edit-2
      1 day ago

      That’s just it though, it’s not going to replace you at doing your job. It is going to replace you by doing a worse job.

    • Architeuthis@awful.systems
      cake
      link
      fedilink
      English
      arrow-up
      7
      ·
      1 day ago

      A programmer automating his job is kind of his job, though. That’s not so much the problem as the complete enshittification of software engineering that the culture surrounding these dubiously efficient and super sketchy tools seems to herald.

      On the more practical side, enterprise subscriptions to the slop machines do come with assurances that your company’s IP (meaning code and whatever else that’s accessible from your IDE that your copilot instance can and will ingest) and your prompts won’t be used for training.

      Hilariously, github copilot now has an option to prevent it from being too obvious about stealing other people’s code, called duplication detection filter:

      If you choose to block suggestions matching public code, GitHub Copilot checks code suggestions with their surrounding code of about 150 characters against public code on GitHub. If there is a match, or a near match, the suggestion is not shown to you.