A developer never sets out with the goal of making a complete and total mess of things.
In some ways it’s a bit of a “me too!” post about how to organize your stylesheets (e.g., somewhat more opinionated than SMACSS, a lot more opinionated than OOCSS) but still worth the read, even if you’re feeling burned out on this kind of advice. Sande’s proposal is to take a bottom-up/inside-out approach to engineering your (S)CSS and to organizing your directories and files. The key take-aways for me were: (1) the opinionated directory structure and (2) treating `style.scss` as a manifest for everything else. (Though the second item is hardly a new idea, talking about it as a “manifest” is certainly an elegant expression of that idea.)
There are still some unsolved problems here, but they’re mostly social. (“How do I create the right traction for this work in a big organization? and/or reduce the friction for working within a big application?”)
There’s also a nice slide deck that goes along with it.