I'm not saying that my periods of reduced productivity are completely gone, but they seem to be shorter and less severe.
I put a lot of the productiveness down to other factors at work. I'll see if I feel more productive next time she is at a conference and I get the chance to sleep more.
* Not being hydrated enough. Seriously, its a big problem - I don't pay enough attention to how much I'm drinking every day. A single cup of coffee in the morning, and maybe one after lunch does not a properly hydrated body make.
* Drinking too much coffee. Its cool to have an Italian espresso machine in the office and everything, but man does that stuff wire me up. I've had days where I'm getting a refresher every hour - those bumps are not productive. Goodbye next-2-days productivity, after a day like that... I've learned to treat coffee as a recreational drug, and only do it when I'm not at work. Helps immensely.
* Fights/arguments/stress: from anyone. Sure, its important to have 'normal' human interaction, but rude people suck. Discourteous people suck. They suck all motivation to be productive - even worse when they're a cubicle neighbor or other work associate. Manners in the workplace are important: they simply make you more productive. I wish more people minded their manners.
* Unexplainable terminology. Look, if I have to wade through hours of documentation-reading or grep'ing or what have you, just to discover your newly invented acronym actually means what last years fad was, then its a waste of time. I'm looking at you, new-language-fad guys. Reinventing technology is one thing. Reinventing terminology is another thing entirely, and frankly I'm sick of all the kids (GOML!) coming up with new-fangled sparkly words just because they didn't take the time to learn the old-fangled, perfectly workable, phrases for the same darn thing.
.. just to add my 2c to the flow ..
Look in to L-Theanine (pills) to use in combination with the caffeine at times, tends to balance out the effects and for some people it can help a lot.
And the other 2 points I agree on completely.
This line got me thinking it would be cool with an app where you can ask this kind of things, and the message will only be announced when the user is unlikely to be busy. (Triggered by events such as the phone going from stationary to being moved.) Anybody knows if such an app exists?
Check the phone when you take a break, like getting a coffe, a glass of water or going to the bathroom.
I've seen suggestions for good noise cancelling headphones but I don't feel very comfortable wearing headphones for long periods of time.
Here is my shameless plug from an article I wrote - http://brajeshwar.com/2014/missing-step-productivity-activit...
A good part of programming is design, and design can't be measured by lines of code per day or anything like that. I think we all need to come to grips with that. Some days we code; some days we crumple paper.
I suppose it is because the in house database I have been building and maintaining is used more heavily and as such I am a source of knowledge for a lot of stuff that goes on in the organisation as a result. I am personally less productive, but the organisation is more productive. Now if only I could persuade the users to read the error messages and think for a minute ("there is no sample in the database with the name blah" ), rather than come straight to me and ask me to fix it, then we would all be a lot more efficient.
Great list! Agree with almost all of them!
The noise and the visual distractions are too much for me.
Noise cancelling headphones are a must for me at this point. I was a bit more productive even without them on the other side. Extrapolating, I wager I'd be even more productive in a proper office.
Even within programming, the context can make a big difference. I can fix most small bugs in minutes on my current database, yet I never get the chance to focus on anything that involves more than a couple of hours of coding (mainly due to fixing the stupid errors we are getting from not implementing a proper data import solution. Catch 22)