After 15 years of programming, how does one get out of it? [duplicate]

Question

Possible Duplicate:
I no longer want to be a developer

This might seem like an odd question, but I think I've just about had it with programming. I used to enjoy back when I was 11 years old (I'm 31 now), and I actually got to be really great at it at an early age. In high school, I had already knew c++, design patterns and all sorts of things and was building fairly sophisticated stuff.

Then web development became all the rage, and like a lot of people, I sort of got sucked into that - to the point where that's all anyone really wanted. To be honest, I've never liked it.

After learning so many technologies and languages year after year, I'm a little sick of relearning the same sorts of things that I knew how to do before but differently. I am sick of learning the new bugs, design errors and idiosyncrasies of the new technologies over and over again. Sometimes it seems like we are regressing rather than progressing.

The amount of languages you need to know just to get a web application up and running now is just disgusting. It's way more bloated then it should be.

Things have just gotten a lot more complex now too. While I appreciate a lot of the frameworks out today that try to make your life easier, it seems that debugging and knowing what's going on has become a lot harder. I've never come across more bugs in other people's code than I have in the last 1.5 years in my entire 15 years of programming. It is annoying, it sucks out a ton of my energy.

I am just not passionate about this anymore. Learning and working with the technologies for their own sake is just a means to an end - it's not fun. I actually don't care about any of it anymore.

Despite how simple things some things have gotten, it is amazing how trivial problems blow up into solutions that require 4 or 8 hours to fix... and these things have nothing to do with your actual application requirements - it's just fixing crap that other people got wrong.

We're also in a era where frameworks and libraries need to hype their tools and they need to prove to you how easy they are compared to things that have come before... but they almost always make you jump through a billion hoops to doing something complicated. By the time you figure out how to achieve the complex requirements in the new tool, you've lost a lot of time that was more-or-less equivalent to the time it would have taken in the old technology. So what was the point of learning the new technology in the first place? While the old technology required more code, it was more generic and flexible.

You could argue that learning the new quirks for these complex requirements build intellectual capital that can be used later, but by the time you need to utilize this knowledge a second time, there comes yet another new technology that makes this knowledge obsolete.

With websites basically needing to be super rich client applications now, these beasts have become extremely hard to test. No longer can you just write the bulk of your code in a single language, and getting amazingly good at Javascript seems like a monumental task all on its own. We are in the era of mass specialization now, and that doesn't interest me because any projects I want to work on, I have to do by myself.

How do I get out? I have decided that I'm just done with it all. I really want out. I have just invested so much time and energy into being a great software developer for most of my life, it seems sad that I'm basically going to throw it all away.

EDIT

After reading some of the comments, I think these are also problems.

1) Burnout. Regardless of how long I take a break, I have no interest in working on programming stuff when I need to start back again.

2) Not caring about writing "good" software anymore like I used to. You don't get rewarded for doing a job better than 99% of the programmers out there. Nobody cares if you do it well either. It's actually kind of amazing that skill and craftsmanship and care is not a value to most people in this industry.

3) Boredom. Writing mindless queries, business logic and pumping data to a view for so many years is just not interesting. After working on 1500-2000 database tables and the application logic that worked on them, I don't find any of this kind of stuff interesting or challenging.

4) Producing value. Nothing I work on really matters. Sure, it matters for the clients, but it doesn't really matter to me.

Answer 1

So quit... go back to school, get another job, just bum about for a while.

If you're in a position financially where you can afford to live on reduced income for a time you'll be able to try out a few things and see what floats your boat. You might just find you need a sabbatical to clear your head and refresh yourself.

It really sounds like you're fed up working for a company that continually switches in current buzzword technology.

I was in that sort of position a few years back where the company I was working for was making a huge shift away from an embedded application built mostly in C to a "cloud" application built in Ruby. Ruby is a great language and the company was good to work at, but the direction didn't enthuse me much. I saw another job in C development and jumped ship. Haven't looked back.

There is still a huge amount of work in real programming, particularly in embedded code. You should consider looking in the jobs section for programming jobs in technologies you're familiar with that aren't the flavour of the day. You might be quite surprised at the sort of work that's out there.

Oh, and find a non-programming related hobby that you can do instead of sitting in front of the computer when you get home.

And you need to lose the attitude you have - your comment:

"I'm a smart person - a lot smarter than the average developer."

May explain some of the disillusion you are feeling.

Answer 2

If this question is sincerely seeking an answer; study all that goes into a career change.

What I think this is more or less though is frustration. Frustration with your current environment. You are at the point that the frustration has rolled over into your career path and that can be toxic.

Take a look at what is really spawning the frustration.

I know you mentioned numerous things but learning can't be that bad can it? Fixing other peoples problems will exist in every other career you could possibly embark on. When you deal with other humans, you deal with their positives and negatives. Are you feeling left behind and instead of pushing forward bowing out feels like the easier path?

Identifiying the root cause of this frustration is critical. After the initial analysis you may find yourself at a better understanding on why you are frustrated and realize it may have absolutely nothing to do with your current career.

If you do however still find yourself at the point of needing a career change, look at the aforementioned link and jump in.

Answer 3

I don't really think the question is programming specific, but since I was in a similar boat about 7 years ago, here are my thoughts:

