3 ms·

The best point in this article is that you need to take your CSS seriously and treat it as an equal to any other piece of code. A common practice in companies i

The best point in this article is that you need to take your CSS seriously and treat it as an equal to any other piece of code. A common practice in companies is to rigorously code review application code while basically giving CSS a pass. Obviously your CSS might be less important than core business logic, but just ignoring any sort of practices will make developing new features take longer and less efficiently. It will also come back to haunt you at some point. A key metric of any company is how fast you can develop new features while keeping quality, consistency and reliability. Following good CSS practices will only help out that cause.

mattacular 13y ago
In terms of developer time spent, working out thoughtfully organized and tidy stylesheets up front can save a lot in the long term (just like with any other part of the codebase). Maintaining and adding to stylesheets is difficult: they almost always (and quickly) devolve into the CSS equivalent of spaghetti code, especially on teams where you have multiple people working on them. The 'easy/fast' approach at that point is to just create a new style rule and re-class the majority of the elements you're trying to affect and it is just a vicious cycle.