The article addresses some valid issues, but tackles some of them in a manner which is likely to affect maintenance in a different, and not always positive, way.
The article illustrates LESS and Sass in a sort of magic bullet fashion, but the reality is that such pre-processors are likely to cause many side effects and unwanted behaviour when coming back to maintain a site when used in the fashion suggested.
The author complains about the cascade and such issues, instead of embracing those same features and utilising them to their power.
I've written an article covering methods for writing scalable CSS utilising the cascade, preprocessors, and practices I have found invaluable in assisting with scalable sites / apps:
