Most Obvious Yet Ignored Concept About Programmer's Concentration

Inflammatory stuff by someone who seems to have never dealt with burn-out near the end of a project, or the fact that sometimes work is work, and you just have to push through it to get back to the things you find exciting.

His comments are provably false. There are countless scientific studies showing the benefits of various strategies for increasing productivity as well as increasing your enjoyment of your work. (e.g. how to make masturbation feel better, how to make programming more addictive, how to enjoy yourself while doing the dishes, etc etc)

He even suggests time-boxing, a very popular strategy for countering procrastination.

Suffice to say, he is yet another unqualified non-expert giving opinions on stuff he doesn't know anything about.

This is just wrong. Sometimes you run into a knotty problem that requires you to hold a lot of things in your head while you try to fit them together. A conversation in the next cubicle can prevent that from happening.

For those who like to have music playing while they work, I've found that albums can be a nice way to pace the work day, and to account for time.

Open up my editor, start an album that fits in with my current mood so it will service its purpose of covering up outside noise but will not distract me, and start hacking away.

When the album ends, I get to a good pause point, and take a break to plan my next move, and pick the next album. Good time for a stretch, or a snack, or a check of HN. Then start the next album and back to work.

This naturally breaks my day up into the kind of concentrate/break cycles that many recommend. At the end of the day, if I need to account for my time, It's easy to check iTunes and see how long each album was, and therefore how much time I spent on that phase of my coding.