One common theme popping up in projects is that change is the only constant. Code changes, architecture changes, technology changes, requirements change and people change. But often, change comes at a high cost. Things were just not prepared for change because doing so would have imposed the costs earlier on. But really the same costs? To reduce costs in the long run, wouldn’t it be beneficial to spend some effort in changeability upfront? Of course, but it is difficult to find the sweet spot between spending enough and too much effort to properly implement changeability.

If you are like most programmers, you don’t think of CSS as a programming language. It’s a description language, it describes the look of elements on a website. While developing your next super-cool web application you describe the visuals using CSS and it feels like you are writing a book instead of an application, losing sight of all the CSS as you keep developing.

If you have already written CSS you most probably have…