/blog/links

Written and published by Martin Wolf

The Importance of !important: Forcing Immutability in CSS →

Harry Roberts:

Resilient and defensive systems are not designed for the perfect world, they’re designed for the real world, and in the real world, people write sloppy CSS. Using !important to force immutability will safeguard us from collisions and conflicts that others may introduce.

Harry Roberts explains when it is okay or actually recommended to use !important.

BEMantic: DRY Like You Mean It →

Matt Stow:

I don’t understand why BEM and HTML semantics are seen as mutually exclusive. I like to think I’m a good developer; I take great pride in the HTML I write (both the semantics and ARIA attributes) and in my CSS, which utilises both Sass and BEM.

A Must Read.

CSS @apply rule (native CSS mixins) →

Even though I can't see myself going away from SCSS completely anytime soon, it's very good to see what's happening in the native CSS space. Maybe we can ditch at least a few things and use their native implementations in the (near) future. That would be nice.

Building remote-first teams →

Karolina Szczur:

Countless excuses can be made to disfavour remote work, and truth be told there are definitely scenarios and industries in which it couldn’t be effective and plausible. Let’s have a look at why, in the tech world, most of them can go straight to the trashcan.

Excellent article about all things remote.

Meaningful CSS: Style Like You Mean It →

Tim Baxter:

Our systems for safely building complex, reusable components created a metastasizing classitis problem—to the point where our markup today is too often written in the service of our CSS, instead of the other way around.

I don't agree with the points made in this article regarding CSS selectors, but I think if you write CSS for a living you should read the article anyway and think about your own approach. That's never bad.

I don't see why I shouldn't be able to write semantic, meaningful markup and also use OOCSS, BEM, ITCSS, SMACSS, etc.

What I definitely do take away from this is, that I need to pay closer attention to ARIA roles and microformats.

Interview with Håkon Wium Lie →

Oliver Lindberg:

Lie himself, however, will be taking less of a lead — over the next 20 years he plans to take a step back. Although he will be keeping a close eye on what goes on, and he’s hoping that the next generation will continue to work on CSS. “I don’t want people saying: ‘Let’s throw out HTML and get some new platform’,” he asserts. “Especially if it comes from a commercial company. That’s the worst thing that can happen, if we end up in a monopoly situation.

Being a Developer After 40 →

Adrian Kosmaczewski:

I have often pondered about leaving the profession altogether. But somehow, code always calls me back after a while. I like to write apps, systems, software. To avoid burning out, I have had to develop strategies.

In this talk I will give you my secrets, so that you too can reach the glorious age of 40 as an experienced developer, willing to continue in this profession.

CSS containment →

Michael Scharnagl:

[...] contain: strict; can avoid many of the problems of container queries. One of the “problems” of container queries is that the children and their content can have an effect on the size of the container. This can be avoided by using CSS containment.

Oh boy, contain will be a very powerful property once we can reliably use it in production.