4 ms·
I actually had the opposite happen a long, long time ago. Started my new job on salary. Sysadmin on a bunch of remote Unix systems (yes, "Unix"), and systems pr
by mikestew 4y ago
I actually had the opposite happen a long, long time ago. Started my new job on salary. Sysadmin on a bunch of remote Unix systems (yes, "Unix"), and systems programmer as well. As one might expected, it was a demanding job. That's fine, I liked it, and the first month went fine.
Then a new manager gets the idea that we should be hourly. Why? My only reasonable guess is that he had some misguided idea that "salary" was for big-whigs like himself, and "hourly" is for the grunts under him. So now I have to punch a literal clock, like a fast-food worker or summat? Fine by me.
I made fucking bank at that job, as one might imagine. Oh, I worked my ass off, but I got paid for every minute of it (and more, with overtime). What I can't imagine is how much payroll went up, and how he got away with continuing it.
- petsfed 4y agoDid he ever express that he thought it was for big-whigs [sic]? Did he put in long hours alongside you? Is there any possibility that the manager thought "we work these people like dogs, we should treat them better, the least we can do is pay them overtime"?