If you’ve read my first two posts, you already know that I prefer reading to watching videos when it comes to learning stuff, so this may come as a surprise to you all, but I’ve made an instructional video.
As I’ve been working through various JavaScript tutorials, a recurring issue has been that stuff is sometimes being done in an order that didn’t initially make sense to me with my C++ background.
When I asked about the oddities I was seeing, I was told that the asynchronous nature of JavaScript was the cause of everything.
If there is one thing that more than 10 years of accounting has taught me, it is that more often than not it’s the stuff that you just think you understand that really trips you up in the biggest ways, so I set up to understand the asynchronous nature of JavaScript well enough that I would be less likely to have it come back to bite me later on.
As chance would happen, shortly after I started to get a decent handle on which parts of JavaScript were synchronous and which parts were asynchronous, we ended up needing some content for one of our weekly development lunches. Being generally willing to pitch in when the need arises, I offered to explain my findings to the development team.
When I shared what I’d learned with some of my co-workers, they were really positive–both about the quality of the information, and the way that I’d presented it. So much so, that they convinced me that I needed to turn my presentation into a video and upload it to YouTube.
It’s taken significantly longer than I was expecting to it, and there was a much bigger learning curve than I was prepared for on something that was just supposed to be a quick side project, but it’s done, and if you’ve ever wanted to have a better understanding of how JavaScript handles asynchronicity, this is the video for you.
Here’s Dean’s first JavaScript Video
Here’s the slides that I used to create the video
Here’s the transcript of the video
I would love to have you link all three of these items around to anyone that you think might benefit from the information–just please leave the links back to WritingCode.net in place so that I get credit for my efforts.