I think scarface74 is right. At my last job, it was clear from the job descriptions that certain people (like me) were expected to spend a substantial amount of

I think scarface74 is right. At my last job, it was clear from the job descriptions that certain people (like me) were expected to spend a substantial amount of time mentoring, leading and working on higher-level tasks, and others were expected to primarily code. IIRC, the pie chart showed that I was only expected to code around 15% of my time. But that was because the organization realized that after a certain point, the knowledge of the senior developers was best used to bring up the level of the team rather than just crank out code. If you're a dev who's expected to basically produce code all day long but you decide you'd rather spend your time helping others, you shouldn't be surprised when you take a hit on your performance review. This isn't a problem with the organization, per se. It's a problem with a dev deciding to do something other than what he's expected to be doing.