▲ 193 ▼ What’s the craziest or most outrageous (maybe even NSFW) incident that led to someone being fired from your workplace? (lemmy.world) submitted 2 years ago by merari42@lemmy.world to c/asklemmy@lemmy.world 150 comments fedilink hide all child comments
[–] slazer2au@lemmy.world 38 points 2 years ago (1 child) Scream tests are a last resort though. permalink fedilink source parent hideshow 2 child comments replies: [–] intensely_human@lemm.ee 13 points 2 years ago (2 children) Sounds like it was a last resort if he “couldn’t figure out” whose machine it was. permalink fedilink source parent hideshow 4 child comments replies: [–] superkret@feddit.org 12 points 2 years ago (3 children) I don't understand how that is even possible. Are there no logs? No documentation? Does everyone share an admin user with full rights? I mean, there has to be a way to find out who accessed the machine last time. permalink fedilink source parent hideshow 6 child comments replies: [–] ramble81@lemm.ee 21 points 2 years ago* (1 child) You’d be surprised with inheriting tech debt. Quite often there’s no documentation, the last person to log in to the system is an admin that quit 3 years ago, but it doesn’t much matter because that’s only for a direct console login which normal users don’t do when accessing the application. With tribal knowledge gone and no documentation, only when you pull the network for a bit do you discover that there was this one random script running on it that was responsible for loading up all the needed data in the current system, when 9 of the other 10 times those scripts were no longer needed. In a perfect world you’d have documentation, architecture and data flow diagrams for everything, but “ain’t nobody got time for that” and it doesn’t happen. permalink fedilink source parent hideshow 2 child comments replies: [–] superkret@feddit.org 6 points 2 years ago Had that the other way around recently. A docker container failed to come back up after I had updated the host OS. Was about ready to restore the snapshot, when I looked further back in the logs on a hunch. Turns out that container hadn't worked before the update either. The software's developer is long gone, and no one could tell me what it was supposedly doing. permalink fedilink source parent [+] GreenKnight23@lemmy.world 8 points 2 years ago* (last edited 2 years ago) [deleted] permalink fedilink source parent [–] uid0gid0@lemmy.world 2 points 2 years ago You'd be surprised. I had some security devices that I was actively using get shut down simply because some paperwork didn't get filled out properly and the data center team claimed they had no documentation on them. permalink fedilink source parent [–] gravitas_deficiency@sh.itjust.works 1 point 2 years ago I read that as “lazy to the point of unprofessionalism”. I’m super lazy too, but it just means I try to automate the absolute shit out of everything I do to the greatest degree possible. permalink fedilink source parent
[–] intensely_human@lemm.ee 13 points 2 years ago (2 children) Sounds like it was a last resort if he “couldn’t figure out” whose machine it was. permalink fedilink source parent hideshow 4 child comments replies: [–] superkret@feddit.org 12 points 2 years ago (3 children) I don't understand how that is even possible. Are there no logs? No documentation? Does everyone share an admin user with full rights? I mean, there has to be a way to find out who accessed the machine last time. permalink fedilink source parent hideshow 6 child comments replies: [–] ramble81@lemm.ee 21 points 2 years ago* (1 child) You’d be surprised with inheriting tech debt. Quite often there’s no documentation, the last person to log in to the system is an admin that quit 3 years ago, but it doesn’t much matter because that’s only for a direct console login which normal users don’t do when accessing the application. With tribal knowledge gone and no documentation, only when you pull the network for a bit do you discover that there was this one random script running on it that was responsible for loading up all the needed data in the current system, when 9 of the other 10 times those scripts were no longer needed. In a perfect world you’d have documentation, architecture and data flow diagrams for everything, but “ain’t nobody got time for that” and it doesn’t happen. permalink fedilink source parent hideshow 2 child comments replies: [–] superkret@feddit.org 6 points 2 years ago Had that the other way around recently. A docker container failed to come back up after I had updated the host OS. Was about ready to restore the snapshot, when I looked further back in the logs on a hunch. Turns out that container hadn't worked before the update either. The software's developer is long gone, and no one could tell me what it was supposedly doing. permalink fedilink source parent [+] GreenKnight23@lemmy.world 8 points 2 years ago* (last edited 2 years ago) [deleted] permalink fedilink source parent [–] uid0gid0@lemmy.world 2 points 2 years ago You'd be surprised. I had some security devices that I was actively using get shut down simply because some paperwork didn't get filled out properly and the data center team claimed they had no documentation on them. permalink fedilink source parent [–] gravitas_deficiency@sh.itjust.works 1 point 2 years ago I read that as “lazy to the point of unprofessionalism”. I’m super lazy too, but it just means I try to automate the absolute shit out of everything I do to the greatest degree possible. permalink fedilink source parent
[–] superkret@feddit.org 12 points 2 years ago (3 children) I don't understand how that is even possible. Are there no logs? No documentation? Does everyone share an admin user with full rights? I mean, there has to be a way to find out who accessed the machine last time. permalink fedilink source parent hideshow 6 child comments replies: [–] ramble81@lemm.ee 21 points 2 years ago* (1 child) You’d be surprised with inheriting tech debt. Quite often there’s no documentation, the last person to log in to the system is an admin that quit 3 years ago, but it doesn’t much matter because that’s only for a direct console login which normal users don’t do when accessing the application. With tribal knowledge gone and no documentation, only when you pull the network for a bit do you discover that there was this one random script running on it that was responsible for loading up all the needed data in the current system, when 9 of the other 10 times those scripts were no longer needed. In a perfect world you’d have documentation, architecture and data flow diagrams for everything, but “ain’t nobody got time for that” and it doesn’t happen. permalink fedilink source parent hideshow 2 child comments replies: [–] superkret@feddit.org 6 points 2 years ago Had that the other way around recently. A docker container failed to come back up after I had updated the host OS. Was about ready to restore the snapshot, when I looked further back in the logs on a hunch. Turns out that container hadn't worked before the update either. The software's developer is long gone, and no one could tell me what it was supposedly doing. permalink fedilink source parent [+] GreenKnight23@lemmy.world 8 points 2 years ago* (last edited 2 years ago) [deleted] permalink fedilink source parent [–] uid0gid0@lemmy.world 2 points 2 years ago You'd be surprised. I had some security devices that I was actively using get shut down simply because some paperwork didn't get filled out properly and the data center team claimed they had no documentation on them. permalink fedilink source parent
[–] ramble81@lemm.ee 21 points 2 years ago* (1 child) You’d be surprised with inheriting tech debt. Quite often there’s no documentation, the last person to log in to the system is an admin that quit 3 years ago, but it doesn’t much matter because that’s only for a direct console login which normal users don’t do when accessing the application. With tribal knowledge gone and no documentation, only when you pull the network for a bit do you discover that there was this one random script running on it that was responsible for loading up all the needed data in the current system, when 9 of the other 10 times those scripts were no longer needed. In a perfect world you’d have documentation, architecture and data flow diagrams for everything, but “ain’t nobody got time for that” and it doesn’t happen. permalink fedilink source parent hideshow 2 child comments replies: [–] superkret@feddit.org 6 points 2 years ago Had that the other way around recently. A docker container failed to come back up after I had updated the host OS. Was about ready to restore the snapshot, when I looked further back in the logs on a hunch. Turns out that container hadn't worked before the update either. The software's developer is long gone, and no one could tell me what it was supposedly doing. permalink fedilink source parent
[–] superkret@feddit.org 6 points 2 years ago Had that the other way around recently. A docker container failed to come back up after I had updated the host OS. Was about ready to restore the snapshot, when I looked further back in the logs on a hunch. Turns out that container hadn't worked before the update either. The software's developer is long gone, and no one could tell me what it was supposedly doing. permalink fedilink source parent
[+] GreenKnight23@lemmy.world 8 points 2 years ago* (last edited 2 years ago) [deleted] permalink fedilink source parent
[–] uid0gid0@lemmy.world 2 points 2 years ago You'd be surprised. I had some security devices that I was actively using get shut down simply because some paperwork didn't get filled out properly and the data center team claimed they had no documentation on them. permalink fedilink source parent
[–] gravitas_deficiency@sh.itjust.works 1 point 2 years ago I read that as “lazy to the point of unprofessionalism”. I’m super lazy too, but it just means I try to automate the absolute shit out of everything I do to the greatest degree possible. permalink fedilink source parent