Weekly Links: March 24th
#SmooshGate FAQ | Mathias Bynens - A great explanation both of the background behind the recent twitter controversy over
Array.prototype.smoosh as well as the TC39 process generally.
js-classes-1.1 | Allen Wirfs-Brock - This is the new proposal for expanding JS classes I mentioned in my post last Friday. It aims to be a more minimalist take on expanding class capabilities (primarily adding private state syntax) than other proposals that have come along over the last few years.
Computer Science and Software Engineering
basecs | Vaidehi Joshi - While I’ve been starting to consider how to explain CS concepts for front end developers without a CS background, I found this excellent beginner set of CS articles written by Vaidehi Joshi on Medium over the past year. Worth diving into, especially if you like fun visuals.
The 3 Skills That Helped Me Become a Better Software Engineer | Victor Savkin - This is worth sharing solely for the advice about mental models. In my experience the ability to think in abstractions (and understand when you need to dig deeper) is one of the biggest hurdles in programming when trying to grow from a beginner to a more advanced software engineer.
I’ve been working through a goal to read 30 books in a year, and have worked through a few more books recently. Here are two good ones.
The Martian | Andy Weir - Yes I know I’m 3 years late on this one. But I’m sure there are other lost souls like me who entered 2018 without reading this book. If you love tech and science (and I’m guessing you do if you’re reading this), you should find a way to read The Martian. My first thought when I started reading it was “This is great”. My second thought was “How in the world did this end up becoming a Hollywood Blockbuster starring Matt Damon?“. The Martian is unapologetically geeky, and it is “real science” fiction, with a very human core. I loved it.
Death By Meeting | Patrick Lencioni - This was a recommendation from my manager, and is a great read for anyone who wants to improve the meetings they’re in at work. It’s written in a “business fable” style, with a story serving to illustrate the principles it is trying to teach. One thing I love is that it tells the story of the principles being implemented from a lower rung employee, rather than a top-down executive driven approach, so hopefully it can be inspirational to you even if you feel like you wouldn’t be able to change your meeting culture even if you knew what to do.