Bad news: it's unlikely you can work longer hours productively. Good news: working more hours is the least effective way to be more productive. The key to pro

Bad news: it's unlikely you can work longer hours productively. Good news: working more hours is the least effective way to be more productive. The key to productivity is reducing unnecessary work. That means: * Things you think the customer wants, but actually they don't. * Things that are nice to have, not on critical path to success. Sometimes the customers thinks they want them, but often they won't care if they're not actually there. * Things that are "best practices" generically but not applicable in particular situations. E.g. unit tests if this is code that will never be reused and you have an end-to-end test. * Digressions where you go off on a tangent and realize too late. This can be solved with timeboxing. I could go on. In general it's possible to be far more productive while still working same number of hours. More suggestions here: https://codewithoutrules.com/2016/08/25/the-01x-programmer/ https://codewithoutrules.com/2016/08/25/the-01x-programmer/ More conceptual overview here: https://codewithoutrules.com/2017/10/04/technical-skills-productive/ https://codewithoutrules.com/2017/10/04/technical-skills-pro...