- #YOU DONT KNOW JS THIS AND OBJECT PROTOTYPES CODE#
- #YOU DONT KNOW JS THIS AND OBJECT PROTOTYPES SERIES#
So every interviewer expects you know the basics of Objects. So this is a gist of some of the questions and concepts that i have came across in my interview for some product based startups.īasics of javascript should be clear very much, Things like arrays, objects, variables etc should be very clear before even you think of applying at any job as a js dev.Īrrays are very important and since you will be using them so much in your day to day use case as being a web dev you should definitely learn all the things that can be done in js for arrays likeĪlso you should learn how we iterate over arraysĮvery developer in his day to day life will definitely come across objects while working on a javascript project. Not is it just awesome but also by just learning and understanding javascript you will be able to learn and use so many great frameworks that are buzzing in current job market Overall, the books are amazing and mind opening, and I highly recommend them.Javascipt is a great language and i believe every web developer in todays world should definitely learn it. It goes through all of the tricks and gotchas of ES6 and as usual Kyle’s way of explanation is very clear and straightforward. I consider this book to be the most important one in the You don’t know JS series, especially for those who have some experience and have been working with Javascript for years. Finally, he gives some overview of assessing performance and benchmarking. He lays down the differences between concurrency, serialism and parallelism and then use those differences to explain the JS Event loop and then goes into the technicalities of implementation using callbacks, promises, and generators. Kyle has a unique way of explaining deep technical CS concepts in a simple and straightforward manner. Async & PerformanceĪmazing book if you want to understand how asynchronicity in JavaScript works.
#YOU DONT KNOW JS THIS AND OBJECT PROTOTYPES CODE#
However, he lays down some strong arguments against writing JS code in traditional OOP style, which ignore or “hide” the dynamic nature of the language and try to tame it into a static one. The fact that he wants each object to have it’s unique method names and prohibits overriding at all is beyond me, it makes code more complex, less intuitive and also doesn’t make it any easier for new engineers to work with an already existing codebase. I have my reservations on the pattern and how readable it’s syntax is. Kyle in the last chapter proposes his own design pattern OLOO (Objects Linked to Other Objects) which aims to solve many of the issues of trying to code JS in an traditional OO pattern. It gives you a general understanding of how objects are created and how behavior is executed or rather “delegated” in JS. The book explains the deep quirks and gotchas of the dynamic nature of JavaScript embodied in the ] concept. I gave it 5 stars because Kyle’s explanations and examples are amazing even if the material itself is dull.
#YOU DONT KNOW JS THIS AND OBJECT PROTOTYPES SERIES#
This book is not as interesting or intriguing as other books in the series because it goes through the basic stuff then it’s basically a list of Gotchas and quirks in the language logic. Kyle Simpson has a unique way in explaining complex CS concepts and ideas in simple words. From syntax gotchas and quirks to how coercion works to asynchronicity (or the illusion of asynchronicity). I think this series is essential for anyone who want to dive deep into Javascript. It took me almost 4 months to get through the 6 books, and I will definitely go back to reread certain parts of it. Just finished You don’t Know JS series by Kyle Simpson.