Can you write “wrong” CSS? You regularly find someone who argues yes, by either saying what you have to do or by saying what you must not do. For example, peers have argued to use resets , not to use !important , not to use shorthands , not to use certain selectors , only to use logical properties , &c. Others have suggested that you cannot write “wrong CSS.” Personally, for the examples given , I have . Why can’t you write wrong CSS? I submit four reasons. (Comment on the socials if you believe there are more—or that I err!) 1. If It Works, It Works If there’s no concrete practical disadvantage to it—like significantly worse UX or concretely experienced worse DX—, there’s no reason to change something that’s working. CSS is not occupational therapy. Furthermore, the web platform rarely if ever deprecates anything, and instead emphasizes backwards-compatibility. This means that the code is safe.…