4 ms·
If he was a company providing a service this wouldn't even be a subject for discussion. It would be a non-issue. Also he's been pretty much instructed by the co
by simonh 9y ago
If he was a company providing a service this wouldn't even be a subject for discussion. It would be a non-issue. Also he's been pretty much instructed by the company not to rock the boat. It seems pretty clear they really don't care as long as the work gets done.
I've known plenty of sysadmins that have significantly automated most of their work and mainly just monitor and maintain, good for them. Nobody ever criticised them for this, in fact it's good practice. Finally he's not really being paid for hours worked. If it took him every hour of that time the first few months,but then he got better at it and later it took 30 hours instead of 40 nobody would care. In fact I'm sure the company fully expects something like that to happen, again they just don't care.
He should stop introducing errors though.
- mst 9y ago> He should stop introducing errors though. Then the QA team would stop paying attention and if he ever introduced a bug it would be much much worse. Seems to me that in this case it serves a "test your backups" function.
- jenkstom 9y agoLike his own personal chaos monkey.
- mst 9y agoThat's a better metaphor than my backup one was. Thank you!
- inetknght 9y agoThat's probably the best argument against everyone else saying that it's fraud.
- mmcnl 9y agoThis might be true, but it is not the best solution. Seperation of duties should be in place here.
- hjksddhfa 9y agoThis. As sysadmin, 90% of my job is automated. I am available 24/7 if anything goes wrong. But then OTH, I can run errands, watch movies, play video games at work. This is true for almost every sysadmin I know. My bosses know this, they don't care as long as I am available when needed. Also they prefer that we as sysadmins don't advertise our free time to the rest of company.