Back

@Patricia same. for me, i mitigate it with breaks. often a walk or a nap. but it is amazing that the societal norm is “8 hours at your desk”. i am more productive in fewer hours by breaking it up

@Patricia I call this "The Bob Effect", after someone I worked with, who would stay later and later, sometimes all through the night, and by the morning, he'd have performed negative work, because his exhaustion-addled mind had actually destroyed existing success while trying to figure out why his previous exhaustion-driven work wasn't working right. The next morning, someone sent him home to get some sleep, while they reverted the changes in version control, and occasionally in the process fixed the very simple thing he was too tired to adequately notice.
Go home, get some sleep, fix it tomorrow. There are two good times to stop work: when you're getting somewhere, and when you're not getting somewhere.
And if you're reading this, Bob, it's not you. It's another Bob. I worked with a lot of Bobs.

@Patricia amen

@Patricia how do you want to measure effort needed then?

@Patricia I had been thinking of something along these lines for a while. Your post inspired me to finally post a draft:
https://hachyderm.io/@smurthys/111541797972969876

@Patricia also sleep isn’t linear either, it’s closer to logrithmic

@Patricia Do you have thoughts on handling this when hiring people?
If you have two candidates for a job, one offering 30h/w and the other 40h/w, but both for the same salary:
Are there convincing arguments the former could make? Or conversely how do you verify the 40h person is consistently doing useful work?

@neobrain @Patricia Is it an interview or an auction of hours?

@Patricia *2 hours left of the work day/week*
Should I code some more? Not very tempting. Odds are I'll just have to re-do it on Monday.