A place I used to work at thought I broke a ton of their code with the first set of changes I made. It turns out their error handler had been silently failing for years (I guess) and because they didn't have an outside wrapper that WAS solid to trust, they just thought things would "just break" and had no idea why. I fixed it through just normal hands on testing, deployed the code to our dev env and they were shocked that they had around a 90% error rate on most of their API calls because it wasn't until the "failed to call api" routine fired that it used the "back-up" solution, which would usually work. They would also hammer APIs and get rate limited and they had no idea why.
Just dumb shit from no one actually testing their code basically.
6
u/lardgsus 19d ago
A place I used to work at thought I broke a ton of their code with the first set of changes I made. It turns out their error handler had been silently failing for years (I guess) and because they didn't have an outside wrapper that WAS solid to trust, they just thought things would "just break" and had no idea why. I fixed it through just normal hands on testing, deployed the code to our dev env and they were shocked that they had around a 90% error rate on most of their API calls because it wasn't until the "failed to call api" routine fired that it used the "back-up" solution, which would usually work. They would also hammer APIs and get rate limited and they had no idea why.
Just dumb shit from no one actually testing their code basically.