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
Today I had an issue where I needed to merge two folders, each of which contained many sub- and sub-sub folders that had lots of images. After a lot of trial-and-error and some Googling, I found the best solution is to use the “ditto” command in Terminal like this: That’s it! Hat tip to AppleInsider.
I wasted some time today to bring you (dum dum duuuuum!): Some Surprising Trends in Website Development!
I was recently asked to look into creating some secure http headers as well as forcing a website to load over TLS1.2+. Below are my “how to” instructions for updating these settings within WordPress and Cloudflare. Install & Configure the Cloudflare WordPress plugin. Make sure an SSL Certificate is installed on your host for your…