Ask HN: How to deal with losing interest in your passion?
I have four and half years of professional programming experience. Two years ago, I was very passionate, always learning, coding etc.,<p>Slowly over the the past couple of years I have lost interest in everything I suppose. i am not speaking philosophy here, but I am feeling tired of everything.<p>I am just 25. I'm too young to say such things. Anyone else have been through this before and "came back with a bang" ?
71 comments
[ 3.3 ms ] story [ 131 ms ] threadMost likely my dilemma is that I seem not to be able to decide where to specialize and programming alone has become quite boring. I kinda want to do everything and can not decide which is the most fun of games, web, mobile, desktop or security.
This sounds familiar, I experience the same thing whenever I sit down to do anything (not just coding stuff) that's supposed to be 'for fun' only, and has no clear utility value. There's simply too many things I want to do, which paradoxically has a paralyzing effect on me. There's at least 20 things I still want to develop, at least 20 books I still want to read, 20 video games I'd like to finish, 20 things I want to improve around the house, I have a car disassembled to pieces I still want to put back together, I want to learn to play the guitar, I want to pick up sports again (tennis, so I'd have to join a club), I want to travel and spend weekends outdoors hiking and such, etc.
The net result is that every time I sit down to do something, in a strange way I feel guilty not doing any of the other stuff that's in the back of my head. This in turn distracts me from what I was planning to do. In the end, nothing gets done.
One thing that has helped me a little is to try and do one thing of each activity at a time. In other words: work on only one code project at a time, not multiple. Read one book at a time, not multiple. Play one video game completely through, or drop it completely if it gets boring. Pick one thing you want to improve around the house and finish it completely before starting something new.
This works for some things, but not all. Travelling more or picking up sports requires a different kind of discipline, but I'm not sure how to get myself to actually get moving. It's a character weakness I think.
Currently I am trying to complete one small project without putting it aside. Though I am still thinking other projects, but luckily at the moment those projects in my head require cash which I don't have, so I can't drop this and start the next.
EDIT: Recently I was attending a startup meeting and there was this video, where one developer said Sleeping and eating are overrated. What a load of crap - following this advice is the best way to burn out. We are not robots.
Snowboarding has been my passion for about 10 years. I snowboard 50+ days a year, I moved out to Colorado for a time just to snowboard absolutely as much as possible. I race, I go into the park a lot, I jump off cliffs, I go into the backcountry, I worked at a ski shop, I read all the magazines, buy the DVDs, and I watch the weather forecast incessantly.
But I'm burnt out on it. I moved back to the east coast, the mountains and weather aren't as good, and I'm totally jaded. If its not fresh snow, steep trails, perfect weather I feel like I'm wasting time and money. Unless I live at the mountain, I can't get any better than I am now (whereas before I enjoyed the challenge of getting up the learning curve). So I just decided to stop.
I picked up surfing instead. I'm terrible at it, but the challenge is thrilling. Now I can enjoy the learning curve again and I don't need 'perfect' conditions. It's fun just to get out there and do something.
And I'm sure when I do go back to snowboarding in a few years, it will be far more interesting.
So for you, I would say make programming your job, and something else your passion/hobby. Take a couple years off from programming outside of work, and come back to it with renewed purpose.
I had the same thing when I was 25. I ended up quitting my job and buying a one-way ticket to Europe. I didn't think I would ever write code again. I spent about three months backpacking Europe, then came back and spent a few more hanging around and doing odd jobs around town. Eventually, I started code in my free time again, and about a year later, came back into the profession refreshed.
Now I know what I need to do to prevent burnout again, and it's primarily that I keep other hobbies, and I have friends that aren't work-related. It lets me get away when I need to and still stay interested in what I do the rest of the time.
But that's more maintenance, sometimes you need to shotgun into that stage by cutting out everything for a lengthened period of time. If you really are a hacker at heart, and it sounds like you are, you'll start writing code again soon enough, and you'll know you're back.
You'll also have stories and other life experiences as well, which make you a better, more rounded person.
After all that I found I missed programming, and realized what things I didn't like about my career choice, such as long meetings, boring projects and so on. This helped me direct my programming career back to what I enjoyed and has made me much happier and more productive.
So, get out there and do something different! You've got your education and experience now and there will always be a job somewhere for you.
As for running my own business, I can point to all the skills gained during that experience as benefits to the company as well. Leadership, discipline, time management, working under pressure and so on.
The sort of companies that wouldn't like my past experience are exactly the sort I would never want to work for, so it works as a nice filter for me too! :)
I also know exactly the things I feel before I get burnt out, so when I feel that happening, I can take a short 2-3 week vacation and don't need to do something drastic again like taking a year off.
Overall, it just teaches you about yourself and how to be more efficient at whatever it is you want and need to do.
Sorry for asking the obvious. But from where did you get the money to do all that?
One benefit of taking this kind of time off is that it lets you know what you truly love. After a few months of kicking around, reading books in parks, seeing sites and meeting some cool folks, I found myself reading web tech articles. That was an eye opener to me--"hey, I really like this career path!"
In my case, one of the side jobs was a small business being run on eBay, so I had that listed. I also said in interviews that I wanted to take a year off to see the world. Once I got the first job after the break, it was never a concern anymore.
Since then, between jobs I've taken a couple months off, and I've never found it to be a problem. Especially when you say, I was burnt out and I needed to refresh myself before I came back to work. Otherwise, I just wouldn't be as productive. Potential managers definitely appreciate that you can take care of yourself.
(Or rather, the kinds of companies you want to work for appreciate that you can take care of yourself to recognize and prevent burnout.)
Specifically:
- Don't rationalize. - Don't be overly emotional about it. - Demonstrate your technical skills
I'd also recommend learning to do something complicated in your personal life, like flying, or diving, or fixing cars. Complexity doesn't exist just in software; it's all around us. Embrace it in your personal life and it will balance what's in your professional life.
For me, it's about composing and IT. When I studied musicology, I couldn't compose anymore and just wasn't creative. Then I changed to studying physics and soon burned my interest in the same way. Both of them definitely came back, and by now, I try to keep my interests more balanced!
The thing to remember is that it's ok to have changes in interests. If our interests never changed we wouldn't make progress.
It sounds like you've got to a point where you are super comfortable with what you know.
Personally after I finished my CS degree I took a big break (2 years) from technology, building things and fixing things. Actually I felt like I hated all of it and that worried me a lot. I wanted to let all the learning settle & see what interest in the field I was left with - if at all.
After two years I made the decison to go into the applications support side of things as I realised I still loved the people part of it. Being the bridge between customers & developers, fixing things & I'm still doing that now. Even my interest in development has come back and I'm building things in my spare time again.
Also my partner & I have transitioned from taking photographs as a hobby, to professionally. I find that each time we get a photography job there's a little 2 month cycle where it goes from being great fun to just being 'done' with it. At that point we take fewer personal photos.
After a little time, the interest comes back we start photographing for fun again and then we get another job and it goes full circle.
I think you can only force creativity so long before it becomes work with obligations etc - that's when the interest fades.
Me, I build plastic robot models. It's no brain power at all, just precise physical motions. It's mindless and enjoyable, and at the end of the day you have something to show for it.
There's a lot of posts here saying take a break, but you really have to make sure that you are truly taking a break, and not just substituting programming with something else that uses the same parts of your brain.
edit: Here's one of the first models I built. Unpainted just to see what it looks like. http://www.flickr.com/photos/37553996@N07/sets/7215762298535...
As the parent notes, finding a hobby that's unrelated is useful, but not only as a diversion ... you can gain that sense of accomplishment in the preparation of a good meal or in completing a weekend woodworking project.
It's much easier to show your friends and family the mission-oak picture frame you built than some obscure bit of software. It needs no explanation and you'll be gratified (hopefully) by their response. Explain a low-level library you built to these same people and their eyes will glaze over while they hope you talk about something regular humans deem important.
For me, I'm a fairly serious photographer on the side, and I spend a lot of time studying visual arts of all varieties - going to galleries, museums, talks and the such. It works a completely separate part of my brain that doesn't get a lot of exercise during the day.
The next question is: are you healthy? Are you getting enough exercise, sunlight - are you eating well? There are tremendous psychological impacts on what you do when you don't physically feel at your best.
If I told people to associate me with one word (a subject), pretty much anyone who knows me would say the same word. I've spent over 10 years learning about it but I've become jaded because just like any subject, you can study about it and you can do it. It's the doing it that has made me jaded and that has effected my will to study it as well.
My best theory is that I simply never defined it for what it is and has been: a goal. In effect, I summited and now I just feel like I'm at the top looking at the view. The solution, it seems, will inevitably be to search out another mountain to summit.
I fixed it with a change of direction. I'd been tackling a bunch of stuff that my heart wasn't in, figured out what i did still like (turns out i wasnt doing any of it day to day), engineered a change of circumstances at work and popped out the other end feeling happy again.
End to end about 4 months. Did involve a fair amount of persuasion - what i wanted to do didn't fit with the organisation at the time.
1) In my 20s, I worked all the time. Didn't live a very balanced life, this lead to burnout, especially if you're working in a startup environment where you think you'll retire at 30.
2) I quit engineering twice (but after 6+ months off, new developments in technology that stimulated my imagination eventually brought me back)
3) I've learned to manage not working the burn-out dream, that likely in the long run, your 80 hours weeks aren't going to pay out. It's proven to me that there's plenty of successful people and companies who work realistic hours.
4) Hobbies. I prefer those where I get excercise (like cylcing). Gives me time to clear my mind and keep my body fit and invigorated. I also enjoy gourmet cooking.
5) Managing workload, prioritizing things that are important and recognizing things that you think are work but really procrastinating.
6) Learn other professional skills than typing text into your favorite editor/ide. Speaking at conferences/local user groups, managing project budget, managing teams, managing bigger teams. Doing these other things makes you appreciate the few hours of coding you have left in the week.
Alternatively, it can also be cathartic to do some volunteer work. It certainly would put a smile on someone's face and perhaps provide some different perspective on life.
Not only did I regain my passion for programming, but I actually like to believe that the skills I learned there made me a better programmer to boot.
TLDR; You're young - Try something different for a while.
This helped me immensely, because I accelerated in my career and knowledge really quickly. But then, after about 10 years, I had gained about 50 lbs, and suffered through some personal issues. I was completely and utterly burnt out. I stopped being curious about technology, and couldn't bring myself to even turn on a computer after work, except to play games or online poker. This period lasted for about 5 years.
What rekindled everything for me was that I found something new to be passionate about, namely algorithmic trading. The entire topic absolutely fascinated me and continues to fascinate me, and that's where I regained my passion. I've been spending a lot of time on this topic over the last few years.
My advice to you is just take a break. You're probably burnt out. Give it some time, and you'll probably go back to doing it, or you'll find something new to be passionate about.
I love it, regardless of my level of success in it. My friend is a day trader, and he gave me one of his setups for trading. I didn't believe him, so I downloaded the data, wrote the code to simulate it across a few years, and then all of a sudden, this became a computer problem that I could try to solve through programming. I've been hooked ever since. There are a lot of much smarter people doing a lot more successful ventures than me, but for a hobby, I really do love it, and it completely reinvigorated my interests in programming.
It can be as easy as "buy at market open, sell at market close". Or it could be much more complicated, for example, the stuff that quants do. I'm much closer to the former than the latter. You can definitely pay for things like a real-time data feed (less than $100/month) and trade real time, or you can choose to expand your time frame and do swing-trades with daily data which you could probably get from Yahoo.
And believe me, it's very, very hard, to the point where I almost don't think it's possible. But I still love it.
http://www.amazon.com/Quantitative-Trading-Build-Algorithmic...
and that authors blog:
http://epchan.blogspot.ie/
When I was a kid, I loved coding. From the ages of 6-19 I didn't really want to do anything as much as hack on cool projects. The only thing that would make my life perfect — obviously — would be to get paid to code, so that I could do it all of the time and pay bills, too. I'd be the luckiest guy on earth.
So, why was I horribly sad (not depressed, btw - that's a disease which you don't bring upon yourself) as a professional developer at 25? I used to be so engaged, but then I could hardly concentrate on what I was doing, and it was very difficult to get started each day.
One day it hit me like a lightning bolt: the reason you do something impacts whether you can enjoy doing it or not. That's why being a prostitute is not generally considered the best job ever; I found that coding other people's ideas was like not getting to choose who, when or how to have sex.
For me, the solution was to gradually move out of coding day-to-day into a more pure consulting role while reintroducing lots of fun personal coding projects, which are mostly just as fun as I remembered from when I was a teenager. 8-9 years later, I simply don't take on paid coding projects.
As a corollary, I'm really into film photography and I flat out refuse to get paid to shoot, because I have no interest in difficult brides or screaming babies. I figure that I deserve a passion that isn't corrupted by my need to pay a mortgage. It's like an endless chain of discoveries and happy accidents that brings me mental calm and occasionally professional (consulting) opportunity.
I recently went to the Luminance photography conference in NYC, and during breaks I met as many people as I could. Every working photographer seemed stoic and anxious, and all of the aspiring photographers verbally differentiated between their "arty" work and the stuff they had to shoot in order to pay the bills. Not one of them thought that there was any hope of them having fans that would appreciate them the way a painter would. [Granted, painters often have patrons... but I digress.] I found it all quite sad.
Needless to say, I suggested that they all learn to code as a career so that they could take photos out of love. I said that if they needed to pay their bills with their camera, they would develop an increasingly abusive relationship with photography.
Don't worry about "coming back with a bang". You only live once, so stop hitting yourself.
From time to time, I say that 'the worst thing I've done was to turn a hobby into work'.
It it not strictly true, there are worse things I could be doing instead. But I have lost some of the that initial spark.
I started learning to program in the 3rd grade. From there, it was a hobby. Come time for college, I decide I don't want to do that a job because I don't want to ruin my hobby.
Fast forward 10 years, and I finally decide I need a career, not a job. I look at my skills and decide that programming is the only one worth doing.
Turns out, I love programming more than ever now! It was absolutely a mistake for me to try to avoid it. I'm better at it than ever, and I can do more things than ever.
I still, sometimes, do it as a hobby. So in that respect, yes, it kind of killed my hobby. But I have that fun at work now, and I get to do other hobbies at home. It's a positive thing all around.
The key is that my job isn't the soul-sucking variety. I work in a positive atmosphere and (mostly) on projects that I enjoy. I'm valued, and my employers prove it by paying me what I'm worth as well as having great benefits.
One thing I find undermining about HN is the focus on finding a market, getting users, meeting their needs. That's great for getting rich. For personal fulfilment, eagerness and passion, it's better to create something that you value, to improve or fix something that you feel is wrong, in your bones, that annoys you, drives you up the wall. You'll get cool ideas (and frustrations) just by interacting in the world, doing any new activity. And disregard whether anybody shares your opinion or not. (There likely are people with the same itch, since you have it, but disregard that). This is liberating, because you regain captaincy of your soul. If people follow you, it's because they share your vision, not because you worked at convincing them to follow you (which would mean you are controlled by their opinions, instead of your opinion of what is valuable). If people don't follow, you've still done something you value. (It's helpful to pick doable goals, or to divide your project up into doable goals, so you get the feedback/satisfaction of seeing your idea become real.)
But take this with a grain of salt. I've been having trouble with passion too and though I'm starting to get glimmers of it back through this approach, I can't yet claim I have "come back with a bang".
PS: Just in case you are literally "feeling tired of everything.", you might want to check in on basic health stuff - food/sleep/exercise - get a check-up from a doctor for any illness, and also see if you are suffering from depression. But I've assumed you just meant tired of everything, in programming.
1. Autonomy. The feeling of freedom and control over your work.
2. Mastery. The feeling that you're good at what you do and getting better.
3. Relatedness. The feeling that you're working with people you like.
When you're doing something on the side, you almost always have all of the above. When you start a job doing something, you almost always lose all of the above.
The real question is how to gain Autonomy, Mastery, and Relatedness at a job. It's not impossible by any means. But it does frame the question differently, since those 3 traits are often more critical to enjoying your day-to-day life than exactly which field you work in.
For a very good book that goes into much more detail, see So Good They Can't Ignore You by Cal Newport.
(I went through a very similar experience with losing interest in a field I loved because I "had to" do it. Working on gaining control over my career completely rekindled my love for the subject, stronger than ever).
There are other angles that you should consider. Is it only affecting your job, or are you apathetic on other things too ? If it is the latter (specially since you said 'everything'), it could indicate depression.
In my particular case, a mild form of depression always sets in whenever I am sleep deprived. This can go on for months if left unchecked. Go out, have some fun, sleep a lot and see if it helps. Have your health checked (physical and mental).
If everything checks out, you might just need a change of scenery. Another city, another job, a slightly different area, etc.
Don't set yourself up for a miserable life. Become a well rounded person. Try something else and see if it clicks for a while.