11

We have to use a 20 year old API that is half assed and doesn't even work right every time.
Every three months the same discussion comes up why something doesn't work that relies on that API. I have to explain the situation over and over again... And then my boss starts to give 'solutions' which we already use or are utterly stupid... >.<

In case someone is wondering: SOAP API on a Windows Server 2003 with timeouts every few minutes and XML output in a language that is not English (even the tags!).

Comments
  • 0
    Sounds like this should be upgraded so you can use your time more productively. Not to mention the frustration and stress.
  • 0
    It always baffles me when management doesn't see the value in upgrading... Yes, it costs time/money, but the amount of time you could put into new development after the upgrade of a legacy system pays for itself.
  • 0
    Unfortunately I can't do anything about that API because it's from another company where we fetch data using it.

    I've been told they're working on a REST API but that's been going since January now.
Add Comment