Does not documenting code result in job security? [closed]
- by Barry Brown
Possible Duplicate:
Should you write good documentation and clean code to increase the “Bus Factor”?
I often ask young programmers why they are not documenting their code. Their responses, perhaps jokingly, frequently include "job security." I hear this from experienced professionals, too. And not just in programming; network engineers and system administrators widely subscribe to this belief.
Can you really ensure job security by holding the details of your work in your head rather than on paper (or in files)? What's your experience?