Bruno “btco” Oliveira's profile photoRoz Hussin's profile photoDanie Loots's profile photoIlyes Gouta's profile photo
How about interruption because a phone call? And that phone call is a user asking how to use the same software that the geek is developing a new module...

Yeah, yeah... The call center didn't handle the call, so the developer have to answer... Unbelievable? Welcome to real life... Be a developer is just the beginner.. :/ ..
I saved that graphic, thanks a lot Bruno... You rocks Bruno! (Brasileiro :) )
people say they wish they could be a kid again i feel the same the real world sucks!
Start your own business.. it's like be a kid again :)... (talk about me) ;)
When i see you i told myself that he will be the right person 
The real world does suck:%
But life goes on!!! U just got to make the best of it!!;)
How are you guys hope you guts have a goid weekend
Oh so true. That damned Thursday conference call. 
Dear Geeks,

You're awesome.

Will you now please stop wasting so much of the internet trying to convince the world that you're awesome?

Thank you.
Many of my days are very similar to these graphs.  Its not about being controlled and rigid, it's about losing focus.  At times I may be performing multiple tasks at once.  What seems to be a simple phone call or chat interruption can break concentration, which is not easily and instantaneously switched back on.
Midnight = highest productivity time
11-2am definitely productivity time for me. 
Ok. So why the peak at 4 am? Then a flat line until the dip at 8:30. Like who works at 4 am?
I know 4-5am is when I'm most effective!
gostei da nota de copyright mas será que é? :)
A correlation can be made about telecommuting, sick days, etc. (Yeah, I'm talking about you, Yahoo!) Perception rules the world.
Interesting. Wonder what the data set was. :-) 
I think interruptions can be tough for developers working with new tools on new and unfamiliar projects. (Junior developers most likely).
The trick is to keep everything really simple most of the time.
The disruptiveness of an interruption varies with the exact task. It all depends on how much accumulated "mental cache" is required to do a given task. On large refactorings with multiple moving parts in several modules requires several MB of "mind cache", a phone call or a "quick meeting" can be catastrophic because it deletes all that carefully prepared mental state which has to be built again. On the other hand, shallower tasks like linting for code style, etc, can be interrupted all the time without significant loss of productivity.
Yes - Interruptions can overwhelm the mental cache. - That explains it well.
I love the midnight-to-one productivity burst.
Yeah, really hits the spot. Great!
I wonder how the data to make that plot were obtained?
Did you have a daemon monitoring how many tests/LOC/changesets you made?
What is negative productivity? Disturbing your colleagues? Breaking things that did work?
+Bruno Oliveira Bruno, I'd really like to use your graphic in a conference I'm presenting in. Any chance I can get a copy of the original slide? All copyright acknowledgement to you, of course.
Story of my life, plotted on a graph! :)
The 9am part is the time of day when I'm not entirely awake yet and I introduce more bugs than I fix :-)
+Jürgen Christoffel thanks for sharing, that was a very interesting read! Brains are one of the most expensive asset that companies pay for, it would make sense that more of them would make sure they are being used efficiently by applying some of these concepts. It's only logical.
I love the negative dip at 9am. So true! (posted at 9:05)
Keep phone shut, email closed, IM answers only with a ticket ID
11pm-2am... peak.... so true!
4am-5am... spike.... ALSO true... (yawn! ...just woke up and heading into the morning dip)
I thought it was just me. But this graph so closely matches my own experience that it must be very common. I am not as weird as I thought.
Midnight-shift.net baby! this is amazing haha
+Tim OKane Its the opposite in fact. We don't want "discipline" ourselves to take on phonecalls while thinking about complex stuff. A burnout mostly occurs because of a lack of satisfying events during heavy load workphases such as: finally successfully implement some renitent piece of crap, because nobody called that day. And then go HOME because youre DONE and for that feature there are two more days on the schedule, wich you then can use to watch three seasons of X-Files eat chocolate and play with some fancy brandnew technology noone would allow you to use in the project. ;) If you're not married... of course.
Brilliant! Expect this to be included in books someday. I thought I didn't get the bump around 4 a.m. but now I think I do: the inspirational thought about how to solve the problem one has been thinking about the whole day without success..
Exactly, the bump at 4am is when you have that brilliant idea in the middle of the night and it solves all the problems you were thinking about during the day.
Bruno, how did you get this data? what exacly are you plotting on the vertical axis?
This data comes from a very careful and scientifically rigorous study and is in no way arbitrary at all.
+Bruno Oliveira "very careful and scientifically rigorous study"
Care to share the original data publication/source? I'd love to add that info to my presentation when I quote you.
I detect sarcasm in Bruno's comment, but I would be curious to hear his explanations for the ups and downs of the blue line.
+Rob Fisher
Indeed. Exactly ;)
Hence, my request that he share his research "methodology". For my request is absolutely serious... I intend to quote him and show this graph in an upcoming conference :)
No use... - as soon you make it official it will probably change completely because the geeks won't let you nail them down anyway. And forget about doing it in a strategic way to make them change to your favor, there too smart for that, too. (Hmm makes me think wether this is a quantum effect...)  +Roz Hussin 
+Roz Hussin So my assumption then would be, the behaviour of electrons in the double-slit-experiment is the most basic physical expression of a will to freedom. Thats why nobody likes to be categorized, its a principle woven in the fabric of our universe. This is probably the key to real AI if we only get it coded .... :D
Yep this is 100% accurate for me.
Unfortunately my productivity peeks collide with the times our dog had to go out :-(
Seems like there's an analogy to hard-drive defragmentation here... which the non-geeks referred to in the plots wouldn't understand.

(side note: it's ironic that this post was made on a site whose sole purpose is to interrupt in these ways...)
This is also true for small interruptions of a classical musician (violinist) during practice.  The recovery of the intense ability returning to the same place that you had prior to an   interruption is about 30 to 45 minutes.  So, are musicians geeks too?
The post midnight interval is so true.
Add a comment...