> How do we stop me from doing that? By not hiring somebody who isn't a team player? Look, I don't know you, and sometimes there's a real deadline. But on a bi

> How do we stop me from doing that? By not hiring somebody who isn't a team player? Look, I don't know you, and sometimes there's a real deadline. But on a big project, I'd rather take two guys working 35 hours a week than one guy working 70 hours a week (all other things equal). And while most cooperations don't care about ethics, societies should. How the hell are you going to be a good parent after a 90 hour week? So we're going to rely on underpaid teachers to teach our kids everything? Hmm, I guess Adderall is the next best thing to parenting. All in all, nobody would stop you from being so stupid, and when you end up burned out, your fault. In a country with decent labour laws though the business might end up paying your salary during sick leave. Suddenly overtime is a massive liability. We could also make managers responsible. For example, somebody has a crash on the way home because he fell asleep at the wheel after weeks of overtime. The manager should have some blame for not managing the workload of his employers better. Of course, this is all moot as long as there's some asshole out there who thinks he needs to one-up everybody else and put in massive amounts of unpaid extra work. Generally though teams wise up to this quickly, and code written at 2am isn't an asset - it's a liability that somebody else needs to fix. I'll bet that's how your code ended up laden with technical debt, and I'll bet the next guy who inherits it from you will curse at the technical debt, maybe rewrite it in a frantic effort - and so the cycle begins again. It's always easy to make more money with a short-sighted view. In the long run, it's usually not worth it. But you only hear the stories about the exceptional successes, and rarely the tragedies.