>>>Also - this 40 hour a week thing. It really depends on the industry and the type of work. Certainly working 60 hours consistently will negatively affect most people. It's unrealistic to expect certain positions will only need to work 40 a week at all times - sometimes you have crunch times a company indeed needs "all hands on deck". This IS an area where I wish companies would pay more attention - I see organizations that pay lip service to creeds of "we don't want people to work weekends, we want people to have quality of life" but repeatedly break it. So I understand where Tamar is coming from.
>>>
>>Sure does depend on kind of work. Adding 10 or 20H of meetings is possible, adding 20H of coding draining...
>
>Adding 10 - 20 hours of meetings would drain me a lot more than 20 hours of coding :-)

Most of the times in meetings 60% of time is wasted on making sure nobody is left out of the loop - as this could mean they are NOT adding to the company by being there. Good time for half naps as long as you have set markers to spring into action when some critical point is touched. Coding is more fun, but doing it all day will get poorer code - I need to spinkle in naps, physical activities and other stuff. Meetings (corporate ones) are often just billable other stuff, as long as they don't grow to more than 25%.