<i>&gt;Though its the most ugly, I&#x27;m a fan of the original B__E--M</i><p>I feel this is something people need to learn to look past - because I agree <i>entirely</i>. It looks terrible. Absolutely terrible. Names get long (but yay for autocompleters!) - but everything is readable. CSS shouldn&#x27;t be aesthetic. It should be legible. Maintaining something you can&#x27;t read is hell - every programmer knows this.<p>I also make use of prefixes to namespace. Which makes my classes even longer. [0]<p>But there is absolutely <i>no</i> question what my code is doing when I read the HTML. I know exactly where changes need to be made. My coworkers are familiar enough with my style that <i>they</i> know what code is safe to change and what code will have side effects. They&#x27;re slowly adopting the style - although it&#x27;s almost a 180 from the old style of &quot;be as specific as possible so you don&#x27;t accidentally break something someone else had worked on 8 months ago&quot;. (#NotEvenKidding .our .selectors .are &gt; .like .this)<p>[0] <a href="http:&#x2F;&#x2F;csswizardry.com&#x2F;2015&#x2F;03&#x2F;more-transparent-ui-code-with-namespaces&#x2F;" rel="nofollow">http:&#x2F;&#x2F;csswizardry.com&#x2F;2015&#x2F;03&#x2F;more-transparent-ui-code-with...</a>