If you haven't started a bootcamp and what this instructor is saying is confusing you, don't worry, these concepts are HARD, a lot of bootcamps don't expect you to know these to start but they will teach you.
@@isaacgarcia2979 I struggle the most with defining these concepts. For example, when he said “higher order functions” i didn’t know what he meant. I’ve been passing functions into functions and didn’t know the technical name.
This was good to know but not explained in a way that would capture the intended audience. Mainly because the explainer doesn't seem to completely understand his target audience any more. Any time you address an audience you are now essentially a public speaker, and as a public speaker its imperative to know that if you are a speaking to an audience that is new to your concept, do NOT fill your explanation with jargon or even language you learned during your introductory classes. If you want to share anything, you have to break it down to much smaller parts-- pun intended.
I still don't quite understand the last part. Classes creates instances of that class and those derived classes have extra functions. But when he says those derived classes are just pointing to the parent class. Not sure what he meant lol
Rat, Pick up a book on coding on your own. That’s what I did. It’s not a difficult subject, if you can understand the origins of it. Here, you have a guy with his nose in the air, going on about a bunch of nothing.
That sentiment is precisely why some people (myself included) are very leery about ES2015's inclusion of `class` keyword. ES2015 classes are not an alternative to prototypal inheritance, they are an abstraction pattern on top of prototypal inheritance. It makes some things easier, and you can "get away with" using them sans deep understanding for simple patterns (e.g. formulaic class-based components for React), but it is still possible to run into edge and corner cases where JS's true prototypal nature peeks through. In those cases, if you mistake JS's `class` syntax for true classes, you may end up horribly confused. Whereas, if your basis is a confident understanding of prototypes, `class` becomes a convenience rather than a crutch - and you can handle it when coming up against prototypes in the wild. The same goes for things like `async`-`await`, which is basically do-notation for the Promise monad; if you don't have a really good understanding of promises, it is very easy to write terrible `async`-`await` code which doesn't leverage concurrency or handle exceptions as well as it should.
Galo Recalde MFA /aka Dr Expertus i'm in same boat. I don't know a lot of stuff or have done a lot of free courses but I am working on it. I'm watching UA-cam videos and doing swift playgrounds. Lol, I am interested in learning more and get into it.
Galo Codecademy is free and will get you to the point where you're ready for their bootcamp prep. Its really good. Jon Ducketts book on Javascript is amazing. He's incredible at making everything really simple and clear. Sign up for Codewars when you get to around 70% through Codecadmy to do their quizzes so you can apply what you've learned. Also check out peoples questions on some the threads on Stack Overflow or Javascript Jumpstart (Fullstacks online version of Codecadmy) and look at what newbies are asking and see if you can figure out their errors. That helps a lot. If you want to actually learn, i would recommend setting aside time every day - or at least 6 days a week - to go through whatever learning tool. Consistency is key because you'll often get a concept and apply it to a problem, but if you take time off then you'll forget it and have to go look it up.
If you haven't started a bootcamp and what this instructor is saying is confusing you, don't worry, these concepts are HARD, a lot of bootcamps don't expect you to know these to start but they will teach you.
These concepts aren’t hard I’d say, they’re just new if you don’t know them.
@@isaacgarcia2979 I struggle the most with defining these concepts. For example, when he said “higher order functions” i didn’t know what he meant. I’ve been passing functions into functions and didn’t know the technical name.
This was good to know but not explained in a way that would capture the intended audience. Mainly because the explainer doesn't seem to completely understand his target audience any more. Any time you address an audience you are now essentially a public speaker, and as a public speaker its imperative to know that if you are a speaking to an audience that is new to your concept, do NOT fill your explanation with jargon or even language you learned during your introductory classes. If you want to share anything, you have to break it down to much smaller parts-- pun intended.
Really great video!
I still don't quite understand the last part. Classes creates instances of that class and those derived classes have extra functions. But when he says those derived classes are just pointing to the parent class. Not sure what he meant lol
I’m sure 2 years later you figured out your question???
@@isaacgarcia2979 hahahaha rofl totally thinking the same thing
This video has convinced me I don't really want to learn to code. : p
Why?
I can’t understand why/how a school wants it students to be twenty percent up on the subject, before the first day of class.
Rat,
Pick up a book on coding on your own. That’s what I did. It’s not a difficult subject, if you can understand the origins of it.
Here, you have a guy with his nose in the air, going on about a bunch of nothing.
With the new ES6 syntax, you don't need to worry about JS prototypical inheritance bull-crap. A simple class instantiation will do the job.
What do you mean?
That sentiment is precisely why some people (myself included) are very leery about ES2015's inclusion of `class` keyword. ES2015 classes are not an alternative to prototypal inheritance, they are an abstraction pattern on top of prototypal inheritance. It makes some things easier, and you can "get away with" using them sans deep understanding for simple patterns (e.g. formulaic class-based components for React), but it is still possible to run into edge and corner cases where JS's true prototypal nature peeks through. In those cases, if you mistake JS's `class` syntax for true classes, you may end up horribly confused. Whereas, if your basis is a confident understanding of prototypes, `class` becomes a convenience rather than a crutch - and you can handle it when coming up against prototypes in the wild. The same goes for things like `async`-`await`, which is basically do-notation for the Promise monad; if you don't have a really good understanding of promises, it is very easy to write terrible `async`-`await` code which doesn't leverage concurrency or handle exceptions as well as it should.
Oh man.. I didn’t understand anything 😓.. probably means I’m not ready to go to bootcamp
Galo Recalde MFA /aka Dr Expertus i'm in same boat. I don't know a lot of stuff or have done a lot of free courses but I am working on it. I'm watching UA-cam videos and doing swift playgrounds. Lol, I am interested in learning more and get into it.
Those concepts are specified for JS mostly. This guy makes it seems complicated but it's not.
Galo
Codecademy is free and will get you to the point where you're ready for their bootcamp prep. Its really good. Jon Ducketts book on Javascript is amazing. He's incredible at making everything really simple and clear. Sign up for Codewars when you get to around 70% through Codecadmy to do their quizzes so you can apply what you've learned. Also check out peoples questions on some the threads on Stack Overflow or Javascript Jumpstart (Fullstacks online version of Codecadmy) and look at what newbies are asking and see if you can figure out their errors. That helps a lot.
If you want to actually learn, i would recommend setting aside time every day - or at least 6 days a week - to go through whatever learning tool. Consistency is key because you'll often get a concept and apply it to a problem, but if you take time off then you'll forget it and have to go look it up.