How many hours per week do you work?
-
One thing that is a big deal is whether your job is one of productivity or one of availability. If your job is engineering or decision making making you a productivity worker, then going to 20-30 hours a week is found to be ideal for getting the best work out of you.
If, on the other hand, you are an availability worker like a system admin, helpdesk tech or similar then cutting hours reduces your value to the company by making you less available.
So it really depends. When I was at CitiGroup they offset this by having me be always on call as a system admin but only in the office for 20 hours a week. There are ways to make availability workers valuable without making them "work" too much, but you have to be more creative than just reducing hours.
-
@scottalanmiller said:
One thing that is a big deal is whether your job is one of productivity or one of availability. If your job is engineering or decision making making you a productivity worker, then going to 20-30 hours a week is found to be ideal for getting the best work out of you.
If, on the other hand, you are an availability worker like a system admin, helpdesk tech or similar then cutting hours reduces your value to the company by making you less available.
So it really depends. When I was at CitiGroup they offset this by having me be always on call as a system admin but only in the office for 20 hours a week. There are ways to make availability workers valuable without making them "work" too much, but you have to be more creative than just reducing hours.
How do I get this????!! I am in the office 40-50 hours and then on-call for the other 150 or so hours
-
@donaldlandru said:
How do I get this????!! I am in the office 40-50 hours and then on-call for the other 150 or so hours
Um... work for a more enlightened company that takes its IT more seriously?
-
I generally put in 40-45 billable hours a week. Billable hours = hours I get paid for.
I also put in 5-10 hours of time doing things to improve my skills for various pieces of our business. This is not paid for directly.
-
40, I work 40 hours and then have a hard cut off. I came from a company that used to push me 45-55 every week to get their money's worth. I am much happier overall now than I was before, and makes me more likely to pick up skills at home and learn again vs coming home drained and wanting to unplug from all tech.
-
@s.hackleman This is where I am at too. I was the on call guy... and boy did I get the calls... My new employer is great and being just one of the minions low on the totem pole, I don't have to worry about too much like that.
-
I used to bust my butt and do tons of OT - when I stopped and everything kept working....
37.5h/wk, occasionally an extra hour here or there, but it's rare.
-
4 10's, and then I have my own business so I work in the evening until about 9-10 and then usually doing stuff for that on Friday as well.
Plus, I feel like a moron reading stuff on here so I'm always trying to learn things.
-
@johnhooks Try, not! Do, or do not. There is no try! (sorry... I couldn't resist)... But seriously, I learn more by doing, so when somebody says hey I want to do $project -- If I have the resources in my system at home to set it up myself, then I do so.
-
@dafyre said:
@johnhooks Try, not! Do, or do not. There is no try! (sorry... I couldn't resist)... But seriously, I learn more by doing, so when somebody says hey I want to do $project -- If I have the resources in my system at home to set it up myself, then I do so.
Lol, I'm the same way. I have a hard time learning if I don't do it myself. Watching other people do it helps (much better than reading) but doing it is always the best for me. I just never feel like I'm not behind on stuff (if that makes sense).
I wish I was paid based on the number of VMs I've created and destroyed in doing projects.
-
If you ever feel like you are caught up... then you should worry, lol.
