I don't think so. I can only speak for myself and some of what I've observed in my colleagues, of course. From what I've seen, you can only work on one thing s

I don't think so. I can only speak for myself and some of what I've observed in my colleagues, of course. From what I've seen, you can only work on one thing so much before you grow to resent it. You need to take time off from it, even if that time is working on another software project. Companies like Google have tried to emulate this effect with their "20% time" initiative, but from what I've heard it doesn't really work, since people still consider it to be part of their main body of work. Some of my best revelations for solving problems at work have come from entirely unrelated projects. As someone who does game development as a hobby on the side, I've actually discovered solutions to major enterprise software problems while working on a random indie game. It's important to let yourself do this.