A: A weird question you may think, but this happens all the time and there is a pure school of developers that are anti-SharePoint. There are three distinct reasons for the resistance:
Many developers look down on SharePoint development for several reasons. SharePoint development lacks some of the basic development standards. Many developers complain that it lacks a unit-testing story. A common complaint among developers is that it is difficult to work with and deploy. Part of that difficulty is the complexity in development environments. Developers also cannot see the benefit of SharePoint development and how it helps them in their development tasks.
To some developers working within a product framework can feel restrictive and perhaps not as malleable as the current new technologies that we've come to know and love. It can feel somewhat "behind the times". SharePoint tools can seem more like configuration rather than development. This is a reality of the product and is a valid resistance. Development must become a broader definition than just writing code, it must become more solution focused.
Developers are wired differently than say, business analysts (just look at their desks). They are technical and their level of expertise is hyper-focused. They want to write code and they want that code appreciated. End users don't usually provide this kind of affirmation. However, they may not have the skill set to apply what will essentially benefit the end user.
Developers want to be good at what they do and that means efficiency. It can be difficult for developers to put themselves in the shoes of the end user because an end user usually doesn't see all the things "under the hood". SharePoint developers need to place themselves in the shoes of the end user throughout the development process and sometimes that means sacrificing the cool things that can be done with raw code and implementing the best strategies for the end user. This doesn't necessarily mean they reject being end user focused, but rather they need user interface skills, user acceptance, and managing expectation skills. Although the project management will usually be coordinating this with the developer, this form of communication to the project manager is essential.