3 ms·
Keep in mind that working 65-80 hours a week is actually really really bad for maximizing output. There's a large body of studies demonstrating this in a wide v
by itamarst 10y ago
Keep in mind that working 65-80 hours a week is actually really really bad for maximizing output. There's a large body of studies demonstrating this in a wide variety of fields. 40 hours is a lot closer to the sweet point for maximal output. See the references in http://www.igda.org/?page=crunchsixlessons http://www.igda.org/?page=crunchsixlessons
So, first, remind yourself a normal 40-hour work week is actually the best thing you could be doing for your employer long term. See similar point I made over at http://codewithoutrules.com/2016/02/24/go-home-already/ http://codewithoutrules.com/2016/02/24/go-home-already/
Second, the biggest benefit you can provide for your employer is coming up with the smart solution that reduces the amount of necessary work by an order of magnitude. And you don't do that by working real hard for a long time. You do that by thinking. And thinking is in part a thing you do in the back of your head while doing other stuff. See Rich Hickey's talk http://www.youtube.com/watch?v=f84n5oFoZBc http://www.youtube.com/watch?v=f84n5oFoZBc