13 posts tagged with "tweak"

Errors handling is part of our work as developers. You can try to ignore them at first, but to offer a good user experience, you don't want your website breaking just because one of the API endpoints decided to give up on you. These days we try to find clever workarounds to run our applications with a graceful degradation strategy. We build software to work in an optimal environment while providing certain fallbacks not to break the experience entirely when there's some disturbance in the system (e.g., lousy network condition, CPU lag, etc.).

In this article, we will understand how to maximize productivity when tackling HTTP requests error handling from a front-end development perspective.

There might be a few reasons why we would want to delay an HTTP request:

• You want to test how your UI behaves to a slow response from an upstream service.
• There's a race condition in my code, and I suspect that it happens when the request to A is slower than the request B.
• You want to show off that beautiful loading animation you've been working on all day!

A Pragmatic Mocking Tool​

When I first started my career in the software industry, I began to get familiar with Single-page applications and how they interact with servers, mainly through HTTP requests to retrieve or send data to the end-user. If you're working with the front end, there's a very high chance you found yourself in one (or multiple) of the following scenarios.