shut up, watch, and learn. Spending years dealing with unreasonable drop-dead dates developed by clueless PMs and managers who pulled the date out of their butt instead of evaluating the true effort to complete the project THEN set the date, then you can complain. Spending years rewriting/reconfiguring your work because the requirements change but the date doesn't, then you can complain. Spend years dealing with people who have to finish their task before yours can be completed but since you are the last guy, you get the blame if it's late, then you can complain. Spend years dealing with vendors who promise "our product can do that!" but turns out that the limitations of the tool are not discovered before some non-techie manager buys it and all you have to do is "make it work", then you can complain. So, have a cup of coffee, mind your business, and enjoy your halcyon days.
It really depends on a number of things, the company you work for, whether you're salaried or paid hourly, whether your single or married, with children or without, two income couple or one, or even if you're saving for a house.
To better qualify the question: for you folks whose companies are requiring more than 40 hours a week, how many hours to you work?
Heck, you might work 80 hours a week between 2 jobs but are you doing so because you want your kids to go to an Ivy League college? Is your standard of living higher that your 40 hour paycheck? Who's responsible for extra hours?
My old college professor made us memorize a definition of an 'OS' and tested us on it every friggin' chance he got. It comes as close as anything I've ever come across. 'A collection of system software that acts as an interface between the user, hardware, and application software. It is also a resource manager.'
Slashdot Mirror
shut up, watch, and learn. Spending years dealing with unreasonable drop-dead dates developed by clueless PMs and managers who pulled the date out of their butt instead of evaluating the true effort to complete the project THEN set the date, then you can complain. Spending years rewriting/reconfiguring your work because the requirements change but the date doesn't, then you can complain. Spend years dealing with people who have to finish their task before yours can be completed but since you are the last guy, you get the blame if it's late, then you can complain. Spend years dealing with vendors who promise "our product can do that!" but turns out that the limitations of the tool are not discovered before some non-techie manager buys it and all you have to do is "make it work", then you can complain. So, have a cup of coffee, mind your business, and enjoy your halcyon days.
It really depends on a number of things, the company you work for, whether you're salaried or paid hourly, whether your single or married, with children or without, two income couple or one, or even if you're saving for a house.
To better qualify the question: for you folks whose companies are requiring more than 40 hours a week, how many hours to you work?
Heck, you might work 80 hours a week between 2 jobs but are you doing so because you want your kids to go to an Ivy League college? Is your standard of living higher that your 40 hour paycheck? Who's responsible for extra hours?
My old college professor made us memorize a definition of an 'OS' and tested us on it every friggin' chance he got. It comes as close as anything I've ever come across.
'A collection of system software that acts as an interface between the user, hardware, and application software. It is also a resource manager.'
See, Bob I still remember!