Writing good documentation is a mission-critical aspect of building software these days. Whether you are writing something for yourself, for the Open Source community, or your company, it's essential to keep things documented for good reasons:

• It makes developers more productive since they can rely on the docs to understand how to use your software.
• It makes developing the software itself easier promoting knowledge sharing amongst developers.

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.