The problem with caching is it’s not always the right cache.
When coding, cached data, is data stored in memory (on a file or some other structure) that makes retrieving constantly used data easier to get to.
The goal is to reduce calls.
Bad cache is data that’s not updated, but the user thinks it’s updated.
Bad cache causes delays, wasted effort, and excessive troubleshooting.
Bad Cache slows us down when it’s meant to speed us up which can happen when we rush to build a new feature or service.
If something new slows people down, it’s not going to get used, it’s going to get turned off.
