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?"

Comments

Sucks to be you!

[Q-Hack!]

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.

Re:Sucks to be you!

[Moryath]

I work for manipulative jerks.

This right here tells me it's not about your passion for coding. It's the fact that you dread going in to work each morning to face the manipulative jerks.

Either go above the heads of the manipulative jerks and report what's making a hostile work environment, or start brushing up your resume, practice interviewing, and start looking for a new job.

Re:Sucks to be you!

[dkleinsc]

Either go above the heads of the manipulative jerks and report what's making a hostile work environment, or start brushing up your resume, practice interviewing, and start looking for a new job.

If you're going to do the first one, going over the heads of manipulative jerks, do the second one as well, because chances are the manipulative jerk's superiors are manipulative jerks who are more invested in your manipulative jerk bosses than they are in you.

Re:Sucks to be you!

[s73v3r]

Second: Start a project on your own that is fun. (in my case: Make games!).

This can be a good suggestion. But before that happens, he needs the inspiration to actually go through with it. Wanting to do some programming, but not having a single idea of what to do is an awful feeling.

Re:Sucks to be you!

[xmundt]

Greetings and Salutations....
          Ageism has been, and continues to be, a serious problem in the IT profession. It does not apply to just coders either, as it seems that being over the age of 50 is a kiss of death for system administrators, DBAs, analysts, etc. I suspect that the issues that control this are (in no particular order)
          1) Folks doing the hiring assume that anyone over the age of 50 is so stuck in their rut that they are out of touch with the newer technologies. Actually the cut off age here seems to be closer to 30....
          2) The younger a hire is the cheaper they will be for the company. Most companies would rather pay a kid $40K a year and not worry about the fact that it might take him a week to do what a $100K a year hire could do in a day or even a few hours.
          3) Again, because of the incorrect perception that IT people are an expense rather than an asset, HR hires the kid who knows how to do ONE thing, instead of the older, more experienced person that knows how to do a dozen things, and can likely apply that knowledge to find a way to make the company more efficient, using the excuse that the older hire is going to be "too expensive".
          I will agree that, in the short term, the older hire requires a larger check...but in the long term, is likely to more than pay that back with the increases in efficiency and the savings he or she can bring to the company. This makes no difference, though, because these days, short-term profit is the only goal that companies can look for.
            4) most management knows that the older hire is going to be more of a pain for them, because experience brings understanding of exactly how poorly most management runs things, and, a considerably lower tolerance for that sort of nonsense. The "fresh face" just out of school is willing to put up with a lot more crap that we, with that experience, are not. The kid actually believes management's vague, hand-waving promises of great rewards later on for 80 plus hours of work now!

Good advice .. but check your contract

[Anonymous Coward]

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.

Re:Good advice .. but check your contract

[ATMAvatar]

Even if you do sign away all rights to your code, there is a small handful of states whose laws override those contract provisions.

For example, I live in Kansas, and Statute 44-130 explicitly states that employment contract provisions about code I write on my own time using only my own resources are null and void. There are a few limitations to that, of course - the coding I do has to be unrelated to my workplace and not derived from work I do at the office, and I have to disclose to my employer what those projects are.

This was covered a little more in-depth in a question on OnStartups, one of the StackExchange sites.