September 23, 2018
Mariko Kosaka wrote an amazing 4-part series about how browsers work, chock-full of helpful illustrations. If you’ve ever wondered about the gritty details of how your web browser is able to turn all those 0s and 1s into text and images, you have to give this series a look.
Along similar lines, over at CSS-Tricks the always eloquent Rachel Nabors published The Ecological Impact of Browser Diversity. A lot of developers see a wide-variety of browsers as some sort of plague (“Argh, why do I have to support all these browsers?”) but actually some competition in the browser marketplace is healthy and better for everyone in the long run.
For React devs, be sure to read the React team’s guide to optimizing performance. It’s a great way to step up your game and includes links to a variety of helpful libraries and tutorials.
I generally avoid acronyms at work — they’re exclusionary, easy to mix up, unfriendly to dyslexics, the list goes on. It’s easy to confuse concision with precision. Over on Twitter, Dan Abaramov threw some shade at the “Stateless Functional Components” SFC acronym. After all, SFC could just as well stand for “Stateful Functional Components”.
Bob “Clean Code” Martin wrote this Platonic dialogue on unit test contra-variance late last year and I’m still digesting its implications. The immediate upshot, however, is that I’m looking at unit tests from a completely different angle than I used to. Any unit test that too closely mirrors the code it’s testing is ripe for a refactor.