A job hopping developer will never have the opportunity to get the feedback on their long term decisions.
I'm not sure where I'd be without this kind of feedback. Making it valuable for both the developer and the company to create lasting relationships is key.
One more thing... what about the third option of leaving and coming back? I feel like that's a reasonable scenario that doesn't wind up happening enough due to resentment or old-timey ideas of loyalty. If I wanted to go to a different kind of company, learn a lot, but be welcome back with open arms if I were to return in the future, it would be a pretty great outcome for everybody. It's not unheard of, but it's rare.
I totally agree with you about the third option. This is an absolutely valuable option.
It's great for developers to see other company structures, policies and tools. This will let developers value the things, they had in the previous job.
As you already said, it's also great for employera. A developer may come back with great possibilities to improve processes, which have been successfully established in other companies.
Beekey Cheung is a software engineer with a large amount of enthusiasm for economics and a passion for education. He loves mentoring other programmers and is currently building an application to te...
Yeah, I think there is definitely an advantage to sticking around for a little bit. I've met a lot of developers who know a wide variety of technologies, but don't actually have the skills to maintain a large production system because they've never stuck around long enough. Yet there's a balance there. Stay at some places for too long and the developer usually stagnates a little. At that point the option to leave becomes more advantageous than sticking around.
I don't have any scientific evidence of how well leaving and coming back would work, but anecdotally I have never seen it work out well. The people I know who've done it only did so because the place they went to was much worse. Going back was more a decision made out of desperation rather than positive intent.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm not sure where I'd be without this kind of feedback. Making it valuable for both the developer and the company to create lasting relationships is key.
One more thing... what about the third option of leaving and coming back? I feel like that's a reasonable scenario that doesn't wind up happening enough due to resentment or old-timey ideas of loyalty. If I wanted to go to a different kind of company, learn a lot, but be welcome back with open arms if I were to return in the future, it would be a pretty great outcome for everybody. It's not unheard of, but it's rare.
I've received feedback on projects done at former employers from former colleagues. It's not as formal or measurable, but it's something.
Hi Ben,
I totally agree with you about the third option. This is an absolutely valuable option.
It's great for developers to see other company structures, policies and tools. This will let developers value the things, they had in the previous job.
As you already said, it's also great for employera. A developer may come back with great possibilities to improve processes, which have been successfully established in other companies.
It should happen more often.
Yeah, I think there is definitely an advantage to sticking around for a little bit. I've met a lot of developers who know a wide variety of technologies, but don't actually have the skills to maintain a large production system because they've never stuck around long enough. Yet there's a balance there. Stay at some places for too long and the developer usually stagnates a little. At that point the option to leave becomes more advantageous than sticking around.
I don't have any scientific evidence of how well leaving and coming back would work, but anecdotally I have never seen it work out well. The people I know who've done it only did so because the place they went to was much worse. Going back was more a decision made out of desperation rather than positive intent.