How to Deal With Fear of Custom Dev
I'm dealing with an issue at my current employer that has seriously made me consider seeking employment elsewhere.  They are under the impression that 100% of custom development should be eliminated and replaced with COTS products, such as SharePoint.  While I realize that this is not a realistic expectation, I've found it impossible to argue my points with the people in management that share these views.  Their argument usually involves something along the lines of a feature already existing in SharePoint that covers feature X, therefor there is less risk involved and testing doesn't have to done against it.

Case in point, we have a situation where a SharePoint list is completely **incapable** of meeting customer expectations and requirements.  Saving this data in a SQL database, however, would easily satisfy the requirements.  Any time our development team suggests going outside of the boundaries of SharePoint, however, management goes up in flames about how every line of code adds to the complexity of the project and increases risk.  While this is certainly true in some situations, it's not always the case.  Their argument, however, is that since SharePoint provides a mechanism for storing data, that we should use it 100% of the time.  Regardless of if it meets customer requirements, or not.

I've gotten to the point that I hate coming to work because I'm constantly forced into doing things that I know (with 100% certainty) are not right and that could be made right by doing custom development.  It's simply what seems to be an impossible argument where I work, however.

Have any of you experienced a similar situation?  If so, what have you done to work through these challenges?
How to Deal With Fear of Custom Dev
===

I'm dealing with an issue at my current employer that has seriously made me consider seeking employment elsewhere.  They are under the impression that 100% of custom development should be eliminated and replaced with COTS products, such as SharePoint.  While I realize that this is not a realistic expectation, I've found it impossible to argue my points with the people in management that share these views.  Their argument usually involves something along the lines of a feature already existing in SharePoint that covers feature X, therefor there is less risk involved and testing doesn't have to done against it.

Case in point, we have a situation where a SharePoint list is completely **incapable** of meeting customer expectations and requirements.  Saving this data in a SQL database, however, would easily satisfy the requirements.  Any time our development team suggests going outside of the boundaries of SharePoint, however, management goes up in flames about how every line of code adds to the complexity of the project and increases risk.  While this is certainly true in some situations, it's not always the case.  Their argument, however, is that since SharePoint provides a mechanism for storing data, that we should use it 100% of the time.  Regardless of if it meets customer requirements, or not.

I've gotten to the point that I hate coming to work because I'm constantly forced into doing things that I know (with 100% certainty) are not right and that could be made right by doing custom development.  It's simply what seems to be an impossible argument where I work, however.

Have any of you experienced a similar situation?  If so, what have you done to work through these challenges?