It was fun to play the hero and get 'That One Critical Feature' out of the door for an important demo. It is a rush. Investors like it. Engineers like it. Soon a company is always in crisis mode; pushing hard to get the next great thing out. It becomes the culture.
At one company I worked at the VP of Engineering was the hardest, longest working person I'd ever met and a driver of that culture. No matter how hard or long you worked, he could beat you at that metric without breaking a sweat. There was a lot of pressure to live up to that example. Mostly I didn't mind because solving problems on a deadline is fun. Mostly.
Eventually, inevitably, that lifestyle started catching up to us. Nerves were frayed. Small technical disagreements started to stretch on into weeks long religious cold wars. We started losing good people who had the good sense to see what was happening.
Those of us who believed in the company and product stayed on, even thrived at some level.
After a few years of this something drastic changed. Our VPoE mother died unexpectedly. It hit him hard. He realized that he had been ignoring absolutely everything but the business. Everything. And the culture shifted on a dime. Engineers were no longer /allowed/ to be called on weekends whereas before we had to respond in 20 min. He would make it a point to go out with us after the workday, or even during the workday, to chat about life, the direction of the company, whatever. Most importantly, he ran interference when it came to the clients and laid down and enforced very sane timetables for completion of projects and features. And if there was a delay, it was ok...not the end of the world.
The product did not languish. Things still got done. Turns out clients, for the most part, could not care less how hard and fast we worked. Having good information for when something would be complete was sufficient. Sometimes better because we were not breaking ourselves trying to impress them with impossible deadlines that we would sometimes miss. Good information was better than fast information.
On top of that, the quality of the product improved. Crises mode was used too often as an excuse for shipping half baked product.
Creativity blossomed. Several revenue generating products were conceived and executed in the breathing space we all now had.
People started recommending talented friends to fill positions again...
Altogether, it was just a much better scene.
Now our criteria crisis is much more strict. It is basically "Will someone (client) die or lose their house if this is not done by some certain time?" If the answer is no, go home.
If you are managing people and part of your evaluation criteria, formally or informally, is "does that person work a lot of hours" or if your 'business stability' requires that kind of sacrifice on any kind of regular basis you are doing it wrong.
TL:DR Unless a client is going to die or go bankrupt if you or your employees don't work extra hours, go home.
This. After years of working at shops where putting out fires was the norm I took a position with a company that handles their client deliverables in the manner you describe. For the first six months I was constantly jumpy, waiting for crunch time to hit and slinking home at 5:00pm feeling vaguely guilty that I was done for the day.
I just couldn't famthom how we could be working on all of the large project initiatives in our pipeline with no screaming clients and no marathon code sprints.
After a year in a sane environment it'd take more than six figures to get me to go back to the soul-eating grind that is so typical in small dev shops.
However, this resulted in a bit of crisis addiction, followed by burnout. However, the CEO learned that crisis mode was a death march motivator. Suddenly it turned into crisis-this and crisis-that. Every small feature was a "drop everything we'll lose customers" crisis. It started wearing pretty quick. At some point he dropped the crisis act and just stated flatly that "your terms of employment state that you will work as needed, i need you now" the day before I had scheduled time off, and the "crisis" was getting a new feature complete for shipping in a year. Needless to say I got a new job.
Basically, I agree with clavalle - crisis mode if not used exceedingly sparingly can lead to a new set of expectations that will chew up a dev team.
It was sort of like this at one of my previous finance jobs where I was expected to work no more than 60 hours a week (due to their allotment towards me of salary + overtime). Sometimes on Friday I'd get to leave a bit after lunch, which was nice. Although that did mean earlier that week was kinda rough...
So, for example, I'm in crunch mode for the next week working X+3 or X+4 hours a day. And then I'm taking a 2.5 week trip to Nepal a month or so afterwards. Crunch time happens, and we can't afford to thumb our nose at it, but this system means that it can never become the norm.
Your system sounds good. Do you also have the flexibility of working weekends in lieu of weekdays or at home instead of the office?
I'm not sure how you get that out of what he said, you could conceivably care more about your job than anything BUT your family which is still a lot of caring, IMO
Why should it be any different for me than it is for you?
I can't ever get as passionate about working for someone because at the end of the day, I get 1/1000 of the profits and when push comes to shove, will not be able to make many of the decisions that matter.
My free time is worth everything in the world to me. I don't mind doing extra emergency work once-in-awhile. My problem is that at many companies, this is the norm (because they hire kids right out of college that don't know any better) and you are a salaried employee and will not get paid any extra for it.
This is exactly why I keep this a secret from every company I've ever worked for. From their perspective, I'm a great employee.
Serious stuff happens, it does not happen every other week.
Should we take him at his word or assume that he isn't precise when speaking? Both are bad signs.
Life is about living, not about working, after all.
Look I can't speak for the OP, maybe ze would quit the first week ze's expected to work 40hours and 1 minute. Saying "no more than 40 hours, unless a tornado hits the data center; or my close friend and co-worker's mother dies and he asks me to stay a little late to finish some of his paper work; or a bomb will go off killing a dozen orphans if we stop coding" might be more precise, but it's also less accurate because by listing off every one of a billion unlikely situations in which OP might be willing to work over time it creates the impression that 40 hours is a much more flexible limit than it is.
"under no circumstances will I work overtime" has a very clear meaning.
The OP said "under no circumstances will I work overtime". Someone says that he really meant "i will sometimes do overtime".
I said, "he could have said I will rarely do overtime, only for exceptional cases".
And you claim that this isn't more precise? Did you pass reading comprehension in grade school?
Think about what numerous people are arguing here. OP said, "under no circumstances do I work more than 40 hours a week" and a number of people insist that these words mean "sometimes I will work OT", and that it's perfectly clear. That's stupid.
Also, I absolutely would not tell a company that I want to work for that "under no circumstances" will I work any overtime. Nor will I hire someone that says such a thing.
As I said, you could simply have said, "I will only work OT in exceptional cases, and these cases should be rare". It doesn't take an entire paragraph to get this point across. You get the idea.
And that even a supposedly more precise phrasing suffers from the problem that the listener may not interpret the words the way the speaker intended them to be.
I personally feel that a categorical statement such as yours is less amenable to misunderstanding than a equivocating one. Thanks.
Anyway, we're generating heat rather light in this subthread.
"I screwed up, but it's 5:00 so I'm going home. Remember my childish contract? So long!"