We are mostly likely the most impatient iteration in our species history, our current era is marked with unprecedented innovation, the bar upon which speed is measured has been taken to new highs so much so that speed is now measured in microseconds. The tech industry is responsible for our high level of impatience. Through consistent innovation, we've made some processes as fast as the speed of human thought.
Cacheing is one of the ways in which tech is able to provide such near-tachyonic speed. When you frequently visit some online resources for example websites, memory is allocated in your device storage such that the next time you try to access that resource the page/resource is loaded not from the internet or database but from your device storage instead, this makes for faster load times and improved customer experience.
While that sounds good for the customers it's actually a nightmare for developers, those online resources takes a lot of iteration to build as such we're consistently checking those online resources to ensure that the changes we're making are being effected real-time, say we make a mistake that produces an error and we're trying to fix it, cacheing can make that page keep displaying an error (even after the error is fixed) because the page isn't being loaded from the source/database, but from the device storage which stored the error in its memory and keeps fetching that error. This is why developers mostly turn off cacheing on their browsers and resources. We value real-time concurrency over speed.