That's where mentorship comes into play - mentoring the rest of the team has greater effects than trying to plow through code over the long haul. The reason is

That's where mentorship comes into play - mentoring the rest of the team has greater effects than trying to plow through code over the long haul. The reason is that it creates a silo that the one high producer gets saddled with, and it creates a bottleneck that ultimately probably will even result in the high producer becoming unhappy due to being distracted with all of the maintenance burden from his/her code. I used to be more of the former type who would try to power through everything & still display flashes of it whenever I do have to code, but after being a lead engineer for almost a year, I understand more deeply the value of knowledge transfer and making everyone more productive. Having a team that is genuinely happy to work together has an effect of creating more for the company than the sum of their parts because the team is more honest with each other from being comfortable/not having to fear reprisal, which results in better (& planned) team architecture, mistakes being caught as early as possible, and overall decreased stress.