What I do to fight the boredom is build my own framework.
Excellent idea. I have done this myself several times.
My dilemma: At what point do you realize that your code is so cool that you don't want to develop it on someone else's machine (and dime)? I often find myself saying, "This is WAY more than they're paying for and will be worthless to me since they will own it."
To the parent: This where I've been. I've built many of my own tools and frameworks. Problem is, they're still related to the space that I no longer enjoy being employed in. It was fun work, with plenty of great challenges, and proved to be a great strategy for securing most of my sanity. Elevate anything to a "higher purpose" and you'll find some extra motivation to get the job done.
To edw519: This where I'm going (in addition to looking for another line of work I might enjoy more). I've been making my own tools for about three years. I guess that's my "breaking point". I'm using them personally, but I don't want to be at shops without some kickass tools and practices already in place. I like my tools, but working at a place without any useful abstractions is no fun. In the meantime, I'm trying to make the best use of my tools and talents on my own dime, for my company (http://greaterscope.com). There I can solve the problems I want to solve, without restrictions (until I get customers). Hopefully it'll be a much better ride and I won't post another similar thing in another five years.
Excellent idea. I have done this myself several times.
My dilemma: At what point do you realize that your code is so cool that you don't want to develop it on someone else's machine (and dime)? I often find myself saying, "This is WAY more than they're paying for and will be worthless to me since they will own it."