I won't address his pay, but as for his work, this guy is getting bogged down responding to emails about projects that are in maintenance mode, with no new deve

I won't address his pay, but as for his work, this guy is getting bogged down responding to emails about projects that are in maintenance mode, with no new development approved. There are three possibilities. One is that he failed to mention that he has been tasked with user support. The second is that the old projects are buggy or fragile as hell, and maintenance is a big and valuable job that deserves the time he puts into it. The third possibility is that he is being barraged with support requests and enhancement requests which are NOT his job to handle. In that case, this guy's manager needs to run interference and get the other managers out of his face. When you want new features added to projects in maintenance mode, you aren't allowed to harass a developer who has been ordered to only fix bugs on those projects. (It's normal to do so, but that's because people are dicks.) When you need support, you don't harass a developer who isn't tasked with support. (Again, it's completely normal, but only because people are dicks.) The people taking up his time are taking advantage of his experience to get work done that they can't get done the right way. His manager needs to tell all those folks to back the #@%^ off unless they have a valid bug report. Then he can concentrate on his real job: his new development projects and bug fixes on the maintenance projects.