Sharing should be a basic policy, otherwise you create silos and silos are bad for business, especially if you have high turnover. A leader should not only encourage sharing but also make sure this sharing actually happens :D
You can offer him a contract as consultant for a time. By hours, just in case that a problem appears.
But I think that the best solution is the preventive one.
Encourage pair programming, or a second developer for every stuff developed.
In some newspapers they use to have peer-review, all the stuff developed for one should be reviewed for another random workmate. You may assign a review partner for every developer.
In general I don't advice to outsource tasks that can not be reviewed and fully understood by an internal developer.
For the people that go away, you can involve the substitute a period before it leaves. The first tasks could be documenting the existent code. If some question arises there is time for direct explanation.
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.
It is supposed to be. How do you ensure the knowledge have been shared?
We're human beings, you talk to the other person you're sharing the documents and knowledge to :-)
You mean the leader should encourage sharing in the team. Right?
Sharing should be a basic policy, otherwise you create silos and silos are bad for business, especially if you have high turnover. A leader should not only encourage sharing but also make sure this sharing actually happens :D
Yes. I agree.
But some old guys do not want to share. The worst case is they do not know.
You can offer him a contract as consultant for a time. By hours, just in case that a problem appears.
But I think that the best solution is the preventive one.
Encourage pair programming, or a second developer for every stuff developed.
In some newspapers they use to have
peer-review
, all the stuff developed for one should be reviewed for another random workmate. You may assign a review partner for every developer.In general I don't advice to outsource tasks that can not be reviewed and fully understood by an internal developer.
For the people that go away, you can involve the substitute a period before it leaves. The first tasks could be documenting the existent code. If some question arises there is time for direct explanation.