F5, F5, F5.
"Why aren't my changes updating?"
*20 minutes later*
Browser caching...
FUFUFU

Still better than
Fuck I didn't save that one file

Ctrl-F5 forces fresh reload on chrome

In chrome, if you have the developer tools open, right click on reload button, you have a menu that you can 'clean cache and hard reload'

Cache Killer extension for chrome. I've never known I needed something so much before.

on chrome, you have an option to remove caching when dev tools are open. But then you have to not forget opening dev tools. If you have an assets pipeline, cache bursting is a must-do, cause it forces te downloading for your visitors also.

You could also run an auto reload script which updates the browser whenever you save. So much more fun to see if happen automatically.

@elgamine the cache busting method is definitely the best choice. I use a versioning script with my grunt file watcher process, so every time I save, it adds a hash to the file name and updates the relevant files that reference the asset. Combine that with a hot reloading module, and you're good to go for testing, as well as a much more visitor friendly method. Your users are unlikely to hard refresh your site to pull changes lol.

I still never had browser cache affect my web development process. Never has it blocked changes I've made, at least as far as I can tell... 🤔

Ahh, been so long since I needed to worry about that.

@Koolstr means you never used CSS b4

@matanl And yet that is patently false. So what's up with my dev process?

@Koolstr Maybe you use an environment which takes care of removing the caches for you? If you write a simple css layout in notepad++ you'll need to ctrl+f5 from time to time

@matanl haha no chance in hell am I going to use notepad++ while sublime text is still an option