Yikes. So many things wrong with this. Firstly, hours in != output. At my last job, we had several guys working 60+ hours / week whose output was miserable. I

Yikes. So many things wrong with this. Firstly, hours in != output. At my last job, we had several guys working 60+ hours / week whose output was miserable. I put in 5-6 hrs / day and was easily 2-10x as productive as them. Secondly, work/life balance is real. As a lead, I tell my team they should absolutely not be working over 40 hours, and I won't do so myself unless I've fucked something up that's mission-critical. I'd advocate for a shorter workweek but my boss is very old school. Thirdly, I don't think you can put in long workweeks and be productive long term. Most people just waste time when they work longer, and their productivity goes down, not up, and their mistakes go up. In dev, especially at startups, a single mistake can cost you your business. Do you really want exhausted workers in your codebase? The truth it you should work however much you feel comfortable for the money you're getting. That's different for everyone. But if I can provide several million in revenue growth with a few hours of effort per day, then I figure I'm more than paying for myself. If you're willing to work 80 hours while getting paid the same as if you work 40 and being as productive as working 20, that makes you stupid and servile imo, not dedicated.