Great to hear this perspective. Like Sergei says, there are structured and unstructured aspects to programming. It's important not to neglect either side. The custom software consulting company I'm working at here in Utah right now (collabratus.com) has this great practice of requiring clients to go through a 'Blueprint' phase before the beginning of development. This puts innovation and the creative process *first* and sets aside time to focus on the innovations and the design that will drive the project. I think programmers need to be given the message that both are critical.

Personally, when I have definite and unstructured time set aside for creativity that is fully recognized as profitable for the company then I perform better and I'm more innovative. It also makes the structured part that Sergei talks about more enjoyable.