I've never seen a 60+ programmer workweek schedule that didn't start generating negative productivity through reduced quality, technical debt and poor design ch

I've never seen a 60+ programmer workweek schedule that didn't start generating negative productivity through reduced quality, technical debt and poor design choices. In part, this is because high workloads are symptomatic of poor project planning, but it's also because overworked programmers make poor choices. Conversely, I've worked with companies that produced amazing, very high profile work under ridiculous deadlines and still got everyone out of the office by six. Obviously, limited crunch periods are unavoidable, but if your project plan assumes more than six to seven hours of productivity a day you're probably creating an unsustainable workload.