1. If you've got some savings, something on the order of a year's worth of living expenses, stop worrying and just try something new. I spent a year or so drawing up a business plan for something non-software related, and just went for it when I realized that my time was up, even though all my calculations showed me that the odds weren't in my favor. Go volunteer for a while, or start training or studying something completely new to you, or wander off to a remote spiritual pilgrimage, or start a business. What you do matters only to the extent that you can convince yourself it's worth a try.
2. Chances are your frustration has little to do with the technical issues you're dealing with now. You're probably actually a) bored b) frustrated with your current work environment or c) hoping the grass is greener on some mythical other side. That's fine. It doesn't really matter. Just find a new challenge and invest some emotional energy and time in that.
3. Realize it's not that hard to come back, so don't worry about what direction you end up trying out. I was pestered by recruiters for most of the two years I stepped away from software-related work, and when I started running low on money, I just took a short term gig that I wasn't emotionally invested in but was in a domain I knew well, and I was far better at it because I was no longer concerned about my career progression and I just focused on solving interesting problems. Your career crisis may be different than mine, but time away from it will do you good.

One of my friends hiked across the country for about a year after getting rid of most of his worldly possessions. He's only been looking for work for a week or two and has at least one offer already. I started a business on too little money and got the business to cash flow positive after a misstep or two, but realized there wasn't enough money in it without resources I didn't have. A more aggressive person than I would have sought VC or angel money, but I took a couple of contract gigs and got back on my feet, and realized I didn't dislike software all that much after all. Whether your next step is successful or not isn't important. Get your mind off your current frustrations for a while and more doors will open for you. You'll either be incredibly happy with your choice or you'll realize the grass isn't so green.

Answer 4

How do I get out? I have decided that I'm just done with it all. I really want out.

There's no problem getting out of programming. Just walk away. The field will survive without you, I promise.

The problem is getting into something else. Starting in a completely new line of work with no experience could prove challenging.

I have just invested so much time and energy into being a great software developer for most of my life, it seems sad that I'm basically going to throw it all away.

Do you want to get out, or don't you? From your rant, it sounds like you just don't enjoy building web applications. You do know that programming skills are useful for more than just building web applications, right?

Answer 5

The few times I've felt like that in the past have definitely been related to my specific working environment. I found that going to a big developer conference, learning about new stuff that was completely off my radar, and meeting people who are smarter than me, were a few things that gave a new lease of life to my waning motivation.

Oh, I changed company too :)

Now I'm working on something that I actually think is worthwhile - so even though the technology may not always be what I'd choose, I'm motivated because I'm actually producing something of real value (not just websites to make rich people richer)...

Answer 6

If you have a CS or engineering degree, consider going to law school and becoming an intellectual property attorney. You work on new technology in every case that comes across your table. You become an expert in some crazy intricate field while often glossing over the annoyances of the technology (e.g., IT admin, getting the project to build, etc.). Also, your "product" is your own written-word either as an opinion or persuasive argument, something that is often much more personal than a chunk of code within a huge project. (not to knock programming, I still love it).

You don't have to be a patent troll or sue/defend massive companies like Apple in their patent wars. You can help start-ups grow, work for public service organizations like the Software Freedom Law Center (SFLC), the Public Patent Foundation (PUBPAT), the Electronic Frontier Foundation (EFF) or many others. There is lots of great work to be done and it can be very rewarding.

It's not for everyone. The first year of law school is grueling, it costs lots of money, and in this economy job prospects are difficult (although those with engineering degrees have it easier). Something to consider though.

Answer 7

So don't throw it all away. Take a break for a while, and promise yourself you'll reassess in 1, 3, 5 years time. Try a change of scenery, it sounds like you aren't in a good place, so maybe looking for someplace where people share your passion for error free, less framework dependent code.

If you really are going to get rid of this piece of your life completely, while it is fresh in your mind, make a list of your skills and try to find skills in other fields that match up (e.g., "attention to detail, I could use that as an accountant or an editor", etc. That way, once you are looking into other things, you'll have a ready list to use in cover letters, interviews, etc.

Answer 8

You have to ask yourself: are you tired of the corporate/office life, or do you want to stick with that and change direction?

I have seen a few people get tired of programming and change over into team management, project management and business analyst type positions. These positions all deal with programmers, but involve no programming work themselves, and can be paid just as much or more than programming.

Moving into a pure management role will turn things upside down for you, as your focus will be on considerably different things. From the sound of it though soon enough you will get tired of that as well, because as you learn how a business operates you will find things there that you don't like, and you appear to be the sort of person who wants to do things a certain way. If that is you, then the only way to break out of that rut is to work for yourself, run your own company - then you can run it any way you like, and create product any way you like (the market will determine if you are right with your approach).

Answer 9

You might want to think about a sideways career change into something like QA or Technical Writing.

For what it's worth, I also burned out with programming and am currently working on getting into Testing, with the goal of potentially getting more into the QA and possibly BA side of things. In my case, the frustration with programming was possibly a bit different to yours: it was mainly to do with my aptitude and patience being far better for analysing things (from the "outside", from a step or two back) than synthesising and building things at a very low level. But that's all by the by.

Once you identify exactly what bothers you about programming in very fine detail, it really pays to look at related fields which could use someone with a strong development background. You might be able to find your niche or a new career in one of these.

The reason why programmers often burn out without seeing these alternatives, at least in my experience - is that we tend to be a very one-track-mind bunch in the way we look at our careers. We partly even have to be, due to the sheer volume and fast evolution pace of the skills and knowledge we have to acquire. We simply don't have the spare energy and time to step back enough to see how our skills and experience might be transferable to other semi-related fields, which we might actually enjoy more and/or be better suited for. We just work ourselves into a burnout instead.