I got thinking about caching again today, recall that I explained that cache is what allows browsers and other software solution to save you time and data cost by preloading saved resources rather than accessing the whole platform online. I also likened it it to how we as people aren't very good at proofreading our work because we see what we think we wrote and not what we actually wrote down and it makes it harder to fix our errors.
Well there are some other ways to reduce the negative effects of caching without disabling caching totally, we call it cache-busting, when we as software engineers add new things or features to our web apps or software solution, there are unique values we give the digital assets on our software solution. The way caching works is that if the browser scans through the website and doesn't see any change in the name of items, it assumes it's the same items (we usually don't change the name of assets) and proceeds to load that web page from the browser memory.
With cache-busting, the browser will see the same names with some added figures or values that trick the browser in order to make it load the web page from the server and not from the browser memory. This will only take effect when we add new things. Cache-busting is how we have our cake This d eat it in software engineering, we don't disable caching but we don't let it get in our way either.