Nov 11th 2015
My hand would have definitely stayed down. If I have a problem that I'm scratching my head about, my usual course of action is to jump on Google and wade through blog posts, tutorials and StackOverflow answer threads till I stumble across a solution that appears the most 'right'. It's painful to admit that going to the spec (up till now) never even entered my head.
This is even despite being a fan of Getify's books, books that actively encourage you to not take things for granted and try to look closely at what is actually going on in the language. I suppose I had to actually hear him say it for it to really sink in.
The rules by which they do this are complicated and unmemorable.
Getify's rebuttal to the issue of complicated rules is pretty spot on:
I believe this is a flawed premise -- that you readers are competent developers who write (and read and understand!) algorithms (aka code) all day long.
So I went and looked at the spec, and to quote DC out of context:
In that moment, I achieved enlightenment.
I didn't find the rules to be that complicated (and I'm a n00b). He might be right about them being unmemorable, but we are talking about a context in which we are almost inevitably connected to the web as we work. The spec is not much more than a bookmark away (especially now I've bookmarked it).
I found that reading the specification, in order to deepen my knowledge and understanding, to be hugely empowering (even just on this one issue). I've noticed that the people that inspire me the most when it comes to web development, people like Sara Souiedan, Kyle Simpson, PPK (to name just three, there are obviously many more) are the people that have obviously taken the time to dig deep into a subject.
Am I going to throw
Kyle Simpson on Hanselminutes
You Don't Know JS