4 ms·
> Name them for what they are. I've kept hearing (and believing) this for 20 years but never seen a project where it's actually enforced. It seems like one of
by Kiro 2y ago
> Name them for what they are.
I've kept hearing (and believing) this for 20 years but never seen a project where it's actually enforced. It seems like one of those things that doesn't work in practice and that come with very few benefits compared to the overhead it creates. Every time I redesign something I throw out both HTML and CSS anyway.
- isleyaardvark 2y agoWhenever I have seen code like that, it’s awful. “Name them what they are” becomes “name them after their content”, which is the opposite of separation of concerns.