I don’t know JS
So far I’ve learnt to code through bootcamps, workshops, study groups, online videos, podcasts, meet-ups, mentors, teammates, Stack Overflow… the list goes on. It includes just about every learning resource out there, except for books.
I recently had dinner with a girlfriend who is a back end engineer at Deliveroo. On her bookshelf sat a big, fat book about Java. I asked her if she’d read it and she said yes. “The entire book?” I gasped. “Every page,” she said. I felt a pang of guilt. So that’s how you go deep on a language, I thought to myself.
So I asked my Twitter followers for the latest and greatest resources:
Then I put everyone’s suggestions into a Gist:
The one that stood out to me was You Don’t Know JS, a six-book series by Kyle Simpson.
In the preface, it says:
Here, we address head on the tendency of JS developers to learn “just enough” to get by, without ever forcing themselves to learn exactly how and why the language behaves the way it does…
When developers encounter confusion, they usually blame the language instead of their lack of understanding. These books aim to fix that, inspiring a strong appreciation for the language you can now, and should, deeply know.
I’ve made it my goal to read at least two of these books, from start to finish, by the end of September.
I’ll be blogging my learnings from the first book here.
I’ve gone through various stages in my learning — all of which have led me to where I am today.
In 2015 I coded Hangman from scratch. This felt like a huge achievement. I’d now reached a stage where I could hack together a game that worked (despite a few bugs). Later that year I started learning React and React Native, and built a series of mini projects with them.
Now it’s 2017. I’m in my first front end engineering job. I understand the ES6 arrow function, maps and filters. I understand .bind(), .call() and .apply(). I understand RxJS observables (sort of). I’ve started learning Redux. I’m getting better at writing unit tests.
Wish me luck!