Third-party scripts are probably the #1 cause of poor performance and bad UX on the web.
Training a neural network to do front-end development.
I didn’t understand any of this.
Suggestions for small interface tweaks.
Slides from a conference talk with a really clear explanation of how
await works with promises.
Ooh, this is clever! Scott shows how you can use
And the whole thing is available here for free under a Creative Commons licence!
I like this distinction between coders and developers.
The Coder is characterized by his proficiency in a narrow range of chosen skills.
By contrast the Developer’s single greatest skill is in being an applied learner.
I’m definitely not a coder. Alas, by this criterion, I’m also not a developer (because I do not pick things up fast):
Quite simply the Developer has a knack for grokking new [languages|frameworks|platforms] and becoming proficient very quickly.
I prefer Charlie’s framing. It’s not about speed, it’s about priorities:
I’m not a “developer” in that I’m obsessed with code and frameworks. I’m a “developer” as in I develop the users experience for the better.
Data visualisations created for The Times, complete with code.
Before reading this article, I didn’t understand regular expressions. But now, having read this article, I don’t understand regular expressions and I don’t understand linguistics. Progress!
This is clever—you can use the
navigator.connection API from a service worker (because it’s asynchronous) which means you can have a service worker script that serves differently sized images based on bandwidth.
In the immortal words of Ultravox,
this means nothing to me.
I’m filing this away for my future self for the next time I (inevitably) get confused about what
Great advice on writing sensible comments in your code.
A really great case study of a code refactor by Mina, with particular emphasis on the benefits of CSS Grid, fluid typography, and accessibility.
Good advice on writing code that is understandable to your fellow humans (and your future self).