Anyone else deal with burnout at a corporate gig?

This is natural for an ambitious person at your level.<p>You're also doing the right thing by staying where you are until you find a compelling reason to walk away. The side projects are good and will get your name out there. Go do some tech meetups if you get a chance. Don't underestimate the value of an employer subsidized launch schedule.<p>You will know when the time is right.

While side projects are good you are going to need more to stave off burn out, consider taking a painting class or learning an instrument. You need something external to the computer to expand your horizons, burn out is a combination of issues, but one of the big issues is that as a group developers like to learn and at a certain point we peek in a language their is just not that much to learn that is interesting, when this happens that need to learn has to be focused on other outlets.

Dealt with this myself. The side projects only go so far to help you deal with this. I also found myself so into the side projects that I would often find myself distracted from my actual job. I'm sure you plan on sticking with your career field for many years to come. If you absolutely need the money/stability, stick it out (at least for a while). But if you are ready &#38; willing to take some chances, ask yourself first if this corporate job is teaching you skills you can continue to use, and move up/forward, for the rest of your career or are you a 'worker drone'. A corporate job can teach you boatloads about how to run stable apps at scale, but usually stifle innovation &#38; creativity. Working at a startup or smaller shop will usually get you much more exciting and creative projects and challenges, however the tradeoff is that you usually have to accept much more responsibility for what you build. You won't always have a rigorous test suite, QA department, and week-long rollout cycles. I can tell you though, from somebody who came from the exact same place, working at a startup is 20x more rewarding and fulfilling.

Corporate burn out is inevitable. Having done this for the last 14 years or so, I see it and experience it all the time.<p>I agree with most of the posts here so far, side projects only go so far to help you deal with it, but the future is pretty grim too. If you stick at this, and then get settled, there's actually very little to push you off the treadmill.<p>Corporate IT is mind-numbingly dull. You will never be a big fish, no matter what your title says you are, and you'll always have the feeling you missed the boat, because coprate IT is always years behind the curve. I speak from experience!<p>If I had my time again, I'd do everything I could to get into a tech start-up, or do one myself. You'll learn all you need along the way, and more. Stuff that corporate meetings and politically messy projects will never teach you.<p>If you have family that can support you, just go for it.

Trust your instincts on this one, especially before you begin acquiring wife/house/kids, etc., as this will chain you to the biggest paycheck. I have worked in several large corporations and in general they stifle creativity and are so mired in politics that it is nigh impossible to accomplish anything of substance. The key here is that you highlighted practicing your craft as creating and being rewarding. For most corporate devs, it is only a job and they do belong and thrive there. For you and others like you, find a smaller place (or a startup that you can turn into a bigger place) that needs and recognizes the fine art that you practice.

Yep. Two programmers enter, one programmer leaves.

The worst corporate environments bring you -- persistently; repeatedly; seemingly as a matter of policy, no matter what the "propaganda" of internal communications -- to doubt yourself.<p>When that's the case, get the h-ll out!<p>When it's not that bad, evaluation the pro's and con's and make sure you have a plan forward -- <i>your</i> plan forward, not theirs.<p>It may -- perhaps even likely won't -- work out just the way you plan. But, you'll be making progress and trying to get somewhere.<p>If you don't have a lot of personal responsibilities to others (e.g. family) and want to learn more, a different environment is very likely a better bet.<p>Sometimes one can end up on a... "blessed" -- or ignored -- team in a larger corporation, where corresponding autonomy combined with a good manager leads to a good, productive, educational experience.<p>(In my experience, this is when the team members are so valuable and rare that Management has realized/decide that they can't afford to do without them, and maybe is even respectful of or afraid of disrupting the environment, balance, or "magic" that makes the team work.)<p>But that seems to be somewhat the exception. And from cycle to cycle, year to year, you don't know when a critical person is going to move on, or Management is going to "notice you all" and make things crap.