The title of this blog post explains the question that I’m posing. I would love to get some feedback on this as well. Does using a CSS preprocessor like LESS or Sass actually create less maintainable code in a collaborative sense?
So here me out. I’m currently working on a WordPress theme and an ExpressionEngine site. Both of these will be turned over to the client at the conclusion of the project for maintenance and updates. I’ve been a big fan of Sass in particular since Eddie Machado converted me over from LESS, but the fact of the matter is that many people tend to edit CSS in the ‘old fashioned’ way, whether that be through the WordPress editor screen, straight HTML or any other method.

From the Smashing Magazine post “An Introduction To LESS, And Comparison To Sass
However, if I’ve written everything in Sass or LESS, turned the files over to the client and they go in to edit stuff, either they don’t know how to compile LESS or Sass (or don’t care anything about it) or simply make their changes in the CSS the old fashioned way. Now you have a discrepancy between the LESS/Sass files and the compiled or resulted CSS. What do you do?
One solution is to include the less.js script, however that comes at a steep performance hit and not at all optimum.
So then, if you’re working on a client project where you know you’ll be turning over the code, do you still use a preprocessor? Do you include ‘directions’ or ‘instructions’ on what the preprocessor is and does? Or do you not worry about it and just make sure the final product is what you’ve been contracted to do.
Would love to hear some of your thoughts in the comments.