### Latency numbers every professor should know
Email from student ............................ 20 sec
Person at office door ......................... 8 min
Other interruption ............................ 20 min
Twitter or something seems really important ... 45 min
Anxiety about deadlines ........................ 1 hr
A meeting ...................................... 2 hrs
A meeting you forgot about ..................... 1 day
A class to teach ............................... 2 days
Request to review a paper ...................... 3 days
Request to write evaluation letter ............. 6 days
Stuff to grade ................................. 1 wk
Unsolicited time management advice arrives ..... 2 wks
Fire alarm clears building ..................... 3 wks
Travel to conference ........................... 5 wks
Paper deadline ................................. 6 wks
Grades due .................................... 16 wks
Grant proposals due ........................... 26 wks
Summer ......................................... 1 yr
Sabbatical ..................................... 7 yrs = 2.208e+17 ns
With apologies to the folks who published latency numbers every programmer should know.
3 responses to “Latency Numbers Every Professor Should Know”
Brilliant! 🙂
Some are parameterized:
Realizer there is a bug in long-running experiment that invalidates all results: (runtime of experiments – 10%)
Alex, true!
Also the unsolicited time management advice tends to fall off over time and you thankfully don’t get it after tenure.