I never played "You Don't Know Jack", and so I tend to interpret your title literally. Nope, it still doesn't work for me, personally. I'm just trying to provide resources for developers who want to take learning JS seriously, and challenge "all" of us to ask, "just how much DO I know JS?" The rest is up to you.
#What you dont know js code
If you aren't really sure exactly why your code works, my theory is that you'll never know exactly why your code doesn't work either. I have found that approach to be good at getting and keeping yourself employed, but bad at giving you any confidence that you actually know what's going on. Most developers in most other languages do tend to take formal learning of the language, to a deep extent often, a more serious task, but with JS it seems many developers just kinda get whatever they get along the way. If you're going to make JS your primary language that you write on a daily basis, doesn't it make sense to invest more time into learning it than just whatever you might accidentally pick up through trial-and-error? The proposition that I approach JS from, including my writing of these books, the JS workshops I teach, my OSS work, etc, is this: It's a shame you apparently didn't read the content/previews before buying, you could have saved your $5-7 (at least it wasn't $35-50)."
#What you dont know js for free
One last comment: these books are all available fully for free to read here: In addition, Amazon's site makes preview snippets of the book available to read for free so you can get an idea of what you're buying.
#What you dont know js series
The spirit of the whole series (given the title) is to get us all (myself included) to admit how we don't fully know JS and how we need to dig deeper than we have before.
If you're already a JS expert (even on all the new ES6 stuff coming), then you probably do know JS and I'm not sure why you bought the book. But I feel quite certain there's a lot of content in there (like block scoping, etc) that most developers (and perhaps even you) aren't fully aware of. With regards to this content being "pointless", that seems quite a spurious and unsubstantiated claim. Rather than being about me greedily making more money, it rather downgrades my ability to make bigger chunks of money per copy for the majority of people who (like me) only want/need part of the content. This places you, the reader, more in control, not only of what you buy and own, but more deeply of what you spend your money on compared to the content you get. This COULD quite likely mean that I make a lot less money in the overall picture, because there will be plenty of people who don't buy all the books, or even not enough of them that would have generated the same income as a single book would have. I decided when I wrote this content that I'd make each logical chunk of content available separately, which means that you can buy only the stuff that you actually care about. One of the things I hate the most about tech books is that I spend $35-50 on a big book of which there's only a few chapters I actually care about. I can assure you, my goal of splitting up the content into a book series had ZERO to do with making more money. I posted this link after having read the author's comment to a one star review on Amazon:
0 kommentar(er)
