I think another great question to ask is how are you importing separate SASS files and spitting them out?

Is everything getting compiled into one style.css and spit out on every page? Do you have one global.css and separate style.css sheets for different pages?

Instead of appending classes to your HTML, have you thought about writing the SASS like this:

.sampleElement { ...

}

The apostrophes at 1:26 - 1:29.

The Freight family is absolutely incredible.

Right now we're in the early stages a larger project and keeping everything in smaller, separate files (think 20-50 lines for each file) to modularize as much as possible.

Using BEM with SASS has been a great experience so far. Nesting with a "&--" or "&__" pseudo selector is immensely powerful.

These are great. +1 for the tees. Office team has their credit cards out!

The dudes at Hard Copy Printing in the Financial District are pretty badass.

Also check out the Console. Give it a bit....

I think it's up to you to manage that separation. As nice as it would be to embody that "unicorn" status, the reality is that there are only so many hours in a day. If you're splitting that between design/creativity and code/best practices/chasing the bleeding edge you're gonna end up burning yourself out. Is it empowering to be able to do it all? Absolutely. Is it sustainable? Not in my opinion.

Take a step back and evaluate what you prefer doing. Focus on that.