I used to use Drupal in my everyday work. I got very familiar with it, how it worked, and how to avoid its (many) pitfalls. I was able to build sites that met client needs quickly, and they were able to make use of them.
Then I decided to change jobs, and I consciously turned away from being a “Drupal guy”.
The thing is, when you are really experienced at using a particular piece of technology, the prospect of moving on from it can be intimidating.
I had a situation at work where we had an edge case in a component: sometimes a logo didn’t appear. When I noticed this, I responded as a dumb developer.
I didn’t look around, and notice in other very similar components that there was a fallback for this scenario. Instead, I just saw a lack of a logo, blinked, and just mentally folded.
Don’t do this. Don’t be a dumb developer.
Linting your Sass is a great way to ensure some degree of code quality. At the very least you will have greater stylistic consistency.
One thing before we get started: be careful not to blindly follow what a linter says, though: treat linter rules as guidelines, not absolutes .
In my text editor of choice, Sublime Text 3, the best way to get linting in any language is currently using the Sublime Linter package. Once that is installed, you can install extension packages for each language you want to lint.
In my case, the main ones are Sass (as