Slashdot Log In
12/7 and Overtime on a Salary?
Posted by
Cliff
on Sun Jun 15, 2003 04:39 PM
from the when-management-isn't-on-your-side dept.
from the when-management-isn't-on-your-side dept.
over-timeout! asks: A company I work for (in the U.S.A.) had submitted a statement of work to a client, who waited for a month before signing the work order. The work order explicitly stated a timeline which would start from the time the order is signed. However, the client is insisting on the project being completed by a fixed date, as discussed with our company's management, instead of the deadline that starts from the signing of the work order. Although our company representatives tried to push back on the date, the client refused. Because the client is among our company's biggest customers, our company's management caved in and agreed to their deadlines. Management has told us meeting deadlines means that for the next month to six weeks all of the developers involved will have to work 12 hours a day, 7 days a week. The contractors involved are going to get compensated by being paid by the hour. But us salaried employees are going to get nothing in return for trading in what's left of our life so someone else in the company above us can make money. Obviously this isn't fair, but what are the alternatives in this down economy, where jobs are hard to find?" A related articles on this subject discusses suing for overtime, and California residents should find this companion article pertinent, as well. What can you do when management agrees to a timeline and a workload that may make your job, as a programmer, difficult-to-impossible?
This discussion has been archived.
No new comments can be posted.
12/7 and Overtime on a Salary?
|
Log In/Create an Account
| Top
| 932 comments
(Spill at 50!) | Index Only
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
They pretend to pay us... (Score:5, Funny)
Re:They pretend to pay us... (Score:4, Insightful)
(http://www.google.co...nI=I'm+Feeling+Lucky | Last Journal: Sunday September 12 2004, @09:05AM)
:p
Re:They pretend to pay us... (Score:5, Informative)
(http://www.footballpredictions.net/)
To elaborate, in the EU you cannot be forced to work more than 48 hours per week. You may volunteer to work more than 48 hours, but your employer cannot insist that you do and may not punish you for refusing to.
There was a minor fuss when this EU regulation was incorporated into UK law, but it seems to have had no negative effect and provides protection for workers.
Re:They pretend to pay us... (Score:5, Insightful)
(http://www3.telus.net/alexander_russell/)
I NEVER work for free, and neither should you.
PS - I must admit that while working as a contractor I have worked huge amounts of overtime - but I was getting paid for it.
Re:They pretend to pay us... (Score:5, Insightful)
(http://slashdot.org/)
Re:They pretend to pay us... (Score:5, Funny)
(http://google.com/)
Don't worry, the E.U. is outsourcing its I.T. jobs to India and the Ukraine, too. Although, I suppose that "unemployment" is approximately the same as "long, poorly paid vacation."
Re:They pretend to pay us... (Score:5, Funny)
I know, my point-of-view is a little bit too much over at the other edge, but I just can't imagine getting into a state where my employer says "you have to work the rest of your life for me and sell your soul for the company" -- and all *I* do as a reaction is Asking Slashdot "what should I do"?
What he should do? Kick the man's ass, of course! I've heard of "slave to the minimum wage", but this beats everything!
Re:They pretend to pay us... (Score:5, Funny)
This is where it pays to be religious. (Score:5, Insightful)
(Last Journal: Thursday September 13, @12:15PM)
That is well within the demands of our religion. Get laid off? Ask why, in writing. If they say "could not work to meet the demands of our contract", that is enough to haul them into court: religious discrimination, and sue for company ownership.
No kidding, that 1-day-off is God's minimum-benefits plan. It is also extremely important for a different reason: people who don't get 1 day off tend to start making very bad decisions. Ask my brother, who was working 7 days per week on his grad program. He got an ion trap working that had never worked before, then got data; it was given to a previous student for her PhD. He accepted it, and went to get more data... but long story short, destroyed the million dollar superconduncting magnet through a series of plausible, but erroneous mistakes.
His grad professor approved every one of the decisions, but was not overseeing the work, since he too was making bad decisions...
I really think 1 day off a week is quite important, and the 3 major religions of Jewish origin provide a good means for that 1 day a week.
But if you aren't religious, that's okay. Go ahead and put bugs in the customer's code [you can't help it... it'll happen.]
Or go back and argue this one out with your management, saying "this isn't acceptable -- you need to hire more workers or the work isn't going to get done right, and you need to charge the customer the extra."
Re:They pretend to pay us... (Score:5, Interesting)
Reminds me of a story on TV in the UK a week ago (BBC2, Correspondant, Sunday night, all about the eurozone but no link unfortuately).
A German manufacturing company manager was being interviewed. He said a project was due on Monday but Friday night was not finished... so the workers decided to come in on Saturday to finish it. The manager did not know the workers were coming in. The project went out on Monday. Some months later the employer was called to court - someone had mentioned this to the authorities, and although they were working voluntarily he was ordered to change locks at the factory and hold all keys himself only, and if a worker did voluntary overtime he should fire them!!!!
Wow! That is a nanny state wrapping you in cotton woll and duct tape until you asphixiate.
Re:They pretend to pay us... (Score:5, Insightful)
I make it a point to always leave at 5PM when I can. If there's some emergency or important project that requires me to stay late, I do so, but I make up for it by leaving early at some point in the future.
I suppose this is an advantage of working for the state (state university), but you have to remember that if you let work control you, you can never be truly happy (unless you're a workaholic but that's something else)
Work 9-5. If your employer abuses you, put up with it until you can find another job, then leave. There's no reason to put yourself through hell.
Re:They pretend to pay us... (Score:5, Interesting)
When stuff needs to get done ASAP, I stay until 9 p.m or 10 p.m. I even come in on the weekend. This is OK with me because if I don't the company won't make money or get the next contract and I will probobably end up unemplyed.
Plus, I like the company I work for. People are great and we are a real team. It is not like everyone is slacking off and I have to work lots of hours. Oh and our management also work lots of hours. They are always last to leave. These guys even stay until 9 p.m. on Friday nights.
Re:They pretend to pay us... (Score:5, Insightful)
(http://diaspora.gen.nz/~rodgerd/)
Re:They pretend to pay us... (Score:5, Insightful)
(Last Journal: Wednesday May 09 2007, @08:30AM)
I have every right to say, "it's 5:00PM. I'm going home now". And I do. Every day. At least I work for a sane and humane employer. Granted I don't make a six figue salary and would be considered "poor" by most of the Slashdot neocons. But having more time outside of work then at work is worth more to me than six figures, an SUV and a cluster home.
Europe has the right idea. If we all worked less, we'd get more done with a higher level of quality. And maybe not everyone would be as uptight.
Re:Then I DO get paid for overtime (Score:5, Insightful)
(http://wolfrdr.tripod.com/linuxtips.html | Last Journal: Tuesday November 27, @11:07PM)
--A balnace *has* to be struck between work and personal life. I don't care if you're a single bachelor even - if you devote your entire life to work, you rob yourself. Your employer does NOT CARE about you. Stand up for your personal time, and don't agree to be a slave.
Re:They pretend to pay us... (Score:5, Funny)
Jobs are hard to find, but... (Score:5, Interesting)
Re:Jobs are hard to find, but... (Score:5, Interesting)
(http://www.eecg.toronto.edu/~livio/)
wrongful dismissal (Score:4, Insightful)
Re:wrongful dismissal (Score:5, Informative)
(http://www.ucblockhead.org/journal/ | Last Journal: Thursday November 14 2002, @03:24PM)
IANAL. However, I just spent two weeks in a jury [ucblockhead.org] on a "wrongful termination" case.
In the US, there are only three reasons you can sue for this. 1) The company promised via explicit or implied contract that they wouldn't. (Exceedingly unlikely.) 2) You complained about safety and they fired you in retaliation. 3) They fired you for your race, age or gender.
Since most companies employee people "at-will", they can essentially fire you for any damn reason they want, as long as you aren't a whistle-blower and as long as their reasons aren't discriminatory in specific ways.
Re:Jobs are hard to find, but... (Score:4, Informative)
(Last Journal: Saturday June 04 2005, @11:50AM)
It may not work, but has a hell of a better chance than "let's all band together".
Re:Jobs are hard to find, but... (Score:5, Informative)
(http://www.phoenyx.net/ | Last Journal: Sunday December 26 2004, @11:50PM)
I *did* mention the Title VII exemptions, which would cover the first two examples.
But yes, as I understand it it's legal to fire someone because you decide they're ugly and stupid, as long as you're doing it on an individual basis and not making a pattern of deciding that sort of thing about members of a protected class (Title VII again). They might have grounds for slander charges, or even assault if you phrase it wrong, but that's a side issue.
I'm not a lawyer, but I had grounds to consult one. Two, actually. The first lawyer I spoke to was one I knew of who normally handled the corporation's side of the case, and who I trusted to refer me to someone who wasn't an ambulance-chaser to handle an employee's side of the case. He flipped through the employee's handbook, which the company owner had written without benefit of counsel. There's nothing quite as interesting as having a lawyer shaking his head and muttering "Oh, shit. Oh, *shit*." very quietly under his breath. I'm not sure he was aware he was doing it.
At any rate, one thing that stuck with me was when he pointed out that the company owner stated that part of the company mission statement was "to treat employees fairly." He said he'd never advise a company to put that in... because Kansas law does not require a company to treat its employees fairly. It merely requires a company to treat its employees in accordance with the law.
All that said, I do suspect there's Wage & Hour restrictions on extreme hours, but sararimen get much less protection than the hourly guys, so I dunno. Never have had to find out, fortunately.
Re:Jobs are hard to find, but... (Score:5, Insightful)
That depends on your point of view. From another point of view, it's probably incompetent management trying to take advantage.
It doesn't matter that it's "only" 4-6 weeks. The employees will be straining to get through half that at 12/7 before they start doing more harm than good. If it's "only" a one-off and really necessary for the company, then management should have approached the employees and discussed the possibility with them before accepting the project and telling them what they "have to do".
This sounds like a simple failure of good management. The managers exist only to balance requirements with resources. If this project requires excessive work on the part of the staff, then management should have assigned more resources, or not taken on the project. They have no-one to blame but themselves if they treat salaried staff in a less favourable way than contractors, and those staff then feel aggrieved.
I agree with the other posters that you should look at the company and the nature of management overall before deciding how to act in a situation like this. But look with a very sceptical eye. Loyalty to a good employer is fair enough, but I've seen way too many people stick it out way too long because they assumed that "things will get better" or "the economy is just down", while others around them in a similar position were getting much better deals by actually going out and shopping around.
Re:Jobs are hard to find, but... (Score:5, Insightful)
They should decide whether or not it is viable to complete the project to the client's specifications with the resources available. ("Viable" needn't mean "profitable"; they could decide to run the project at an acceptable loss in order to keep the client sweet.)
If the project is viable, they should assign sufficient resources and have the project done. If the project is not viable, they should explain this politely to the client, and decline the business.
No smart client is going to withhold future business because you declined an infeasible project. If they do, you have failed to manage your clients' expectations effectively, which is another common but avoidable failure of management. And besides, you are in business to make a profit, not to keep happy potential clients who do not make you a profit.
Sure, and the employees have every right to say no if unreasonable demands are made of them, particularly in the sort of unpleasant way that this seems to be done (telling not asking, no up-front offers of compensation, treat staff differently to contractors, etc).
I'd work out what resources would be needed. If necessary, this could include asking whether people would be prepared to do more than their usual amount of work to increase that, given mutually acceptable compensation. Then I'd work out if the project was viable. If it was, I'd take it. If not, I wouldn't.
This is not a new problem, nor even an uncommon one. Yet companies with bad management seem to run into it all the time, while companies with good management strangely seem to avoid it, even when working in a similar industry and with similar or identical clients. Go figure.
Four letters (Score:5, Interesting)
If you cave on this, they might throw you a bone (they might give you a 3 day weekend or two). If you're succesful and you deliver a good product, your management won't have to think twice about doing this to you again. The fact that your management isn't willing to throw a carrot out there up front tells me they aren't going to make competent decisions in the future.
I know its hard to quit when you have mouths to feed, etc., but if quitting is not an option, you're really at their mercy.
Five letters (Score:5, Funny)
Four more letters (Score:5, Insightful)
It's easy to say "oh, well just quit, then" when they situation is purely hypothetical to you. Unfortunately, not many of us are in a position where we can just tell our boss to get fucked, as much as we'd like to.
In the last year my department has been whittled down from eight employees to me and another guy. It sucks ass, but I've got to pay the bills.
Re:Four letters (Score:5, Insightful)
"hard to quit when you have mouths to feed, etc."? It's downright irresponsible in this economy. I'm all for the entrepreneurial spirit and I am certainly for the rights of the worker but to quit an IT job right now...without another job already lined up...is likely to spell 6+ months on unemployment and a lower paying job at the end.
I realize you are not saying the parent poster should quit but it just strikes me as funny that so many posters to slashdot yell "Quit!" as if jobs are growing on a 1990's-esque tree somewhere.
I think the better approach is to first ask yourself whether or not the employer has a history of doing this kind of thing. Do they treat you well when times are good and call on you to step up when times are bad?
Case in point: I recently led a small team developing a web application. The completion date was set by the customer even before we were able to analyze the requirements and once I had a chance to look at the requirements I told my managers that it would be really difficult to meet the date without working alot of overtime for an extended period of time. Management replied that their hands were tied (they were) and that we had to hit the mark i.e. I walked in this geek's shoes.
I had no choice. I wasn't going to walk out of my job on the off-chance that I might find another job. I'm salaried. I knew I was getting screwed, etc.
What happened: every step of the way, my management team was there fighting to get the schedule extended, attempting to reduce the requirements, etc. In the end, the schedule was extended by about a month and a half and a particularly troublesome requirement was dropped. Now that the job is done things have slackened off some, my team is looked upon favorably, nobody gives us hassles if we are not busy 100% of the time or come in under 40 hours for the week because they know that when push comes to shove we will get the job done and leave the attitudes, etc. for the project's post-mortem review.
So...if you are employed, like your job overall and management generally treats you well overall, etc. you might want to consider just biting the bullet for a the time it takes and go from there. The pendulum has swung from one extreme (the employee's market of the 1990's) to the other (employer's market of today) but it will eventually swing back towards center and, when it does, management will have, as Ricky Ricardo would say, "some 'splainin' to do". The fact that you stuck it out when times were hard can be leveraged into either a fat raise, new position or another job at a company that appreciates you more.
Re:Four letters (Score:5, Insightful)
I said it before and I will say it again. If you don't have the latitude in your life to quit your job, you are at the mercy of your employer.
Nine letters (Score:5, Interesting)
You help the company out of a hole, then they can give you some extra time/bonus/spare computer/whatever afterwards.
If you can prove to be flexible and valuable, then the company will want to keep you around. The flip side is that you signed up for a reasonable workload, not 12/7. There is no need to be screwed.
Therefore try to figure something out to keep it win-win.
Law of diminishing returns. (Score:5, Insightful)
(http://www.alioth.net/ | Last Journal: Sunday December 02, @05:43AM)
12 hrs/7 days in a thought-intensive job is fatiguing (I know, I've been there and done that). After about a 50 hour week, you start hitting diminishing returns. After about 60 hours, in my experience, you start getting negative returns (the project actually starts regressing) because more bugs than good code is put in.
Is there a proper software process in the firm? I think not if they agreed to those sort of terms.
hire some more temorary workers (Score:4, Funny)
We all would love that to be true, but it isn't (Score:5, Insightful)
The sad truth is that you are right (Score:5, Insightful)
(http://communitycolor.com/ | Last Journal: Monday November 19, @12:08AM)
Of course, trying to keep employees primed at 60-80 weeks leads to burn out. The IT work load generally is cyclical as well. There is a killer deadline, people have to be give their all to meet the deadline...then there is a shallow period.
In the ideal world, companies would realize this and allow IT workers much more time off with pay during slow times.
Re:The sad truth is that you are right (Score:5, Insightful)
(http://slashdot.org/)
Why should they when they can save money by just firing them, and hiring more desperate programmers when they need them, or just not renewing contract employees?
It's win-win! Employees get their time off, and companies don't have to pay for it!
Re:Law of diminishing returns. (Score:5, Interesting)
(http://www.rigidsoftware.com/ | Last Journal: Saturday September 24 2005, @11:58PM)
Thats when more equals less. Like having a car with the choke stuck. If you mash the gas, it will just stall...
Re:Law of diminishing returns. (Score:5, Interesting)
(http://mannu.livejournal.com/)
BTW has anyone noticed this trend with MSFT? They produce a poor 1.0, and by 5.0 (a few rewrites later?) it's robust, feature-rich, and popular.
As I said, sometimes the "first version is meant to be thrown away", so it doesn't matter how many bugs. The time-to-market is more important in introducing a product. Moreover, the team can take a 2-5 day break, and come back to code version 2.0 at 8/5 pace.For projects, the more the no. of bugs, the better it is, because they can keep billing the client for the mythical man-hours put in for fixing them. Project-companies with hourly billing gain both ways (12/7 followed by bug-fixing cycles).
Re:Law of diminishing returns. (Score:5, Interesting)
The differences between my situation and the original posters were several:
a) We were on an aircraft carrier, and had no say in our working hours. Frankly, they could have been much worse: some groups worked 5 hours on / 5 off, or 12 on / 6 off for months at a time.
b) We had limited outside distractions. No commute, no having to mow the lawn or paint the house on weekends, no grocery shopping, no cooking. Our job was just to fix avionics boxes, and the system was optimized to keep us on task and productive.
c) You have to get used to the hours. The 8/40 work week is a relativly modern invention - our bodies will work much longer, it's just that our brains aren't used to concentrating so long.
All that being said, if my boss told me that my job depended on working 12/7 for months with no bonus, pay raise, or comp time then I'd walk.
Difference (b) above is a big one - if I have to work 12/7 as well as commute, grocery shop, and maintain my house and car there is simply not enough time left in the day for everything. I didn't go to college for 6 years to work the hours of my great-grandfather the farmer, who got up before sunrise and slept after sunset.
Difference (a) is the clincher, though. Once you enlist, they *own* your ass and you will work whatever hours your semi-literate boss dictates to you. If you tell him to fuck off, you can go to jail, be fed bread and water, or in wartime, be shot. After eight years of experiencing that environment, I'm fully aware that as a civilian I can quit at any time for any reason - this is a luxury that I've earned, and I see no reason not to use it when the conditions of my employment start being arbitrarily changed.
Re:Law of diminishing returns. (Score:5, Insightful)
(http://www.alioth.net/ | Last Journal: Sunday December 02, @05:43AM)
I've done non-code jobs where there were 12-hour shifts, and it wasn't a big deal - it *is* possible depending on the work. However, in my experience, writing code isn't one of those jobs where you get a linear increase in work done for each hour worked by an individual, and in my experience when you go past a certain amount of hours per day/days per week, you reach diminishing returns, then negative productivity.
From what I've seen, 60 hours/week with code is about the most before negative productivity begins to creep in. Also, consider the fact when you joined the military, you expected the sort of work you were given. When you sign a contract saying the normal work week is 40 hrs, 5 days a week and then are told to work a 7 day, 84 hour week (over double the hours) for no extra pay because management were too spineless to negotiate a better deal, morale doesn't generally get boosted meaning a double blow to the worker's productivity.
Is this even legal? (Score:5, Insightful)
Re:Is this even legal? (Score:5, Informative)
(Last Journal: Tuesday April 29 2003, @08:22PM)
programmers are an exception to the Fair Labor Standards Act of 1938 - 29 USCA Â 213(17) --
 213. Exemption
(17) any employee who is a computer systems analyst, computer programmer, software engineer, or other similarly skilled worker, whose primary duty is--
(A) the application of systems analysis techniques and procedures, including consulting with users, to determine hardware, software, or system functional specifications;
You can't get overtime as a salaried programmer. I am really sorry.
Re:Is this even legal? (Score:5, Informative)
(Last Journal: Saturday August 18 2001, @11:04AM)
I smelled BS on this but I was wrong: See the text of the FLSA, section 213 [cornell.edu], provision 17.
Sorry for doubting you, pcwhalen. (Might want to link such things in the future, to help people like me who don't take Slashdot comments at face value. Which should be everyone...)
That exemption really sticks out like a sore thumb, I think; take a look at the other exemptions and I think you'll agree this one doesn't fit in, except perhaps in the very limited domain of server operator (who may need to do something for 70 hours in a week, as a sailor might).
Re:Is this even legal? (Score:5, Informative)
Getting back on topic, the experience that lead me to contact the DOL was similar to that of the guy in question. My team was tasked with completing a project in an unreasonable timeframe. With months to go, we were told we had to put in 60+ hour weeks. This went on for about 10-12 weeks. There was a stretch where I worked something like 30 days in a row with just one day off. Productivity dropped sharply in those conditions and most everyone was talking about leaving (H1B's and all). After the project was finished, we were treated to strict 40 hour work weeks, and we had the appreciation and respect of most of the people in the company.
However, our graphics designer quit (with no job lined up), our development manager quit as soon as he could find another job, I (developer) just quit after getting another job, and the dust hasn't settled yet. We had a 9 member MIS department that they were planning on growing to 11 this year and now we^H^H they are down to 6, and a few others could still go. It probably would have been a lot worse had 3 of the remaining 6 not been H1Bs.
My advise to the poster would be, if you like your job and your management stick it out. If you don't and you have enough money to go it alone for a while, work a 40 hr week and see if they fire you (if you quit, you can't collect unemployment). If you can't afford to go it alone for a while, buckle down because unless you've got some good connections, you are going to be stuck at your job for a while. One thing I quickly discovered was that it is almost impossible to conduct a good strong job search while working 60-70 hours per week.
If you want to try to reason with your management you might want to try to illustrate to them just how unreasonable those hours are. For example, if you are a rookie making 45,000/yr that boils down to $865/week. Now imagine you are a sophomore intern in college making $12/hr. If you work 60 hours a week, you will make $840/week (12*40 + 18*20). Of course there's benefits and a higher stable paycheck, but it's downright insulting to say that a bachelor's degree and year or two of experience is only worth an extra $25/week.
One small point (Score:5, Informative)
(http://eff.org/ | Last Journal: Wednesday December 29 2004, @12:13AM)
A former employer pulled a similar stunt on a friend in a different department (5+ hours per week unpaid overtime). He quietly logged his hours on a daily basis with a brief description of what he did. After two years of this he quit (better job) and filed a law suit againt them. IIRC he just had to go to the state labor board and they got him his back pay and fined the company.
IMO I'd do the same. Mention once that you don't agree with unpaid overtime and log your work activities. BTW, judges/lawyers love to see hand written logs. Also check with your state's labor relations board. I wouldn't do anything big until you start work for someone else.
On a side note: where does it stop? Is the next step to start working programers (et al) like MD residents (70 - 80 hours per week, sometimes 36 hours straight). How many hours over 40 per week is too much?
Good Luck.
Seems like the first thing to do... (Score:5, Insightful)
(http://moofie.lastcoolnameleft.com/)
Is the company entitled to expect you to make this sacrifice? No. But then again, you're not entitled to expect that they will continue to employ you.
Negotiate. If you resort to lawsuit, the only people who will make money are lawyers.
Strike (Score:3, Insightful)
(http://www.markdnet.demon.co.uk/ | Last Journal: Saturday April 01 2006, @05:13AM)
12/7 is the best! (Score:4, Funny)
(http://scottgant.blogspot.com/)
And if you're married, it puts such a strain on your home life.
AND you're not being paid overtime either, which is icing on the cake!
Alternatives? (Score:5, Insightful)
(Last Journal: Tuesday June 11 2002, @01:20AM)
Well .. you have several options:
- Do the work like a good worker bee
- Do the work, but piss and moan to
/. about it
- Do the work, but piss and moan to you supervisor about it
- Start doing the work while looking for a new job
- Quit immidately
Summing it upThe question to ask yourself is: "How much do I like my current job and position? ... and ... Is it worth the lack of a life?"
Just $0.00232 (after taxes)
Re:Alternatives? (Score:4, Insightful)
They cannot make you stay and work once your contracted hours are over. Sure, if just you go home and everyone else stays then that's a different matter.... but if enough go home, they can do nothing but negotiate with you.
That goes double if you follow your boss out the door at 5:30
I suppose you can start working poorly, but that's hardly constructive, and the managers won't see it even if you write 'all work and no play make johnny a very dull boy' over and over in the code.
Re:Alternatives? (Score:5, Interesting)
(http://geekbiker.net/ | Last Journal: Thursday July 01 2004, @05:57PM)
- Do your work and submit your claim for overtime pay.
If you are in California, they MUST pay it, nor can they get you to sign an agreement to waive overtime compensation. After submitting your overtime claim, if they fail to pay you the proper amount on the next paycheck, submit your claim to the Labor Board. If they fire you, great, now they also owe you big bucks for illegal termination. Oh, IANAL, so you might want to verify this information.Demonstrating the need for IT Unionization. (Score:5, Interesting)
I think if you act collectivel and keep the community informed you wil have a lot of support and could be the beginning of something.
Re:Demonstrating the need for IT Unionization. (Score:5, Insightful)
(Last Journal: Saturday January 31 2004, @05:25PM)
Acting collectively sounds good. If you all agree something needs to be done, send a spokesperson or two to talk to management about this issue. Make it clear that the current deal (working 12/7 without compensation) is unacceptable, and make it clear that you speak on behalf of the entire department or project team.
I'd stay away from proper unions, though. Unions, like almost every other established organisation, primarily concern themselves with perpetuating its own interests... and those may not necessarily coincide with those of the membership or workers in general! For example: a few times unions here have called a strike even after managements conceded to every one of their demands. The reason? Membership was dropping, and a bunch of angry workers picketing in front of a blocked factory gate would look really good on the evening news, they figured.
Our own firm has had some recent dealings with unions recently, none of it very pretty. We've had some layoffs, and unions were pushing for us to implement a 'last in, first out' rule. Managent didn't want that, and especially the employees didn't want that (they'd prefer the deadwood getting fired instead, on a merit basis). But, for, some reason, this rule is a big deal for unions. I'm happy to say they didn't have much influence, as they represent less than 5% of our workforce (mostly educated IT consultants).
Some last thoughts: Be rational about this! Don't start off by banging your fist on the table, but strongly suggest that the proposed work schedule is unreasonable, especially without any compensation. If they keep refusing to remedy the situation flat out, it's fist-banging time... but only if you all are prepared to take it to the next level, up to and including quitting. Because in the end, that is the only leverage you really have.
Re:Demonstrating the need for IT Unionization. (Score:5, Insightful)
(http://www.pathname.com/~quinlan/)
Unions are just a plain bad idea for technical skilled people, especially the most skilled people. We're not just turning screwdrivers.
I've been an individual contributor, a manager, and a team leader all within the same company, usually going where the need was greatest or my skills matched. About half of my managers were engineers (and some were good managers) and they too changed roles from time to time. Unions assume that it's management vs. the employees. In addition to being part of either group, I was also a part owner of the company (through stock options). When I got laid-off, I knew it was the only option for the company at the time. Yeah, I thought bad decisions had been made before that point (and obviously, I thought laying me off was a bad idea, but those are the breaks, I wasn't going to cry about it).
In addition to all that, I'd rather be free to negotiate my own salary, schedule, etc. Being part of a union would not help.
Anyway, please keep your unions to yourself. I like being independent and being judged and paid according to my own work. If I can avoid it, I'll never join a union. It's one of the worst things that could happen to my long-term career and compensation prospects.
Re:Demonstrating the need for IT Unionization. (Score:4, Insightful)
(http://snort-wireless.org/)
Bank it (Score:3, Interesting)
(http://slashdot.org/)
6 weeks, 7 days, 12 hours = 504 hours
at 40 hours/wk this is 12.6 weeks
Yeah, you lose 6 rought weeks, but then almost 7 weeks of banked vacation to draw on, that's pretty sweet.
Another alternative if they argue some OT is expected, bank the weekends and everything over 9 or 10 hours a day, that would still be a few weeks off.
How long for, future promotions, and any Perks? (Score:5, Insightful)
(http://apl.jhu.edu/~mekkab | Last Journal: Tuesday January 30 2007, @03:45PM)
So 6 weeks? Is it limited to that? Because that's do-able. You work real hard, the end date comes and goes, and then its over- time to have a party.
Can you hold this over your managers head for compensation during the next performance review? It is worth a shot to mention it to him/her in clear language- I am a team player. I am busting hump. I want this reflected in my performance evaluations.
Also, are there any perks? Lunches provided on Sunday? Foosball table? Free movie tickets?
Maybe this should be suggested to management- 12/7 does NOT improve morale, and with tight deadlines thats when you need morale the most.
IF its only 6 weeks, this can be sustained. When it grows to 6 months, to a year plus, that is NOT sustainable. You break down. You wear out. Productivity goes down the tubes. And you break out into stress-related rashes. Its not a pretty sight.
What state? (Score:5, Informative)
(http://autopr0n.com/ | Last Journal: Saturday August 06 2005, @01:30AM)
Work 8 hours a day. (Score:5, Funny)
(http://seattletimes....001757992_kay06.html | Last Journal: Saturday December 07 2002, @12:29AM)
- A.P.
work from home option (Score:4, Interesting)
(http://libtom.org/)
Why not ask for a compromise?
Tom
Labor Board (Score:5, Informative)
(http://nokilli.com/rtw/ | Last Journal: Tuesday November 06, @03:20PM)
Ask them what you can do.
Alternatives (Score:5, Interesting)
(Last Journal: Thursday October 17 2002, @10:28AM)
1. Quit on principle and give your job to someone who doesn't have one.
2. Keep your job and lower wages for everyone.
You probably only have your job because you're salaried and cheaper than your hourly colleagues of equal skill. You made the concession long ago that you would take security over cash.
During the boom, labor will rule. During the bust, management will rule. Them's the rules.
I never follow the rules, but you're not me.
I am a contractor (Score:4, Interesting)
(http://www.livejournal.com/users/jackwilliambell/ | Last Journal: Wednesday November 12 2003, @12:20PM)
The downside? I have worked for nearly a year away from my home in Seattle because there is no contracting work available there, and hundreds of qualified applicants for every full-time job. Health Insurance if far more expensive for me. I am not paid for holidays and the closest I come to vacation is the period between assignments that I must often spend frantically looking for the next contract.
Plus contractors always get the worst desk / cubes / equipment because they are not part of the headcount (which determines space, equipment and office furniture allocations). I have literally worked at a table in a hallway before.
I have been on both sides of the fence and you know what? Freelancing and/or working through a pimp is better in one respect: We know the customer is going to dump us sooner or later. While you full-timers labor under the mistaken belief you actually have job security...
Do the math (Score:5, Insightful)
(http://www.chriscanfield.net/)
Employees are generally useless after 60 hours. After 80 hours, I can only recommend bringing a videocamera and selling it to "America's Funniest Home Videos."
Negotiate with your boss for A: two weeks of paid vacation starting as soon as the ludicrous crunch time is over, and B: two extra weeks of paid vacation to be taken sometime in the future. If that doesn't work, look for another job. It's unprofessional to demand such hours with no reward, and it is unprofessional to give in to such demands.
It would also help morale if the managers who made this mistake also stayed 12/7, though I don't know if it will help your position of you pointed that out to them.
Re:Do the math (Score:4, Insightful)
(Last Journal: Saturday January 31 2004, @05:25PM)
I had a great manager while working on a difficult project: launching a new service for a mobile phone provider. The service was already heavily advertised and the delivery date was set in stone as a result. We had to work some nights and weekends (though nothing as bad as 12x7 for 6 weeks). The manager was around when we were... not getting in the way and being a pain, but checking if we needed anything like extra help or equipment specialists or the like. And in the morning, she'd come round with coffee and breakfast.
In the military I learned: "One leads from the front, not from above". This applies to management as well, and in general the managers who share their team's hardships become part of the team rather than standing above it. They are also the manager who will get the best results and rarely miss a deadline, because the team knows that the manager will be on their side, and that their pay rise and performance reviews will reflect their success. Sadly, such managers are far and few between.
Day of rest? (Score:5, Informative)
Know your state's labor laws. (Score:5, Insightful)
1) Threaten to quit and hope they don't call your bluff. If they call your bluff, you'll like like an idiot of you don't quit. See #2.
2) Just quit "in-force" and watch them panic. With any luck (and hoping your other team members do the same), they'll do what they can to retain you. Make sure you have something else lined up or you won't be able to collect unemployment.
3) Suck it up and look really hard for a new job and pray the fire you for poor performance (that way, you get out of any non-competes and can collect unemployement).
Well, there's a fourth option, that's to quit and join the consulting firm your company has hired. Of course, that may not work either as they may have a non-compete/non-hiring agreement with your company.
If you choose #3, be sure to do the absolute minimal amount of work, call in sick a lot. Complain of illnessess like carpal tunnel syndrome, headaches, dizziness, back pain. And, be sure to visit doctors to get these "illnessess" on record. Then, when they let you go, you nail them for creating an unhealthy work environment and take them to the cleaners.
Baring that...a measure of last recourse...be sure to mutter to yourself and yell "grenade" or some other war time saying whenever your boss walks in. And, cover yourself with water so it looks like your sweating profusely and having some sort of stress attack. It helps, of course, to have some real legitimate combat experience to pull this one off effectively. Alternatively, you can come to work wearing trench coats and talk alot about your cache of weapons you've been collecting with your other, less stable, coworkers (who also wear trench coats). Make sure your supervisors overhear you. When they let you go, sue for creating a hostile work environment as, I assume, you don't truly have a cache of weapons.
Get even (Score:5, Funny)
You can't "WORK" for 84 hours per week. (Score:5, Insightful)
Let me offer these idiots (the people requesting a 12/7 schedule) a piece of advice: 84 hours per week is f---ing insane. You wind up with diminishing returns after about 50-60 hours/week. While 84 (or more) hours is very possible for a week or two, such a schedule will QUICKLY become ineffective immediately thereafter. You might be at work for 84 hours, but your mind won't. Whoever is running this company doesn't know that, which means they don't know how to run a company, which therefore means that the company (or your department) isn't likely to be successful, which you should take as an indicator of its expected lifespan. Get out now.
Cancel contract (show they will lose money) (Score:5, Insightful)
They need to look at any penalities that will incur for not delivering on time, or delivering a poor quality product that would incur a lawsuit for delivering a poor quality product, and the loss of bussiness from this and other companies when you get a reputation for delivering poor quality products.
There is no way you will make the deadline, so be sure that they know the potiential for them to LOSE MONEY is greater than the possibility of EARNING A PROFIT on the contract.
The timeline unrealistic. Any bonus for being on time will not be awarded.
Expectation of quality from overworked employees is unrealistic. They will be spending money on fixing this thing, even if they don't get thier ass sued for a poor quality product.
Large potiential to lose any reputation you have for delivering on the above two.
Yourdon's Death March - read this book (Score:3, Insightful)
(Last Journal: Monday February 20 2006, @09:53AM)
You've been invited to participate in a "Death March" project - if it fails, the company fails, if it succeeds, you ensure they're going to have you do the same thing again as soon as they find the right opportunity.
If you want to do something about it collective action is the only route and you're leaving yourself wide open to being replaced by contractors. I've been in this place before but I was a one man band
I don't see anyone posting who is looking at the bigger picture here. Software jobs are getting exported to places like India, where someone younger/sharper than you works for 25% of what you make. Are you nervous yet? This is the same thing that happened to manufacturing in the US in the 1980s and its going to happen to white collar jobs over the first twenty years of the twenty first century.
Globalization got you cheap tennis shoes and you didn't understand that they were going to end up on someone's foot planted in your behind, did you?
Don't be too hard on them, they're getting the same treatment from the management above them, who is getting it from the CEO, who is getting it from the board, who is getting it from Wall Street.
If you stay and want to be a hero (Score:3, Interesting)
(http://www.berylliumsphere.com/security_mentor | Last Journal: Wednesday January 31 2007, @09:13PM)
The way to do that is not, of course, to work 84 hours a week. Read Yourdon's book _Death March_. It's about the tactics that allow pulling off a project with preposterous resource constraints.
In a nutshell, put all the coders in their own offices, unplug the phones, put up barricades against all bureaucrats, compromise quality and ruthlessly, viciously prune features.
If your management thinks that working 12x7 will get the contract done, they don't understand project management. If they're willing to learn, you can show them and make yourself look great.
Is The Company Publicly Traded? (Score:4, Funny)
(Last Journal: Thursday April 18 2002, @07:50PM)
Is The Company Publicly Traded? Is the project going to form a major percentage of their revenue?
Short the company's stock.
One thing is certain: The contractors will figure out a way to keep the contract going, wasting more money, and all the code written by your group will look something like this:
From experience (Score:5, Funny)
That said the FIRST thing you should do Monday morning is to call your State Department of Labor. What you are being asked to do may be illegal.
NEXT, if you work at a big enough company, mention the situiation to your boss's boss or boss's boss's boss (aka Senior of Corporate Management ). They might not be in the loop about what is going on. This may be in violation of company policy. Or they may be smart enough to know the signs of a death march and take steps to stop it before it gets started.
But, if they can't help you you have a couple of options...
- Work the hours and don't complain.
- Explain to your management that it is not possible for you to put in those hours on such short notice. Explain the outside of work commitments that you have in your life. Apologise for not being able to work the extra hours, and then don't work them.
- Say nothing to them, just don't work the hours.
- Keep a log of when you and everyone else on the team comes in and goes home. Next time your review comes up show them what a good resource you are.
- Do the same as above, but put a packet sniffer on your managers PC. Next time you have a review, show them what a hard worker you are and what porn sites they have been surfing during business
hours.
- Start coming to work in a Star Trek uniform. demand that everyone refer to you as 'Commander'.
- Every day at 5pm hit the emergency power off in the server room and pull the fire alarm.
- Make generous use of the rm -rf * command.
The ground rules are simple... (Score:3, Informative)
Don't let anyone tell you otherwise...
At both the Fed level and in CA, 8 hours a day and 40 hours a week is the non-overtime cut-off. CA goes further by breaking hours down using a 1/40 fraction. And you must have 1 day off for every 7 days...before continuing work unless (yep, there are usually exceptions) an emergency exists that threatens property or life.
Now here is where folks who fall into "professional" fields (not doctors or teachers in this example) get confused. Especially in CA.
If you for example as an IT person get loosely labelled a "computer professional" here in CA you pretty much can't duck it so long as you are not a trainee or paid less than 41.00/hr. The label sticks in most courts and Labor offices.
So what happens when you work overtime as a "computer professional"? Well, you don't get 1.5 or 2.0 multiplied to your hourly wage. Nor do you get minimum wage or a multiple of the minimum. What you really get is straight-overtime. In other words, you continue to get paid just your hourly wage. No more, no less.
This law under Section 510.00 onward under the CA labor code was obviously passed to keep companies from getting killed by mutiplier overtime on employees who are very expensive to being with. It was a break given to companies and the state as well for teachers, doctors, etc under different professional classifications and schedules.
Each state and the Feds have differences on professions and the minimum that professionals must be paid to be declared as such...do your research.
Keep records, and get ready to push the issue. Nice thing about the Fair Labor Standards Act is that if you keep track and provide a bill for overtime - and your employer hasn't done the same using a certified time piece or tracking system - they get stuck with the bill. Have an attorney ready too who if familiar with that act and other relevant labor info.
On the other hand, if you can't stand on your own two feet - you are better off quitting. My experience has been that companies or managers who try to claim salaried employees are not entitled to overtime are operating under questionable leadership and headed for recognition on Fucked Company.
=8-)
just make sure you are compensated.... (Score:5, Insightful)
(http://www.slashdot.org/ | Last Journal: Tuesday July 22 2003, @01:21AM)
I have been put in simular situations many times (though not as severe), and have never ever been refused compensation. Of course, I've had to negotiate compensation, often the management don't realise how much this will cost them. And when you do negotiate, do it up front, before starting the work. Oh, and make sure they know it is *not* negotiable. You need some sort of compensation.
Just remember, a normal day is 8 hours, so a normal week is 40 hours.
They want you to work 84 hours a week. Thats double. IE, in those 6 weeks you will be working an equiv of 12 weeks.
A few ideas:
* Get paid a bonus equivelent to 6 week wages.
* Get 6 weeks of paid leave.
* Some sort of combination.
* Be pepared to compromise a little...work 10 hour days, and get 12 days holidays (IE get back your weekend time, and work 2 free hours a day)
A few no-nos:
* a long weekend is not fair compensation.
* Providing you lunch on Sunday is not a "fair exhange" (How much are you worth?)
* Tickets to your favourite sporting match is not compensation.
I prefer the holiday option (time in luei), as I can spend time with family and friends.
Just remember...the managers are human too, and they do care. They are more likely to offer you the holiday option, as it doesn't cost them more. And they do understand that it is fair they compensate you for your time.
The thing to remember is to be firm. Don't offer or threaten to quit. Just tell them...yes, I will work the extra hours, but I expect to be fairly compensated for those hours. If they won't budge, work 8 hour days. They can't fire you for working what you were hired to do.
At the end of the day though, its your decision. Not the companies. If this is the life you choose to live, and you want to work for this company. Then do it.
I dont get it... (Score:4, Insightful)
(http://slashdot.org/ | Last Journal: Thursday August 12 2004, @10:57AM)
Why the obvious political weight of the place is not applied to this situation.
Is the demand for work wrong? (I think it is.) Then name the damn company! (and the client) Better yet, put a link to their web site so they friggin notice.
The cat will be out of the proverbial bag then and all sorts of things might happen;
- the client realizes they are being dumb and backs off
- the company realizes a huge list of potential employees just decided not to work for them, and backs off
- potential purchasers of stuff from this client or company can avoid this product. I can tell already it's going to suck. What if it's the control system for the new Nuke plant... or computes YOUR salary or something, think about it.
- people can dig up facts about the laws in the state, county and city, forcing the company to back off
- they gotta pay for bandwidth, and the programmers can sit back and watch the smoke billow from under the server room door knowing something they did made a difference
Remember, it's not slander if they don't catch who said it, and it's not slander if it is true.
Get compensated. (Score:4, Interesting)
Say you'll be putting in 5 months of work in 4 months. Ask for 4 weeks vacation to be added to your personal leave.
If they say no, don't threaten to quit. Just interview elsewhere, get a job, and leave.
Get the request in writing (Score:3, Insightful)
Then don't work all those extra hours - work 12/5 or 10/6 and let them fire you if they want. Then if they fire you for not doing 12/7, sue their ass for wrongful termination and for the unpaid overtime you did so far. As an exempt employee, they are not supposed to be counting your hours and penalizing you for going below a ridiculously high amount.
But have you asked? (Score:3, Insightful)
But...have you asked about compensation of some form? If you don't ask, a money-tight company (or insensitive boss) won't think to offer. However, if you ask they just might see your point...
I'm not saying that it's right that you are in a position of having to ask. But if you don't ask, then you won't know for sure that the above statement is true. If you do ask and they say "no", then see those "Q-U-I-T" threads above ;-).
Ah, the old Death March (Score:3, Insightful)
(http://www.slashdot.com/~proudrooster)
1. Lie down and get kicked.
2. Q - U - I - T
3. Organize, play along, and turn then turn the tables at the end.
You didn't mention the margin on this deal and that would be a very good thing to find out before excercising Option #3. If they are making 500% profit off your blood, sweat, and tears then I would definately go after some of some of that cheese. If they have no cheese to give, you might as well start looking for another job since this project probably won't finish on time and the company is sunk anyway.
However. if there is money to be made. First, I'd organize with the the key people on the development team. Then I would start the death march and work hard on the project. On death marches, people start quitting after the first few weeks because they can't handle it. Once the pack leans out a bit and there is no hope of finishing this project with replacement developers make your collective demands. This is called collective bargaining. Also, get any CASH you want UP FRONT. Don't take promises, take CASH UP FRONT or you will NEVER SEE IT.
Also, if the mandate is 7x12 then make sure everyone one the team works 7x12. If anyone is excused from working for any reason then make sure you take equal time off. Those with kids and families tend to get breaks like working from home and weekends off.
Remember that no matter how much they yell and scream, you are NOT a slave.
I guess this is what Greenspan was talking about when he said, "Employee productivity gains have been made."
I would leave (Score:4, Insightful)
(http://obfuscated.net/)
I think we have our selves to blame when we can't afford to do this, and I've been guilty of it in the past, which is why I changed my habits. You see, I generally can afford to quit a job, and I've done it before. By having saved for more than just those days when I stop working for good I was able to quit. By being sucked in to the consumer machine we spend and spend without thought to consequences. While many of us save for retirement and a rainy day, not to many save six months to a year of living expenses so that we can be in control of our work day.
This company believes they have you. For most of the poeple there they probably do. You can't afford to quit long enough to find a new job, so they will do to you what they can. If you can't afford to leave the job, at least use it as a reminder next time your looking at that new CD or adding 20 new cable channels you will never watch, or upgrading that computer you bought last year. There's a deeper price to pay than the money. That money is your freedom. Freedom from control.
When you shop, when you buy things, when you use the credit card, think about it. Think about what you could do if you could afford to take a year off to find the perfect job. Think about what you could do if you could take a year off to get a consulting business off the ground. Think about what you could do if you have the choice to do it. Money gives you that choice. When I'm working my goals are to get one year salary saved, seperate from retirement and savings for other things like a new car or home, and it's worked. When a previous company was going the wrong direction I was able to simply walk in to my managers office and hand him a polite letter saying that I was leaving for personal reasons and planned to take some time off.
Whine, whine, whine (Score:3, Insightful)
There was a case in the Northeast a few years ago (Score:3, Interesting)
I can't remember the details, but the gist was simply this,,, if you were an hourly worker, federal law would require compensation for you overtime and that compensation would be at an inflated rate. If a company chooses to make you a salaried employee, the concept is supposed to include a certain amount of flexibility in your job that acts as compensation for the overtime pay an hourly employee would get paid. Things like flexible lunch breaks and flexibility in when you work are expected.
In the case I heard about, a company had treated their employees like hourly employees, absolutely dictating every detail about their schedule and even requiring them to punch clocks for record keeping purposes. The employees brought a lawsuit against the company for back pay on their overtime using the same 1.5X normal pay to 60hours, 2X normal pay on Sundays, 3X normal pay on holidays rules that they would have received by law if they had been classified hourly employees. I heard that they won, but didn't hear whether any appeals process was followed.
So, there is a limit to what they can demand. If they are offering some form of compensation like 3 day weeks for a while later, I would think that you've got no case. If not, and they are treating you like hourly employees, you should consider breaking the business relationship if you can as a first resort, but if that isn't possible (i.e. another job can't be found) you should keep careful records including anything written that describes this policy and any other policies that seem like the kind that would be employed with hourly workers and consult an attorney.
Your job is toast, whether you quit or not (Score:3, Insightful)
If a client insisted to IBM or EDS that they must have the project finished by the same fixed date after the client delayed it, they (the client) would get the contract shoved up their ass.
Walk away (Score:3, Informative)
(http://veraperez.com/ | Last Journal: Thursday January 12 2006, @11:14PM)
Weare all familiar with how customers screw us during the life of a project. They wait til it is too late to sign the statement of work, push our net 30 to net 45 or worse, come up at the last second with mods we never agreed with and are NOT in the contract, etc. All these are normal. The problem is when your company lets the customers screw them even before the contract is signed. Just because they are your biggest client it is no excuse to risk losing money on the contract just to keep them happy. The customer knows exactly what they are doing, and if you let them do it now they will do it again and again.
Back at my previous job we had a lot of business with about 5 divisions of a huge american conglomerate. My programmers used to hate working on these projects because the internal clients sucked. I started keeping track of all these separate customers (I was managing the programming team but was not project manager, so I did not have day-to-day contact with all the clients) and noticed a disturbing trend: except for a wild variation in the mood of the customer, all of them tried to screw us with the same excuses and delays! I started digging around and found out ALL employees that have responsibility over software projects are trained by that company in how to intimidate small shops into this kind of behavior!
Don't be misled by all the BS talk about the economy going to the crapper. There are tons of jobs out there! It took me over a month to find a good consultant to offload some of my excess work because there are not enough good programmers out on the street.
I know its pretty obvious but... (Score:3, Insightful)
(http://www.karasu-log.com/ | Last Journal: Wednesday March 05 2003, @02:15PM)
If you don't quit, then shut up and take it, just like you deserve to.
My religion won't allow it! (Score:3, Insightful)
My religion does not allow me to work on Sundays. It isn't extreemly strict, as the preacher say, illness doesn't wait, so if I need an emergency room I don't want the doctors to wait until monday to do surgery. So we cannot tell doctors to not work sundays. And there are many other reasons that you may have to work sundays. However if your job isn't critical to life in some way (you know if your job is really critical to life) and you have to work a lot of sundays, then there is a problem. Doctors are encouraged to find some other doctor who doesn't care about working sundays and switch, but that isn't normally possiable.
More improtantly, about half the people in the US belong activly to a religion that prohibits working on a Holly day. (normaly sunday, but some saterday, and I think Muslims have a different day) You should have no problem telling your boss that your religious health is more important than anything on earth. (in most religions anyway).
p.s. check your local unemplyment laws. In Minnesota the law allows you to get unemployment if quit for a reason that would cause a normal person to quit, and a change in working conditions is one example givin. You should seriously check this option out. Unfortunatly it is a tight market, I've been looking for a programing job for almost a year, which is longer than unemployment lasts. Consider it, but I don't know your situation, or your local laws.
Oh, that's easy. (Score:3, Interesting)
(http://205.205.253.95/Crackster | Last Journal: Wednesday September 22 2004, @09:57PM)
Do they have sealed isolation cubicles? (Score:4, Insightful)
(Last Journal: Wednesday April 09 2003, @03:17PM)
- Physiology: increased stress = decreased function of your immune system. Insufficient sleep = increased stress.
- Human factors: if you're on a team, you don't want to appear to be doing less work than the others.
- and the numbers: 168 hours in a week. 84 for work, 56 for healthy sleep...28 for everything else
Assume all developers find a way to work 12/7: they cancel all vacations, classes, conferences, workshops, ceremonies, weddings and funerals; they telnet into religous services (and never mind all the caselaw protecting rights of religious expression when, for example, it includes having a day of rest); they suspend all taking care of children or parents (nevermind the family medical leave act)...So what happens the first time one developer gets exposed to a cold or the flu? Under regular 9/5 circumstances you might just say "Look, I'm coming down with something. I'll head out early today to sleep it off": you make up the time later, and everyone appreciates that you didn't expose them to the bug. Instead, under the 12/7 situation you're going to try to tough it out. You won't get the extra sleep you need, so the illness just gets worse. Because everyone else is sleep deprived, more people are likely to catch the cold from you. Because there is no room for errors / illness / humanity in the schedule, anyone who falls behind will be aware of how they're holding everything up. This causes stress. Stress causes illnesses to last a lot longer. Interesting negative feedback loops ensue.
And this is assuming everyone is gung-ho for the 12/7 plan. What happens when one developer gets creeped out over having to skip a funeral and decides the only choice is to quit? There won't be time to train a replacement: those 84 hours'll have to be absorbed by everyone else.
And that's just the people: that 12/7 schedule doesn't have wiggle room for all the standard crashes, viruses, connectivity failures, power outages, traffic jams, major news events, and other standard slowdowns in modern office life. Someone in management there needs to buy a spine and give the client an honest timeline.
OK. Practical stuff. (Score:3, Insightful)
I am a reasonably senior manager in IT. I have been around a bit and here are the facts.
A)
It is the resposibility of your manager to report to his manager, up the line to the CEO. The CEO works for the board. The board DO WHAT IS BEST FOR THE COMPANY SHAREHOLDERS. Not you. I'll come back to this point as its important.
B)
Any student of HR will understand that 12*7*6 is not tenable. Per day, assume 12 hours work, 1 hour break, 2*0.5=1 hour commuting, 8 hours sleep, 1 hour breakfast/wash/shave, 1 hour evening meal. Add it up. That is 23 hours. That leaves 7 hours a week for other things. Grocery store 1 hour, washing clothes 1 hour, etc. 12/7 working not only destroys your social life, it is MATHEMATICALLY intractable.
C)
Any student of psychology will know that in a given team of (say) 10, 2 will go the distance, 2 will do it under duress, 2 will do it but badly (see B, above), 2 will do a half-assed job and 2 will simply quit. Its a bell curve of human behaviour and RESPONSE UNDER PRESSURE. Thats the key. Some personalities (like mine) - Briggs-Meier ENTJ will simply quit. Google for Briggs-Meier, look at the behavioural motifs and then the responses of each type under stress. I predict you will lose 25% of your effectiveness over the duration of the project.
D)
I assume most people are familiar with the mythical man month so I wont go there other than to say hiring new contractors wont help.
OK. So what do we do. There has been good advice about not being the guy to put his head above the parapet. Especially in this market. So draft a letter, all sign it, and deliver ANONYMOUSLY to your management.
Make the points above. As a responsible manager, they SHOULD see impending doom and go straight back to the client and negotiate an extension such that critical cuntionality is delivered on-time and less critical thereafter. They can sweeten this with free support later. They HAVE to spread this load or the team will walk. There, you have turned this debate from a "they are trying to screw us - f*ck them" into a BUSINESS DECISION. Business is about weighing up risk. They need to clearly understand the risks. I can now refer to to point (A). The company's interests are clearly not served by doing this. What are the penalties if they fail? Can they risk failure if some of you guys take the ultimate sanction and walk. I refer you to point (C): other posters tell you to quit whiing and/or knuckle down. Yeah. Whatever. The truth is that certan personalities will QUIT whether it is logical to do so or not. Some personlaities UNDER PRESSURE will resort to self-destructive behaviours such as walking out with no job to go to and even sabotage. I have seen it happen.
Document EVERYTHING. If HR get involved (they will have to in this one I think), if people get fired, quit, sue (the whole gamut is possible - nay, probable here) you want to have some arrows to fire. Even if there is nothing to document - document the fact that there is nothing. Do it NOW.
If you win concessions, carrots, etc from management, get it up front and guaranteed IN WRITING from the guy who will ultimately write the cheque. Clue: that wont be your line manager. In these times, it's likely senior management/CFO. Your manager will piss and moan about you mistrusting him but the risks here are too great to not do it.
Regardless, get the company to formally request each of you in writing to do the work. Even if you as salaried employees are expected to do certain unpaid overtime, in a LEGAL situation the court will generally ask whether the request was REASONABLE. 12/5 or even 8/7 (sixtyish) hours might be reasonable but 84? for two months? in summer? Hmmm. A judge will have a long hard look at that.
And final
Form a Union! (Score:3, Interesting)
(http://www.qsl.net/wa2mze)
demand the overtime (actually DOUBLE time) and tell them you will all walk out in mass if they don't agree. Also have them sign an agreement guaranteeing everyone at least a year's employment after the contract is over (anti revenge clause).
If management doesn't agree they will doom the company by loosing the contract.
Start with No (Score:3, Insightful)
Re:Move to a country like canada... (Score:4, Informative)
Jason
ProfQuotes [profquotes.com]