When is it the right time to quit?

Question

I am a software developer for a decent sized software company who's major revenue comes from on-site consulting and web design.

I am one of very few in-house developers, whose job is maintaining a .NET 1.0 application (pretty much legacy at this point). This project has been neglected for years (due to the main revenue coming elsewhere) and is the proverbial red-headed step child of the company.

Long story short is I am about half way done adding major functionality to the application, of which I was hired on to do and I am thinking about calling it quits, and look for a job where the software I work on is appreciated.

My company isn't interested in re-writing the application, and there is so much bureaucracy about updating the web application that features and bug fixes that I have implemented and tested take several months to get released...

Have any of you been in a similar situation? would you stick around to finish the remaining half of the new functionality, or is it time to call it quits?

what would you do?

Answer 1

There are many types of developer... some would be happy to be a "maintenance drone" that just does his 9-5 shift and that's it. But it sounds like you aren't that type of developer. You want to be on interesting new projects.

Personally I would not stick around in that sort of situation. Maybe make your concerns clear to your boss(es) and see what they say.

If you do decide to leave don't burn your bridges.

Answer 2

The best thing I can tell you is that your decision should not depend on the stage of your project. Otherwise, you have to consider yourself what exactly bothers you about working on a neglected project. Personally, I would not be so concerned with a particular project (projects come and go), but would be focusing on more systematic problems with my group or with the company.

In any case, if you are considering a move, it never hurts to look around and see what your options are.

Answer 3

If you are unhappy going to work everyday then something needs to change. You can either try to get a new assignment in the current company or convince them to allow you more freedom (it sounds like you might like to rewrite it) or you can look for another job. Good luck in any case.

Answer 4

I'd ask if there was a role elsewhere inside the company you could move to after your update on this project is complete.

Then if they say no, start looking elsewhere. Some people consider it a professional courtesy to complete the project they are working on to a reasonable state before leaving. Having been there and done that, I don't recommend it, it delays you getting on with your life.

Answer 5

Also realize that companies have an interest in there never being a "right time" to quit. Assuming, of course, they want you around. If they want you to leave, that's a different situation.

So, leave when you can. If you can survive without a job for a couple months, or however long it takes to get new work, then give your two weeks right now. Otherwise, start talking to other places and set up interviews, use some sick time or vacation time to go on them.

Be professional and honest about it, as you probably want to leave on a decent note so that you can use your co-workers or bosses as references.

People leave in the middle of projects. It happens, I've done it myself. If the project was completely dependent on one specific person being employed there, then it was poorly managed. If you've written good code, and it can be finished by someone else, then you've done all you're expected to do. You are not contractually obligated to finish this project. If it was important enough, they would have made you contractually obligated.

Answer 6

As others have underlined, if you are not happy, there is clearly something wrong, and you should clearly do something about it lest you want to procrastinate, drag on, and make your life unhappier. I, or for that matter, no-one can really tell you when is the right time for you to quit. Only you will know that, when that time comes. I can tell from experience. You just know yourself when it is the right time.

Answer 7

If there is no good time to quit, then by corollary any time is a good time to quit. You can walk any time you want. What happens to the project afterwards is mostly a reflection of your previous employers, not you.

If you are unhappy with the work, talk to your manager and find about moving to other work. In the people I manage, I actively look to see if they're happy with what they're doing and try to create a path to what they do want to do with milestones for getting there. Not all managers are active in doing this and need a poke - otherwise your manager needs to read your mind. You can help fix this with more communication.

Answer 8

if you decide to quit.. make sure you find another job FIRST.

The economy, as we all know, is in the proverbial crapper.

Answer 9

I've been in a similar situation. Working for a company that I liked but on projects and technologies that were going nowhere. I ended up calling it quits and moved to another company that had what I wanted. That company ended up being difficult to work for. I traded a good company with bad projects for a bad company with good projects. 2 months after I left the first company I had lunch with my former manager and he asked me to come back and help them tackle better projects that they just couldn't do as they didn't have the technological skills. So, I got back to a good company with good projects.

I'm a firm believer that staying too long at any company is bad for both you and them. So, if you're ready to move, move.

Answer 10

If you're asking this question publicly, it's probably a good time to quit...

Answer 11

I'm in almost the same situation. Currently maintaining an older, monolithic ASP.NET 1.1 web application, and besides tacking on new features here and there, and maintaining the backend, I've been considering a move for a few months now. To answer your question, my own insight on the situation has been this; as soon as I'm not enjoying what I'm doing in the day-to-day, it's probably time to find something that will better fulfill you. Good luck, to you and me. :)

Answer 12

I'd be looking for another job first and recognize that it may not be easy finding a good work environment to get into, IMO. If I found a good place to get into, I'd likely turn in my 2 weeks notice and be gone. In that 2 weeks, I'd likely prepare documentation for whoever will pick up this project in the future.

2 weeks notice seems to be common in the US and Canada but may vary depending on your locale. If you were higher up on the food chain I'd suggest telling management you are thinking of leaving and what would you have to do before you leave. I remember one boss of mine spending months where he was because of what the executives wanted from him before he could go.

At the same time, if you have sufficient savings to pay the bills for the next 6-9 months and feel that your job is making you worse every day, then I'd say quit now as it may help your self-esteem to get away from the toxic environment.

Answer 13

Does your boss understand the value of your work? Are you on good terms with him?

1. Figure out what it would take to keep you reasonably happy at your current job. More money? Better job title (good for the resume)? Working from home? Come up with specifics.

2. After you know what it would take for you to quit pining for the fjords, approach your manager. Tell him that you don't want to leave, but there isn't enough keeping you there. Tell him what the company could do to make it worth staying.

3. Be prepared for the possibility that you will be fired for expressing any dissatisfaction. But also prepare yourself for the possibility that they agree to your terms. (Which is why you should consider them carefully.)

Answer 14

One of my .NET heroes, JP Boodhoo, has made a very good point in one of his blog posts about when it's time to leave. I'm in a similar boat and what he said has made a lot of sense to me and I'm getting ready to move on to more challenges.

He said: "If I am not enjoying the place that I am currently engaged, and I have done everything in my power to impact change for the betterment of the work environment that I am in, it is time for me to leave. I do not have time to waste being in a place where I do not feel challenged and happy about the work that I am doing."

I would recommend reading the whole post. It's really inspiring.

http://blog.jpboodhoo.com/DontPlayLimboWithYourGoals.aspx

Answer 15

Look around. Work is not only about programs. It is about people who do them and customers who use it. Do you like your boss and colleagues? You may wish your company customers the best and be ready to deliver great software but are they ready for it?

If colleagues are good and boss is great and customers really waiting for product then it is THE place to work. If not, then even greatest software will not change it for better.

Answer 16

When you have in your hands a written offer for a new job which you have already agreed upon, to do interesting stuff, and with a better pay.