3 ms·
My gut says, for this sort of thing: why delete it? Let them have it, there’s no upside to deleting it. Who cares, right? But hypothetically, it probably has n
by bee_rider 3y ago
My gut says, for this sort of thing: why delete it? Let them have it, there’s no upside to deleting it. Who cares, right?
But hypothetically, it probably has no license or anything like that. Not even the “no promises of merchantability” stuff you sometimes see. Hypothetically could there be a risk to the coder? If my buggy “forklift stacking high” software says “stack that stuff up to the roof,” and gets hurt listening to it, am I on the hook? (In that case of course he never should have let anybody use it in the first place, but leaving the job provides a moment of reflection).
Realistically it doesn’t seem like the sort of thing anybody would pursue. But it is interesting to wonder about…
- travisgriggs 3y agoI think there is an upside. Or at least a perceived upside. The employee may feel like they went above and beyond what was expected and wanted to be recognized for that. This may be the only way they get recognized. I’m not condoning this. And I think the long term costs/price outweigh the gain of affirmation/recognition they may want. But I do believe there is an emotional calculus that goes into this.
- exodust 3y agoGood point, but realistically if harm is caused due to unsafe warehouse stacking, there is a human employee behind that error. The exception might be automated stacking software, which would need to be licensed and done properly. So it's more likely the software in this case was an office admin data entry solution. When they fail, people say "oh crap" and call IT who may or may not fix it!