A few problems with this: 1. I'm not sure "internal" vs. "external" is the right dividing line. I've worked for start-ups where doing something scrappy with ou

A few problems with this: 1. I'm not sure "internal" vs. "external" is the right dividing line. I've worked for start-ups where doing something scrappy with our external look-and-feel was fine, and on the other hand my previous project was an "internal" tool that had thousands of internal users, which demanded a higher quality. 2. I've seen cases where internal standards slow things down, but I've also seen cases where internal standards speed things up. Yes, if you have to do the same amount of work every time to maintain a high bar, that would slow down CSS work. But we would never say that about bugs in logic, instead we'd say "Use the foo function that so-and-so wrote" and. The problem isn't the standards themselves, it's what corners are cut to achieve them. A "high standard" CSS can help remove friction by helping developers avoid thinking about things that are irrelevant to the task assigned, leading to a more sustainable overall design (see https://www.martinfowler.com/bliki/DesignStaminaHypothesis.html https://www.martinfowler.com/bliki/DesignStaminaHypothesis.h...). 2a. To be more specific about the last point, having a clear design language (we are allowed to use these font sizes and no others; we are allowed to have buttons that look like this one, that one, or the other one; we have to use these colors) forces constraints on developers that can make the overall code base easier to understand and maintain. The constraints remove the possibility of engineers who aren't all that strong in designing user interactions from designing something confusing or buggy. 3. I don't know what this "beforetime" is. I've been working in the industry since 2008. That was three years before Bootstrap's first release which the article mentions as some epochal dividing line. During the entirety of my career, CSS has always been a technology that many developers just don't want to deal with. The only change has been that now a team has 1 person (or maybe 2 people) who are good at writing new CSS definitions on top of a pre-existing CSS framework, whereas before a team had 1 person (or maybe 2 people) who made all the CSS definitions from scratch.