Comment on Amazon boss tells staff AI means their jobs are at risk in coming years

Cocodapuf@lemmy.world ⁨4⁩ ⁨weeks⁩ ago

• qyron@sopuli.xyz ⁨3⁩ ⁨weeks⁩ ago

  Stupid question but what is stopping the software engineers to poison the well?

  Insert malicious code, self destructing functions, have entire batches of code lost or corrupted, hardware damaged, etc?

  source

  • Regrettable_incident@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    From what I hear, people try stuff like this all the time, stuff like putting a bit of code on your employer’s system that’ll erase important files if you get shit canned and no longer appear on the payroll. It’s why a lot of companies no longer give notice when ppl are fired, just have security walk them out. And unfortunately this stuff is often traceable, which means they’re risking quite serious prosecution.

    I don’t like much of what I see, I think it’s becoming clear that some new tech is going to have wide ranging and harmful effects. I’m not sure that doing luddite stuff will help but I can understand why people would think that way.

    source

    • qyron@sopuli.xyz ⁨3⁩ ⁨weeks⁩ ago

      We could just regulate tech companies and outright ban some practices but since we apparently don’t have time for rational solutions…

      Well thought out sabotage can be written off to causality or involuntary human error.

      Not giving notice of lay off is an abusive work practice and only shows how far we’ve allowed work conditions to degrade.

      And that practice itself can be highly dangerous, if we consider a person can be midway into a complex task that can turn extremely difficult to follow by another: waste of time, resources, energy and money.

      source
  • baatliwala@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    A company with fuck off amount of legal power?

    source

    • qyron@sopuli.xyz ⁨3⁩ ⁨weeks⁩ ago

      Small acts of sabotage are easy to write off to causality, if well planned.

      source
  • pinball_wizard@lemmy.zip ⁨3⁩ ⁨weeks⁩ ago

    Stupid question but what is stopping the software engineers to poison the well?

    Great question. I agree with other responses - it happens, and there’s motive to hush it up, so we tend not to hear about it.

    It’s also just really hard to tell the difference after the fact between “Dave sabotaged us” and “no one knows how to do what Dave did”.

    But I’ll add - there’s currently little need motive sabotage AI implementations. Current generation AI is largely unable to deliver on what is promised, in a business sense. It does cool but useless things, like quickly generating low maturity code, and writing a summary any seven year old could have wtitten.

    Current generation AI adds very little business value, while creating substantial risks. Nevermind that no one knows how Dave worked, now no one knows how our AI works, and it’s so eager to please everyone that it lies at critical moments.

    Companies playing around with current generation AI to boost next quarter’s stocks will hit plenty of “find out” soon enough, with nothing beyond the natural consequences of ignoring their own engineers advice.

    All that to say - if we see what looks like sabotage, it may well just be the natural consequences of stupidity.

    source
  • Cocodapuf@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    Well it’s hard to do without leaving a very clear trail. I assume most engineers want to keep their job and their income.

    But programmers tend to use some form of a “versioning” system like git. This will record everyone’s changes to the codebase, when a change was made, what was changed, who changed it. And it allows you to go back and revert changes if something important broke. Very convenient for programmers, less convenient for sabotage.

    source
  • LastYearsIrritant@sopuli.xyz ⁨3⁩ ⁨weeks⁩ ago

    bleepingcomputer.com/…/developer-guilty-of-using-…

    10 years in jail is what’s stopping them.

    It’s REALLY hard to create a dead man’s switch that works, but also leaves no trace. Even if you delete the script after it executes, there’s probably backups or logs that show what happened.

    source