Code, code, code

Damian Dulisz @kamil Yup! Prefixed BEM and almost flat classes for CSS scoping and SMACSS for file & responsibility organization. Once you go this way, you don't want to go back! :D
However I've recently read about this: medium.com/seek-ui-engineering... Might be interesting!

Kamil Grzegorczyk I was even meeting J. Snook last year in NY and I was attending his workshop but i still was not convinced by SMACSS and BEM as I perceive them as an overkill in their pure version. I love the concepts (and use most of) but i cannot buy it as a whole. That is probably a matter of preference.

Damian Dulisz Nice! Was it worth?
Well, that's why I hardly go pure BEM or SMACSS. Taking what works for you, skipping the redundancy. It is all a matter of personal preference and your needs. For small projects that's completely overkill. However the ideas behind those philosophies solve lots of problems when you have to deal with large codebase. Even more if you work in a team and the code is supposed to work for next ~4 years or so. Remember the last time you jumped inside some big legacy code!