Slashdot Mirror
How Do I Get Back a Passion For Programming?
bigsexyjoe writes "I am a somewhat experienced software developer who is pretty much an office drone. I used to enjoy writing code. I even enjoyed writing routine code before it became routine. But now I just come in day in and day out. I work for manipulative jerks. I don't care about the product I create. I don't enjoy coding anymore. I'm not great at interviewing. I don't have an impressive resume. I stick in more advanced stuff into my code when I can, but that is always on the sly. So my question is how do I get back the enjoyment I used to have writing code?"
How about getting out of your comfort zone. Get your resume up to date. Have people review it for readability. Start looking for a new job. You may not enjoy your current employer, but find one that peaks your interest and the joy of coding will return. Also, it helps if the projects have an overall goal in mind that you agree with. For some that may be the Defence industry, others may prefer coding for the Medical industry. Industries that have a meaningful goal will help you to achieve that missing passion.
Some days I get the sinking feeling Orwell was an optimist.
I can't "give" you passion. I'm not Martin Luther King Jr. and this isn't about Human Rights. Passion comes from within and if it's not there, I can't trigger you to release it.
If all it required for passion was to saunter up to a counter and say "One passion, please" then we'd all be theoretical physicists musing over our all night analysis of LHC data whilst having tea with Stephen Hawking right now.
Sorry to be so crass about it but all I can do is tell you what got the ball rolling inside of me to make computers do exactly what I bid them to and how that makes me feel at the end of the day. To tell you to go home and read Edgar Allan Poe's The Gold-Bug and then implement a Hidden Markov Model that learns on Bach Chorales in LISP is unlikely to do you any good. Me, on the other hand, that shit turned me from a hay bailing idiot farmhand into a programmer.
My work here is dung.
The Man is paying you to write this routine code because it's mind numbing, soul-sucking work that nobody would ever do of their free will. If the problem you were solving was fun, there's be an open source project that was solving it.
The solution I had to use was writing my own software to solve problems I found interesting. That also let me test out new techniques and tools that I couldn't do at the day job. After all, there are only so many ways to CReate, Update and Delete records from a monolithic database.
Easy Online Role Playing Campaign Management
Start your own projects on the side. Or if you don't have any ideas, join an open source project. Unless you're amazingly good at programming you'll probably learn something either way, and, at least for me, that's what makes it fun.
But like anyone else I can only really give you suggestions that would work for me or I know worked for someone else. you have to really discover it again on your own.
All the world's a CPU, and all the men and women merely AI agents
Try taking on a personal project, or get involved in an existing open source project that you find interesting.
Do some "creative coding" with p5 in Java ( http://processing.org/ ) or OpenFrameworks in C/C++ ( http://www.openframeworks.cc/ ).
Make some art, it's rewarding.
I found that programming for a living does tend to take away the passion I used to have for it. To compensate, I tend to code for myself on my off time. I'd like to get into an open source project one of these days, but for now, I just write my own programs and enjoy the process.
You could get into an open source project, see if that might re-kindle your passion for programming. Make sure you check you company policy for code you write after work, you wouldn't want to run afoul of that.
No matter where you go... there you are.
Quit your job. You'll find motivation. Maybe not right away, but definitely when money gets tight.
Just don't pass your time with WOW. You'll starve to death.
Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
Start a project on your own that is fun.
That is a really great idea.. probably one of the few things will get him to love programming again. He puts more advanced code into projects for his employer for no reason (not a good idea IMO), when all that effort should be put into his own project.
BUT he needs to check his employment contract first. Very common for the employer to say they own everything you create, even if it's not on company time. And if he works for jerks, I wouldn't assume they won't take the project from him when he leaves if it has any value at all.
Do like I did: retrain and start a new career. I used to be an overworked software project manager with the love of coding drained out of me, and now I'm a happy gunsmith.
It's never too late to go back to school. No sense in living a life you don't like, you only have one life and you need to enjoy it to the fullest.
"A door is what a dog is perpetually on the wrong side of" - Ogden Nash
You don't have to love your job. It's work. You get paid to do it. I used to like my job a lot, but it paid absolute crap and I was working over 60 hours a week. So, I left it. I liked my new job less but was getting paid a lot more to do it. I was working only a 40 hour week. So, I used that extra time and money to enjoy my LIFE outside of work. Passion for programming? I now have the time and resources to foster that creative need on my own time and more importantly on my own terms.
I was in the same situation, bored out of my mind working on a product that *nobody* cares about, let alone me; The product was mature, so there was very little development. Coming in to work was getting to be a major drag. I was starting to consider changing careers entirely, thinking I was a burn-out.
Fortunately, a new project popped up at work, and I was lucky enough to be on it, and it has definitely improved everything. I am having fun cranking out code just like "the good old days", so the burn-out thing was really just boredom, and knowing that the work I was doing was never going to affect, well, pretty much anyone.
So perhaps the question is, "How do I get onto a new project?"
Maybe it won't happen with your "manipulative jerks".
Maybe you have to come up with something completely new.
Are there other devs there too? Or other people who like to come up with product ideas?
I think I was pretty lucky. You may have to make your own luck here.
That's because programmers have no people skills. They are not good at dealing with people. So they have to hire people with people skills to talk to the customer so the software engineers don't have to. What in the hell is wrong with you people?
You know. I don't like paying bills, so I don't think I'm going to do that, either.
"There is a club for people who don't like their job, it is called "EVERYBODY"; they meet at a bar".
-Drew Carey
There are only three ways this is going to end - you're going to stay at the sucky job until you die, or you're going to find a new job and leave them, or you're going to stay at the sucky job until the manipulative jerks you work for go out of business / fire you for disliking them / lay you off to save their own jobs. The first option means your entire life will suck, and the third one means your life will suck for a while and leave you unemployed in ways that make it even harder to get a new job. So you need to get your ass out of there pretty fast.
In this economy, it's not easy to find a new job, but it's a lot easier if you already have some job than if you don't. Interviewing is not only tough because it's the kind of social skill many people don't have, it's especially tough if you're under pressure from unemployment, and it's tough because there are almost always more people looking for a job than jobs available, so you're likely to get rejected unless it's an amazingly good match (and you know it going in.) But hey! you're getting dissed every day at work, so even a day of interviews where the people reject you is going to be better than a day at your current job, so it's a win, and it's practice for figuring out what you really want to do and what kinds of cool things other companies are doing so you can find the right one.
Meanwhile, yeah, go out and start something open source, or start playing with Arduino micro-controllers, or whatever. So what if the company you work for ends up owning the intellectual property for your proximity-activated Christmas-tree-light cat exerciser?
Bill Stewart
New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
I've always wondered about the "we own all your code" thing.
Companies with such a policy generally have a mechanism for waivers as well. Myself and coworkers at various employers had no problems in this regard. There was an admonition not to work on the hobby all night and show up in the morning exhausted. The admonition was offered with a smile in a humorous manner but there was probably an element of seriousness in there.
I think a famous example of waivers may lie with Steve Wozniak and Apple. Supposedly Steve did some work at HP, management was not interested in it, Steve asked for a waiver and it was granted. That work wound up in the Apple II.