Yep.<p>The thing is, the company needs to understand that the smartest thing to do is to leave that person alone and task them on educating (here via docs, but also in other ways) the other developers (assuming the team is of sufficient size, which in my experience is the case as soon as total headcount is 3).<p>Hoarding expertise like that is a good way to waste company resources (because other devs function at a great disadvantage) and to bring down stress upon onself (becuase you become a bottleneck and that gets to be super stressful).<p>The fact of the matter is that it is anti-social and bad practice for these devs not to take a step back and write down the coherent vision of their product--and if they can&#x27;t explain the vision in a handful of pages with some simple diagrams, <i>they&#x27;ve probably deeply fucked up the design</i>.<p>The company, management usually, needs to bite the bullet and sacrifice short-term firefighting ability for mid-to-long-term training.<p>If they won&#x27;t do this, you should leave.