The creative programmer

"Why Writing is Harder than Programming" is Paul Graham's latest post. Pauls premise is that a programming project can have a definable measure of success and that reaching that success is ultimately achievable (given enough talent and time). With writing, however, "You don't have the same total control over the medium".

Paul Graham is one of my favourite IT writers. Not that he's the best or the most insightful (although he is floating near the top) but because he combines programming with other creative pursuits. That's the way I think it should be. He also invests in the education of others and the support of their ideas.

Probably my favourite programmer (and also a good friend) Lars Pind is similar. He likes to write. He plays at least one musical instrument on a regular basis. He is a prolific photographer. He's never afraid to debate his approach to programming or life. He programs fast and furious, but with a degree of elegance and insight that, I believe, couldn't come without all of the above.

It's qualities like these that I always look for when interviewing potential employees (or employers), but rarely find.

What do you think? Can you be a good programmer without being creative? Can someone be truly creative and maintain/nurture that creativity without a variety of creative outputs?

Another question to a certain section of the developer audience: How do you manage the peculiar balance of creativity; logic; and a perfectionistic need for symmetry and alignment that comes with programming excellence?

PS: This wasn't supposed to be a Paul Graham/Lars Pind love fest, but so be it!

Footnote: On a totally unrelated use of creativity, a study by Indiana Universtiy shows that (on some selected topics), The Daily Show is as substantive as regular news broadcasts!