alert()statements throughout your code. We now have inspectors, debuggers, and other tools that make things much easier. And you've probably encountered
console.logand the power of JS consoles. This can provide some good insight into what's going on with your code, but there is a catch.
TL;DR: Just here for Browsersync setup? Skip to the steps.
I’m always looking for ways to reduce the time between saving a file and seeing changes on the screen.
When I first started working with Drupal, back in the day, I would ftp changes to a server and refresh the page. Once I found Transmit, I could mount a remote directory locally and automatically save files to the server. At the time, my mind was blown by the efficiency of it. In hindsight, it seems so archaic.