Well.. this assumes that coding (all coding?) is a burden.. I agree with the article in that coding _for_ work, outside of normal work hours, isn't something to strive for. I did that a lot when I was young, but that was not only when it was necessary due to the strained time schedules we had then, it was also because I literally hungered for it. I needed to. So I would go back to work after dinner and hack away to figure out how the OS worked, deep inside, for example. Writing or modifying device drivers, writing tools that extended the OS functionality, that kind of things. Back when things were new.

These days I don't, as a rule, code for work outside of work hours. But I need to code in my spare time. That's when I can do things that really interest me, side projects where I can enter the 'flow', something I nearly never can do at work anymore. I have to go into flow mode now and then to keep up my ability for concentrating on problems (and yes that's necessary to keep up my work performance too). A few years back the constant interrupts at work degraded my performance so much that I spent my three week holiday in various cafeterias, with a laptop and documentation, and worked all day on my hobby project, finally re-learning to enter the flow again. As in "I looked up, and five hours had passed". Myself, laptop computer, documentation, coffee, food available. Happiness.