3 ms·
This is really bad advice. You reduce errors by reducing code by wrapping your code in functions, thats functional and its how classes work. This article sugge
by dangerface 8y ago
This is really bad advice.
You reduce errors by reducing code by wrapping your code in functions, thats functional and its how classes work. This article suggests the opposite just write everything from scratch perfectly, not going to happen.
> there's nothing stopping you from continuing to add those semantic classes, even if they're irrelevant for styling
If they are irrelevant to style then it could be applied to anything, it has no meaning and is not semantic.
They don't know what separation of concerns is, or why its a good thing.
>when you get into a situation where one of the buttons needs to have slightly more margin-top than the others
Yea just break your designs consistency im sure your users will love that.
- ArchTypical 8y agoI tried this at one company. I have never gone back. It's terrible advice? You can only reconcile this as a matter of experience.
- dangerface 8y ago> You can only reconcile this as a matter of experience. I was able to give three common and specific reasons why its bad advice, none of them where to just trust me, or my experience. If the only reason you like something is because you like it, fair enough, good for you, you like a thing. Its ok to like things, but that doesn't mean there is any solid logic backing the things you like.