Article Roundup - Week of Jun 03, 2018 DRY to the point of WET yak shaving DRY is a great principle, but it is just that: a principle. This article does a good job of going through that, though with a few too many images. If you get to nothing else, read the quote from Dave Thomas near the end. yak shaving: Any apparently useless activity which, by allowing you to overcome intermediate difficulties, allows you to solve a larger problem.
CSS Grid Builder This is a very cool tool that makes building CSS grids super easy. Tips for High Availability – Netflix Technology Blog – Medium When it comes to high availablity you know Netflix knows what they are talking about. If you have been a subscriber long enough you’ll know they have always been pretty good, but have gotten even better in recent years. This article goes through some tips from Netflix.
In most cases, you can assume one character in a string is 1 byte, but that is only in most cases. How many bytes do you think ü is? It turns out it is 2 bytes. But if you run 'ü'.length it will return the string’s length as 1. Unicode characters can appear as a single character but be made up of multiple bytes of data. Usually, this isn’t a big deal if you just need the length of a string, but if you actually need the size in bytes of a string it is a big deal.
The Eponymous Laws of Tech This is just a fun collection of all those laws and such things you find used in tech frequently. Occam’s Razor, Godwin’s Law, Brooks’ Law, those kinds of things. CloudEvents There isn’t a consistent model for events in serverless and cloud computing. Amazon’s SQS events are described one way, Google’s Pub/Sub events another. Kafka has a different format. CloudEvents is an effort to create a spec to be submitted to the Cloud Native Computing Foundation (CNCF).
Testing Strategies for React and Redux Mozilla recently ported the Firefox extensions and themes website to React and Redux. This article goes through how they do much of their unit testing. Dividing frontend from backend is an antipattern Frontend development isn’t what it used to be. It has grown a lot in the last 10 years and now accomplishes things that wouldn’t have been considered possible. It’s time to reevaluate how we think about the frontend and the backend.
A nice feature of tools like create-react-app, angular-cli, webpack, and many others is the ability to reload your application when you make a change to a source file. But what do you do when you have a Node backend to go along with your frontend? There are numerous tools you can use to detect changes to files and then restart a process based on that, but who has time to build those scripts to put it all together?