The best way to leave a job for a developer
There are a lot of reasons to leave a job, I won’t focus on the reasons in this article.
I will focus on the best way to handle the transition from the old job to the new job.
There are not much written content about this topic out there.
I think the transition should be fair to both sides: the old and the new company.
Fair is a simple concept that is hard to describe.
How to be fair with the old company?
For the old company you need to give enough time to let them hire someone else to be in your place. I think 15 days is a good time frame.
You should also transfer your knowledge of the codebase to the ones that you maintain the code.
Write down all the implicit knowledge that you have about the codebase and
Shares tags with
- Bleeding edgeedge Bleeding edge is the state of art of something It is the new technology When you focus on bleeding edge (new), you have an advantage as everybody start in a clean slate. You…
- Career RiskMost people does not optimize to take career risks. I have a lot of smart friends that are stuck on bad jobs (learning almost nothing, and without change of growth) that can't…
- Consulting/ProfessorsIf you never own the whole process of doing something, like having Skin in the Game, you never will "taste" reality (Reality has a lot of details I think this happens with who…
- Doing the right thingSometimes someone in your organization does not wanna do the right thing (maybe your manager, maybe your boss, or CEO) they could decide not to invest in having tests in place not…
- Generalistgeneralist are robust to automation automation will automate a specific task, it can't be easily generalized generalist are better for long term solutions for holistic solutions…
Sign in with GitHub to reply.
Select any passage to quote it.
Comments