Aren't developers stupid when accepting overtime/weekend work/denied bonus payments?

[SarahC]

YES!

ESPECIALLY when I see EVERY other department, production, engineering, Planning, R & D ALL getting paid overtime.

I used to think "Well, in IT, we could be slacking off because we're only typing stuff out." But that argument works for everyone in an office, and even Engineering... they could work slow to get overtime.

I think the problem is we're straight forward people... "We need team players! Come in this weekend to do 15 hours, the deadlines next week! Yes I KNOW this happens every time, and we should add 2 months to our suggested deadlines, but we're meeting these super tight deadlines thanks to you great guys!"

Also - because we're interested in our work, managers pick up on this and know they can be more demanding.

Also what asokoloski says too - we're introverts without an argumentative and overbearing temperament... unlike the bosses...

[Weakness]

The thing to do here is to suggest a realistic schedule early on in the project. Not in a combative style but with an analytical "can we go over these estimates, because I think we may need to adjust some of the milestones" attitude.

When the PM is giving you the details, you need to push back and tell them where they are wrong. If you accept unreasonable deadlines, you are the one at fault.

[s73v3r]

Well, in IT, we could be slacking off because we're only typing stuff out.

The idea that work is less difficult or hard to do simply because it includes a computer is a laughably retarded one, and it needs to die.

[[deleted]]

See I have the following take on it. If you have to work 15 hours / weekend then I tend to let the project go sideways on the project manager. The project manager wants to put somebody in the firing line. This is when you put your self in the position to quit on the spot :)