Web Dev. Reading List #125

About The Author

Anselm is a freelance front-end developer who cares about sustainable front-end experiences and ethical choices in life. He writes the WDRL, and is co-founder … More about Anselm ↬

Email Newsletter

Weekly tips on front-end & UX.
Trusted by 200,000+ folks.

What’s going on in the industry? What new techniques have emerged recently? Anselm Hannemann is collecting everything that popped up over the last week in his web development reading list so that you don’t miss out on anything. The result is a carefully curated list of articles and resources that are worth taking a closer look at.

It’s Friday again, and I found some interesting articles for you to read over the upcoming weekend. In projects, developer, manager and product leaders still try to put pressure on the people who work on a task. Somehow they feel relieved, more secure if they do that. On the other hand, the people experiencing the pressure of urgency are struggling massively with it.

The fallacy here is that while the ones spreading the pressure feel better, the people experiencing it usually do a worse job than without the pressure. It leads to more bugs, unstructured work and, in the end, all people involved will suffer from the result. So instead, a team, which includes everyone from a developer to a manager, should focus on the purpose of the work. Give it a try, y’all, and now, enjoy your weekend!



GitHub templates
GitHub’s new Issue and Pull Requests templates help contributors add the right details at the start of a thread.


  • A bug in glibc has been disclosed. As it’s a very bad and easy to exploit bug, you should patch every server (and clients) as soon as possible.
  • Never say “We’ll just use defaults, for now. That password will do, for now.” in the context of security. It’ll be forgotten, and this is the most dangerous threat to your data, giving attackers the possibility to do anything with very little effort. Do you have a VoIP phone with a default password? A WiFi router? Change it to something secure. And please tell your friends and family as well. This is important.


  • This week, Apple started a new discussion about privacy, encryption and built-in backdoors on their devices. They received an order to build a custom iOS built, signed by Apple, that lacks several security measurements so that the FBI could hack into phone data relatively easily. In an open letter Apple shared why they declined to do so. Luckily, a lot of companies seem to agree with Apple, and I hope we can find a good way to protect our privacy, and with that, our personal security. Because, as we all know, even if such a backdoor is kept secure, no one could assure that this piece of software won’t get stolen and abused by someone who shouldn’t have access to it.

Web Performance

  • Rachel Andrew wrote a great guide on how you should start to make a plan for the transition of web projects to HTTP/2. As the switch should be well planned, it’s a great idea to establish a process to migrate seamlessly and, for now, generate assets and pipelines for both, HTTP/1.1 and HTTP/2, so that a switch is easy.


  • So, this is nothing ground-breaking but if you ever wondered about a good cross-browser way to check if the document has loaded in pure JavaScript, this code snippet is for you.
  • The still relatively new ESLint has been released in version 2.0. It breaks at some point with v1.x but now comes with an auto configuration feature and also introduces code path analysis.
  • Hunt by Jeremias Menichelli is a JavaScript library that detects if an element becomes visible/invisible and acts on these events, by adding or removing classes, for example. This makes it a great tool to animate elements on scrolling and other interactions.

CSS / Sass

Responsive containers in Gmail
The Fab Four technique lets you create responsive emails without media queries.

Work & Life

Going Beyond…

  • Last week, I wrote that most of the time the software we write is not critical to people. But what happens if it is? For example, if you sell a smart thermostat and due to a bug in its software the heating is disabled entirely with no option to fix it yourself? This happened to Nest users, showing the problems of ‘smart’ devices that control critical things in our lives.

And with that, I’ll close for this week. If you like what I write each week, please support me with a donation or share this resource with other people. You can learn more about the costs of the project here. It’s available via E-Mail, RSS and online.

Thanks and all the best, Anselm

Further Reading

Smashing Editorial (mrn)