5

"Just start ahead"

I am supposed to transform calls from one api to another one. Yet there's no documentation, ambiguous code statements, no examples of what values are contained -- but sure, let me just start assuming how the whole thing is supposed to work. That won't lead us more into a murky waters at all.

Even more frustrating: We own the api. We should be able to tell by the access logs how we are queried. Yet for some reason, access logs cannot be accessed and I shall "just work from the swagger defintion".

Well, that swagger definition is broken, its example are shit (somebody liked to use undefined in optional fields, making me wonder even more what the heck is going on here), and I have no idea of what I am doing. Fun times.

Comments
  • 0
    Make sure your concerns are documented in written communication e-mail and then "Just start ahead" 😏
    Let me guess: the guy that wrote that spec and the api isn't around anymore?
  • 0
    @don-rager they are around. They have coded the api quickly over two years ago though.
  • 3
    What is with all the APIs with no metadata? We need a global PSA for this:

    "No metadata? No API"
    Brought to you by competency.
Add Comment