There are few satisfactions in life greater than finding a more efficient way to do something in vi. But if you’re me you can’t just read a vi book. You have to read tutorials like this over and over until a new shortcut for moving, cutting, or pasting text just sticks. This is a good tutorial for ambient skill acquisition.
These security and perfomance changes for websites are easy to add and include some new browser features I wasn't aware of before. I went with the recommendation here for a simple CSP header but it looks like you could really batten down the https hatches with that one if you read through the spec.
Webster’s Dictionary defines serverless as—well, it doesn’t define it yet. But I like Postlight’s take on it here. I’m also a fan of Airtable which does structured data and media entry well. With some light glue in Node.js form, you can present that data and media with HTML & CSS. I could see using this when you don’t need the overhead of running WordPress but you want some structure around how you enter content. Neat idea! In conclusion, serverless structure still requires servers.
Justin Kosslyn is addressing global security concerns at Google and here he argues that friction can be a positive force in technology. We tend to think of friction as something that should be removed from every aspect of our lives. (e.g. If we could only do our banking transactions faster than we could spend more time doing what we want.) Kosslyn argues, "It’s time to bring friction back. Friction buys time, and time reduces systemic risk. A disease cannot become an epidemic if patients are cured more quickly than the illness spreads." Ezra Klein at Vox ties this idea to the success of podcasting in The case for slowing everything down a bit: "I believe that one reason podcasts have exploded is that they carry so much friction: They’re long and messy, they often take weeks or months to produce, they’re hard to clip and share and skim — and as a result, they’re calmer, more human, more judicious, less crazy-making." Meanwhile, Farhad Manjoo signs off of his NYT technology column with a similar sentiment in How to Survive the Next Era of Tech (Slow Down and Be Mindful): "Adopt late. Slow down."
The headline is a little alarmist, but this is a great explanation of some bitcoin scam code that someone placed into a popular node package. I agree that building businesses on top of volunteers is not sustainable and I hope the Node community can work on a solution. Reusing community code is a fast way to develop but you trade away some security.
Have you ever been sitting there staring at an Excel spreadsheet thinking, "If I could just run a SQL query I'd have my answer." And then you have to export to CSV, import the thing into MySQL, and waste an hour figuring out why your import is failing. Anyway, this tool solves that particular problem nicely.
“The data we are shown is not the only data there is.” A good description of a statistical analysis problem and a reminder to think about causes of data not just data you see in front of you. This reminds me of that old zen saying don’t confuse the moon with the finger that points at it.
Welcome to Newsletter Wednesday! (I just made that up so it's a thing now.) Sidebar shares five daily links about web design and it's a good one to subscribe to via email. I've recently been diving down a microcopybestpracticesrabbit hole and I'm blaming Sidebar for that.