Earlier quoted context omitted.
It's the responsibility of the company to ensure they are capable of coping with a coder leaving. I've worked for companies where they've just not given any time or thought to what happens if the coder leaves.
I agree, that companies should be prepared for developers to leave. I maintain that developers and engineers should leave their work maintainable. I know I'm going to get downvoted, but this needs to be said. With great programming power comes great programming responsibilities. And you and I know this power doesn't come from silicon or management. We all bitch about crappy products, and fail to see the developers on…
Now, C# and Java are pretty close syntactically so hopefully they'll be OK. There is a huge difference in libraries and core API structure as well as deployment though, so it's not just an easy step to take. Having marginal .NET skills does not translate to marginal Java skills though. We do have a brand new Java dev, but it's really asking alot to put all of this on their shoulders with just a few months out of college.