You dont know js hoisting code#
You dont know js hoisting series#

You dont know js hoisting series#

Quite a few sections in this chapter seemed very incomplete, and had me going вЂњWait what?вЂќ, but the chapter was peppered with suggestions that I refer to the other parts of this series for a deeper understanding of the concepts explained. The second chapter was called вЂњInto JavaScriptвЂќ, which introduced a few JavaScript concepts. But I remember thinking about this when I was programming on an 8086 in college: the syntax for a move is mov ax, 10h, which means move the value 10h to the register ax, and I wonder if syntax like mov 10h, ax makes it more understandable (to me). IвЂ™m used to syntax like a = 10, because I read it as вЂњ a equals 10вЂќ.

He says using a different syntax, say, 10 -> a is better to indicate that the value 10 is assigned to the variable a. The author says this could be confusing or non-intuitive for people who are new to programming. When we write, say, a = 10, we mean, assign the value 10 to the variable a. My favourite part of this chapter was a discussion about the assignment operator. I couldвЂ™ve skipped this, because it introduced programming concepts that IвЂ™m already familiar with. The first chapter is called вЂњInto ProgrammingвЂќ. ItвЂ™s about the specific core parts of JavaScript that are most misunderstood and not understood well enough. The book is about understanding all parts of JavaScript, and learning how and why JavaScript behaves the way it does. If at every point that you encounter a surprise or frustration in JavaScript, your response is to add it to the blacklist, as some are accustomed to doing, you soon will be relegated to a hollow shell of the richness of JavaScript. JavaScript is called a weird language and is вЂmemeвЂ™d about a lot, and we do tend to stay within the вЂњsafeвЂќ parts of JavaScript. The preface describes the general tendency of JavaScript developers to learn just enough JavaScript to get by and consider the rest of it вЂњweird JS behaviourвЂќ. So when a colleague told me about this series of books called вЂњYou DonвЂ™t Know JSвЂќ by Kyle Simpson (getify) I was like, well, I actually donвЂ™t know JS, and it sounds like a great idea to read this series!

I was okay with trying despite not knowing any React or JavaScript, because, why not! I learnt React from the ReactJS docs, and the ReactJS docs recommended MDNвЂ™s вЂњ A reintroduction to JavaScriptвЂќ, and thatвЂ™s as much JavaScript I learnt! When I started working at Orangescape, my manager asked me if IвЂ™d be okay with working on the front end.

You dont know js hoisting code#

The JavaScript code was like a fire that I would kindle from a distance and not actually get close to. I would dread every time I needed to make a change to the JavaScript, and try to put it off for as long as possible. Thankfully, my colleague had worked on a web app with a similar user interface, and I copied her JavaScript code and made as few changes to it as possible. I worked on a web application using Flask, but a web application needs to have a user interface. This solidified my understanding of Python. I got a job as a Python programmer, and I read this book called Think Python, which had practice exercises that were really fun to work on. When I was in college, I mostly stuck to programming in C and C++, apart from occasional fiddling with Java, C#, and Python.