Would you people seriously just *stop* doing unpaid work already?!?!
-
I get paid an annual salary. For that salary I have to do a job. The time taken to do that job makes no difference to what I get paid. There is a nominal daily or weekly minimum of hours to be worked, but no maximum.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
I'm in the same boat. However, the OP looks to be under contract and not a salaried employee (maybe I'm wrong), he's getting paid for each hour worked, who cares what the other people are doing?
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment "Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
-
But I do not work on Betelgeuse, only vacation there.
Are you tired of Ursa Minor Beta? :confused:
-
Because overworked employees are not productive. Nor happy. No matter how much they fake it. Productive and happy people think better and produce better code.
Jeremy Falcon
I agree, the OP looks like he's billing for each hour worked, and getting paid for it, unlike the salaried people, they should be griping, not him IMO.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment "Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
-
I'm in the same boat. However, the OP looks to be under contract and not a salaried employee (maybe I'm wrong), he's getting paid for each hour worked, who cares what the other people are doing?
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment "Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
Quite. I read is as he's brilliant, and everyone else is shit, which is why he gets paid the big bucks as a contractor, but because the shit salaried people work longer hours than he is prepared to it makes his sticking rigidly to the clock and going home look bad. He isn't bad, he's good, he's better in fact. It's so unfair. Beats fists on floor, threatens to hold breath until passes out, and so on.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
-
Quite. I read is as he's brilliant, and everyone else is shit, which is why he gets paid the big bucks as a contractor, but because the shit salaried people work longer hours than he is prepared to it makes his sticking rigidly to the clock and going home look bad. He isn't bad, he's good, he's better in fact. It's so unfair. Beats fists on floor, threatens to hold breath until passes out, and so on.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
meeee-kin-owww! Put your claws back before you rip your handbag! :laugh:
-
Quite. I read is as he's brilliant, and everyone else is shit, which is why he gets paid the big bucks as a contractor, but because the shit salaried people work longer hours than he is prepared to it makes his sticking rigidly to the clock and going home look bad. He isn't bad, he's good, he's better in fact. It's so unfair. Beats fists on floor, threatens to hold breath until passes out, and so on.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
You can't worry about what you have no control over.
chriselst wrote:
threatens to hold breath until passes out
Oh goody! :)
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment "Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
-
No.Unbillable.Work! If the customer isn't paying for it, the customer doesn't get it. Call me crazy, but I bill for every single hour I work...like I am supposed to. It infuriates me when I get into a project with salaried employees that commit "heroic effort" to making their screw ups not look like screw ups and make my 40-45 hour a week billable commitment look diminished. I had a guy tell me first thing when we got in that he was working until 2:00 this morning completing something because the customer ballooned our scope but held firm to the original deadline. What does project management tell said customer when he did this? "Ok." The real problem is that giving project management what they want just reinforces to them that it is ok to start death marches; your reward for completing one is that you get to start your next. I get paid or you do not get work done. No. Unbillable. Work. STOP IT!!!!
"I need build Skynet. Plz send code"
:doh:
if(this.signature != "") { MessageBox.Show("This is my signature: " + Environment.NewLine + signature); } else { MessageBox.Show("404-Signature not found"); }
-
No.Unbillable.Work! If the customer isn't paying for it, the customer doesn't get it. Call me crazy, but I bill for every single hour I work...like I am supposed to. It infuriates me when I get into a project with salaried employees that commit "heroic effort" to making their screw ups not look like screw ups and make my 40-45 hour a week billable commitment look diminished. I had a guy tell me first thing when we got in that he was working until 2:00 this morning completing something because the customer ballooned our scope but held firm to the original deadline. What does project management tell said customer when he did this? "Ok." The real problem is that giving project management what they want just reinforces to them that it is ok to start death marches; your reward for completing one is that you get to start your next. I get paid or you do not get work done. No. Unbillable. Work. STOP IT!!!!
"I need build Skynet. Plz send code"
-
Because overworked employees are not productive. Nor happy. No matter how much they fake it. Productive and happy people think better and produce better code.
Jeremy Falcon
-
Because overworked employees are not productive. Nor happy. No matter how much they fake it. Productive and happy people think better and produce better code.
Jeremy Falcon
But salaried employees get bonuses, contract ones don't. The perceived effort/input/success of an individual employee can reward with significantly higher bonus than one who does the bare minimum. Contractors then moan that they don't get a bonus, well of course not, you are paid for what you do - your terms! ;P
Dave Find Me On:Web|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProject
-
This girl I used to work with was complaining once about all the extra time we were putting in to get a job out the door...she said, 'All this extra time we're putting in reduces my hourly pay to "do you want fries with that?"' ...made me laugh...
-
Very true but then they're going to be replaced by vending machines and robots...McDonalds will become a cafeteria. More programming work for us... 'Woops, sorry!...the code threw an unhandled exception and injected special sauce into the cherry pie!' :)
-
No.Unbillable.Work! If the customer isn't paying for it, the customer doesn't get it. Call me crazy, but I bill for every single hour I work...like I am supposed to. It infuriates me when I get into a project with salaried employees that commit "heroic effort" to making their screw ups not look like screw ups and make my 40-45 hour a week billable commitment look diminished. I had a guy tell me first thing when we got in that he was working until 2:00 this morning completing something because the customer ballooned our scope but held firm to the original deadline. What does project management tell said customer when he did this? "Ok." The real problem is that giving project management what they want just reinforces to them that it is ok to start death marches; your reward for completing one is that you get to start your next. I get paid or you do not get work done. No. Unbillable. Work. STOP IT!!!!
"I need build Skynet. Plz send code"
I agree, but the bigger issue is that working "unbilled" hours will often adversely affect estimates for future projects. The project manager must know the actual time spent for the current project. Remember that "extra" hours spent on the current project are probably due to a bad estimate based upon what was understood from the previous project. While no estimate will ever be accurate, at least start with good data.
-
Very true but then they're going to be replaced by vending machines and robots...McDonalds will become a cafeteria. More programming work for us... 'Woops, sorry!...the code threw an unhandled exception and injected special sauce into the cherry pie!' :)
-
Because overworked employees are not productive. Nor happy. No matter how much they fake it. Productive and happy people think better and produce better code.
Jeremy Falcon
I'd have to agree. It really surprised me: I had always been in an environment where you ate at your desk, worked long hours, some weekends - mostly unpaid, but for the occasional "thank you" - then I started a new job with a different company and on the first day I was told (with some impatience) that they were waiting to lock up the building at 17:02. On the second day, one of the order processing ladies "had a quiet word" and told me to stop working my lunch hour. They suspected that if I didn't they would have to start... :laugh: So I found myself working 09:00 to 17:00 (13:00 on Fridays) even after I was given the key to the building with a full hour off for lunch. And b*gg*r me! I was getting more done... :omg: I think it has two effects: you focus better while you are working, and the breaks let you relax and become more creative at the same time. So much so that I don't work a full hour any more: I take regular breaks and do something different - come here for example - and it works. Counter-intuitive, I know.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
Very true but then they're going to be replaced by vending machines and robots...McDonalds will become a cafeteria. More programming work for us... 'Woops, sorry!...the code threw an unhandled exception and injected special sauce into the cherry pie!' :)
-
chriselst wrote:
but no maximum.
Yes there is, 24 hours in one day. ;P
-
No.Unbillable.Work! If the customer isn't paying for it, the customer doesn't get it. Call me crazy, but I bill for every single hour I work...like I am supposed to. It infuriates me when I get into a project with salaried employees that commit "heroic effort" to making their screw ups not look like screw ups and make my 40-45 hour a week billable commitment look diminished. I had a guy tell me first thing when we got in that he was working until 2:00 this morning completing something because the customer ballooned our scope but held firm to the original deadline. What does project management tell said customer when he did this? "Ok." The real problem is that giving project management what they want just reinforces to them that it is ok to start death marches; your reward for completing one is that you get to start your next. I get paid or you do not get work done. No. Unbillable. Work. STOP IT!!!!
"I need build Skynet. Plz send code"
-
But salaried employees get bonuses, contract ones don't. The perceived effort/input/success of an individual employee can reward with significantly higher bonus than one who does the bare minimum. Contractors then moan that they don't get a bonus, well of course not, you are paid for what you do - your terms! ;P
Dave Find Me On:Web|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProject
I'm not dissing the salary concept, I'm simply stating that anyone that's overworked cannot be happy. Money is not worth trading your entire life for.
Jeremy Falcon
-
I'd have to agree. It really surprised me: I had always been in an environment where you ate at your desk, worked long hours, some weekends - mostly unpaid, but for the occasional "thank you" - then I started a new job with a different company and on the first day I was told (with some impatience) that they were waiting to lock up the building at 17:02. On the second day, one of the order processing ladies "had a quiet word" and told me to stop working my lunch hour. They suspected that if I didn't they would have to start... :laugh: So I found myself working 09:00 to 17:00 (13:00 on Fridays) even after I was given the key to the building with a full hour off for lunch. And b*gg*r me! I was getting more done... :omg: I think it has two effects: you focus better while you are working, and the breaks let you relax and become more creative at the same time. So much so that I don't work a full hour any more: I take regular breaks and do something different - come here for example - and it works. Counter-intuitive, I know.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
OriginalGriff wrote:
Counter-intuitive, I know.
It's true though. The brain is a muscle. And like any other muscle, it can be overworked and destroyed. We need to give our "thinking" brains some to rest and recoup to always be on our A game. The folks that rot in front of their computer and drug themselves up on coffee tend to act more like zombies than anything else. You just can't beat rest to keep the brain sharp.
Jeremy Falcon
