We worked on our own product, but the first customer to use it, and the one to finance the development had some horrible technology.
First of all, we focus on interface, ux, usabillity and design, so we had planned to build a client iPad app for a server backend, developed by a third party. That third party turned out to be completely incompetent, and we had to ditch them half way through to build the backend on ourselves (me, that is) too.
We still had to sync our backend with the clients horrible hack of a CRM. Using a backwards, badly documented SOAP webservice that was only partially implemented.
I feel your pain. It's seems some of the most popular work available is based on some impossible existing code base that some manager wants to make an "interface" for... yet the existing engineers could not even do it. So the manager thinks they can call in a specialist to save the day. Maybe the day can be saved, but if the APIs/Services are unfinished undocumented inconsistent crap then what... We all need a strong radar detector for this kind of work.
First of all, we focus on interface, ux, usabillity and design, so we had planned to build a client iPad app for a server backend, developed by a third party. That third party turned out to be completely incompetent, and we had to ditch them half way through to build the backend on ourselves (me, that is) too.
We still had to sync our backend with the clients horrible hack of a CRM. Using a backwards, badly documented SOAP webservice that was only partially implemented.