And I thought that petty rulebreaking was a corrosive force, something that would snowball into bigger problems down the road. As a man of honour I would work precisely my contracted hours, never a minute less, I would consider it shameful if someone so much as stole a pen from the office. The rest of the team is heading to the pub at 4pm after a lengthy day of planning meetings? Sorry guys, I don't finish until 5:30pm.
Later in my career I chilled out a lot, and learned that the actual rules are often different (and a lot more nuanced) than the written rules. And that if you've worked with a guy for a decade you can, in fact, hold the door open for him and the sky won't fall down.
This basically sums up my "cover story" nicely so I didn't have to admit to myself that it was more about scoring points for my own position.
Dressing up vanity as integrity is a dangerous thing.
I’m curious, did these ideas come from your upbringing?
The comment already established the senior sysadmin is generally a valuable person who does a lot to flourish the company. Going out of the way to be a encumbrance towards someone who is verifiably doing their job anyways, means you're actively creating a people problem. I;d rather people learn the correct, bigger lesson here.
The opposite lesson is also useful: sometimes you can turn people problems into tech problems, and that's how you can 'solve' them.
Slightly hypothetical scenario: assume your team keeps all the source code on a shared drive. You are supposed to coordinate with your coworkers before touching any code. Sometimes that goes wrong, and looks like a people problem.
If you introduce eg git and automated-tests-before-merging, you can turn that into a technical problem.
My thesis is that organisations (and people in those organisations) can only solve so many people problems. If you lighten the load by automating some of the problems into tech problems, you have more levity on the remaining people problems.
(This happy state of affairs isn't always possible. And sometimes it can backfire.)
So it is a philosophical question of why the restrictions were in place in this scenario. If it was “employee productivity”, then sure, who cares. If it was an IRS computer with thousands of people’s tax returns on disk and access to millions more, then reporting was the right move.
I can imagine trusting someone to set up (and even enforce) eg an alcohol policy, but still be prone to alcohol abuse themselves.
Weak wills are a thing. Or people thinking they are smarter than the protocols that apply to the masses.
I don't think the senior sysadmin was paid to hide browsing from the oversight?
In this case, I think vasco's take is correct: the sysadmin was indeed trustworthy enough to exercise this discretion in response to overzealous employee productivity rules without at all undermining his primary responsibilities.
The proxy was definitely in a place to essentially trivialize it's impact. I'm pretty sure thats why it was placed where it was, as opposed to make it harder to find. If that was the chief concern, disabling logging would have obviously been the first thing to happen.
edit: to be clear, it wasn't the admin downloading the content.
If your values are to report someone to win brownie points with your boss, it’s probably time to revisit them.
Another great guide is asking yourself what you’re trying to accomplish.
There would be times when going against your employer by blowing the whistle or covering up is the more moral thing to do.
Deciding where that line is not simple and there is no guide.