Take the 2-minute tour ×

Some developers keep their job for too little, as if they have commitment issues.

Some keep their job for too long, as if they're afraid to leave their safety zone.

What is the optimal number of years a developer should keep a job?

share|improve this question
Situationally dependent (which probably means this question is due for a close), as there are many implications based on factors like time in job, advancement through your previous jobs, and personal thoughts. If you hop jobs every year, that might send some negative signs to others, whereas if you stay at a job for a very long time, you'll be expected to exhibit knowledge commensurate with prolonged exposure to whatever's on your resume. I leave a company based on a litany of reasons, but usually the ones that win out are if I'm just unhappy and there's no fix. –  birryree Apr 4 '12 at 16:56
Voting to close as too localized; there is no "right" answer that fits everyone's needs or situation. –  John Bode Apr 4 '12 at 16:56
It looks like you think that the developer is always in control! I wish this was the case. –  Emmad Kareem Aug 6 '12 at 8:31
I like this question, but in its current state, it's not a good fit for this site. –  Jim G. Aug 6 '12 at 16:01
add comment

closed as not constructive by jmq, John Bode, gnat, Wyatt Barnett, Karl Bielefeldt Apr 4 '12 at 17:01


1 Answer

up vote 7 down vote accepted

There is no real set minimum or maximum time frame that is optimal. It is different for every person, and every job.

My advice, however, is to stay for as long as benefits you as well as your employer. That is to say, that you are in an environment that allows you to continue to develop your craft and learn new languages/paradigms/technologies.

share|improve this answer
thank you! great answer! –  nurne Apr 4 '12 at 17:26
add comment
