There is a very simple way to maintain DRY code with psuedo elements, specifically with the content of those elements. You don't have to make new classes: just use attr().
Yesterday I was attempting to add a silent autoplaying video to an element and kept running into issues where the video would sit on the first frame and wouldn't actually play the video.
Sometime last year I found myself getting annoyed with how we were using PHP's echo to inject a single string into our WordPress HTML. It felt far too verbose and cluttery. Fortunately, there's a neat solution.
A while ago I was trying to figure out how to write my own pseudo-classes in CSS and couldn't figure out how to make it work, until I stumbled across this stupid easy trick to write remarkably clear utility classes.
Recently I decided to get back into blogging, which you probably figured out by visiting the site. It's a simple setup, but it does one thing really well: it stops me from overthinking.
You don't want to be the person who regrets not doing it sooner.
Yesterday I had one of those days when my life seemed to flash before my eyes. I was staring at my branch's logs, wondering why all of the previous day's work was nowhere to be found.
It's fairly easy to add updates to your code to solve an issue. It's easy to get a directive from a director or project leader or even a request from a teammate and simply execute it. The challenge comes in looking at problems from a standpoint of future proofing.