56
Best way to sabotage AI at work? (hexbear.net)
submitted 5 months ago by to c/askchapo@hexbear.net
23 comments fedilink hide all child comments
 

At work we will soon be getting access to agentic AI that parses through our gigantic code base and burns through money for very simple requests.

What would be the best way to maliciously comply with the management's decision for AI usage to be an everyday thing you are expected to do without getting found out?

My idea is spamming the living shit out of the most expensive models for pointless tasks and then insisting that the result is wrong, and work in the meantime. Nobody can complain if my work is still good, but they will notice that the AI budget is not worth it and stop the hype train.

you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 5 months ago*

Maybe create a module in your repos that are never called by the actual working code, that the AI gives it's contributions to. It compiles, but never does anything.

This will unfortunately increase the attack surface of your compiled binaries.

  • permalink
  • fedilink
  • source
  • parent