32:21 nailed it! if you're getting an interview that is completely based on knowing terms and techniques of the tools, run to the nearest exit. Usually a sign that the interview panel doesn't have a grasp on delivery and is focused on tools.
coding interviews are so badly done . ive never had a single question that is actully relevant to my job . thats like asking a chef how to write good recipe books instead of getting them to cook
00:00 Introduction 00:19 About Russell Anderson 01:57 Inspiration for the talk 02:22 Brad Frost's responses to HTML5 Boilerplate frontend developer interview questions 03:54 Are interview questions a good idea? 04:48 Explain event delegation 05:59 Describe event bubbling 06:30 How event bubbling and delegation works in practice 08:05 What's the difference between "target" and "currentTarget" 08:35 Explain why function foo(){}() doesn't works as an IIFE 09:16 Explain the difference between writing a function as a statement and an expression 12:14 Why in general is a good idea to leave the global scope of a website as-is and never touch it? 13:17 Explain "hoisting" 18:13 What do we do with the knowledge of hoisting? 19:22 What is the difference between a variable that is null, undefined or undeclared? 26:36 What is the difference between == and === ? 28:25 You are hired! 28:52 Closing remarks 30:32 Questions and Answers
In lieu of random technical questions, I would love the opportunity to go into detail in any one of my projects---some of which are open source. While discussing the code, you'll get technical know-how right alongside how I came up with solutions to situations. Let's not interview; let's code!
"so you wanna be a chef here ? tell me how to write a cookbook then ..." "im a chef not a writer i can cook if you want" "ok i dont think youre right for us " thats how dumb coding interviews are
The reality is that if you don't know these things, you won't be able to debug your code efficiently, because you won't know why your code behaves in a specific way.
You're right, I guess it's not a big deal. Next time I'm giving a lecture on 19th century French poetry, I will make sure to start by mentioning that I belong to the church of Satan, I'm a flat-Earther, and I don't know how to knit.
Nice guy giving some background on things that are important to him. Not sure what the reception would be if I said I'm atheist, especially in the US. It is interesting though.
The title is deceptive. Turns out the most basic javascript questions are considered “tricky” by this guy. I started watching this video with completely different expectations as of what “tricky” constitutes.
why people here are so triggered about this individual literary taking 3 seconds out of a 35 minute interesting talk to share his world-view. ...3 seconds! ...didn't even made it a big deal! lul
You are right, nothing goes up physically but all the definations of variables and functions got there memory allocations in the stack at compile time, It is Hoisting.
Yes, I agree with you guys. Let, and const are "hoisted" but don't get initialized, and they are not accessible until the JS Engine hits the line that they are declared on.
No need to know who exactly you are, whats your religion, your parents...etc. When I start reading books about programming languages, the authors wrote about their life, what they drinking when they writing the book, about wheather...etc. First 100 pages of the book are empty talk. Just teach! Stop wasting the our time. We boring! We are stop watching or reading and can't learn anything.
"we boring" means that you are boring, "we are bored" means that you feel bored, and whatever activity you are engaged in is boring might wanna learn that also you can skip ahead easily, if you don't care
