You can never be great at whatever you do if you aren't passionate about it, and put in the necessary hours. This article is pretty dumb.
There are also a lot of interesting meaningful problems that desperately need to be solved by creative, capable people, and if your job is to work on one of those, then great, but for many programmers, those kinds of problems are the ones we work on on our own time, if we're so inclined. I think it's strange that the article didn't make a distinction between code-for-work and code-for-fun.