Productivity Tips for Programmers
Ombu Labs, April 2015
Productivity = Flow (hs) - Interruptions (hs)
“A state of concentration or complete absorption with the activity at hand and the situation.” Mihaly Csikszentmihalyi
Interruptions kill productivity
A programmer takes between 10-15 minutes to start editing code after resuming work from an interruption. [source]
“Hey! Can you help me with this?”
Email #32334 Subject: VERY URGENT stuff
@etagwerker hey, check out this gif! #Twitter
Keep your phone on vibrate/silent mode
Don’t keep your email client open
Keep Slack’s notifications silent
Ignore office phone calls
Don’t interrupt someone with headphones on
Start your Freckle timer widget
Monotask more, multitask less
Sometimes interruptions are good
Go for a walk if you can’t solve a problem
Ask another developer for advice on a problem
Rubberducking on Slack or face-to-face
Manage your interruptions wisely