2 ms·
Interesting that you knew and didn't call them out. I've often felt that some folks at my workplace has suspicions but didn't call me out on it since I got my w
by froaway4job 5y ago
Interesting that you knew and didn't call them out. I've often felt that some folks at my workplace has suspicions but didn't call me out on it since I got my work done. Workplace dynamics are strange.
I'm fully ok with being let go first if there is a "revolution". I've never been let go or fired before, but I'm not willing to go the extra mile for the "opportunity" to not be let go if the company has issues.
- codingdave 5y agoTo be fair, on some of my teams I would have called them out. That particular team was at a large company, for a sysadmin team whose job was to keep one of our enterprise platforms up and running. The dude kept it up and running. I truly didn't care how much time it took him, and there wasn't much intellectual property concern from his role. In a startup, small company, or a role more critical to the strategy and core business, or a role with a less defined scope, I would not have let it slide. To me, it is all about what the expected business relationship is. If I hire someone to do a specific scope and they get it done, that is one thing. If I hire them to a more generalized role whose job is to put a full-time effort into making the business succeed in whatever way they can, then I do expect full-time effort put into that job, and I expect them to look for more ways to help if there is spare time.