3 ms·
Yeah, these codebase-gurus are often bottlenecks. I personally think they should invest time on documentation and walkthroughs. They could also answer some que
by calibraxis 13y ago
Yeah, these codebase-gurus are often bottlenecks. I personally think they should invest time on documentation and walkthroughs.
They could also answer some questions on the condition that the newly-enlightened person must document the answer. (Kind of like caching.)
The problem is that many programmers have little training in effective communication (that is, the skill of somehow transferring/inspiring a mental representation from your mind into someone else's). It's like pulling teeth to get them to document — even if they desperately want to escape being pigeonholed as the only one who understands the crappy legacy system. (Even when job security isn't an issue.)
- unclebucknasty 13y agoYeah, that's true regarding effective communication. And, in addition to that, I think some people actually like being the bottleneck. They want to be known as the go-to. I've definitely seen this in enterprise situations. Not only do they fail to try empowering other devs, they actually purposely hold on to information in order to foster ongoing dependence. Whether it's for job security, ego, or otherwise, it's not an uncommon sight.