Often when testing a website, I need to clear the server cache, cdn cache, and the browser cache. That’s 3 extra to-dos every time I need to test a feature, which is normally coupled with the scores of times I need to test said feature. This means that to get a feature to live state, I might need to clear 60 caches (3 x 20 code tweaks/pushes). Perhaps you work this way as well and feel burdened by this incessant cache-clearing.
Well today I learned that there’s an option in all the major browsers’ dev tools to disable browser caching by default while the tools are open! This means that instead of 60 to-dos, I now have only 40 – not ideal but a 33% efficiency improvement. Nicholas Bering wrote a great article about how to disable browser caching in all the major browsers.
I hope this helps you out as much as it did me!
More posts from themightymo.com
How to Convert .aiff to .mp3 files via Command Line
Yesterday I ran into an issue where I needed to convert .aiff files to .mp3. DBPowerAmp was recommended to me as a paid GUI tool. But I wanted something more lightweight, since this is a task I rarely need to do (most of the time, I’m already in Logic Pro, and exporting is simple there).…
Google Removed Our Business Listing – How we restored our biz to the Map and got our reviews back.
I was about to send an email to a potential customer pointing them to our 5-star Google Reviews via our Google Business profile (e.g. the Google Map), hoping this added information about our customers’ past experiences might help me close a deal. But when I checked the Google Reviews link, it was down. And after…
The Price We Pay: Cloudways Off-Site Backup vs. Budget WordPress Hosts
Cloudways Off-Site Backup Pricing Calculator: The Ultimate Cost Guide