Friday, February 21, 2020

Bad API behavior

Ok, so we were running test code yesterday evening to get some data for a presentation, and there was a typo in a text string that a downstream system didn't like.  So this morning I get angry emails about the "bad data" and have to roll back the changes.

But what really pisses me off is that the downstream system was coded to expect exactly certain strings in that field, and if the contents did not match, IT FUCKING CRASHED.

This is not good software design.  It can complain, log errors, ignore the messages, all sorts of annoying things, but it should not, EVER crash when it can easily avoid doing so.


No comments: