Do you think the lecturer is too lazy to correct his mistakes in the video, and look for API doc before teaching?

Just watched the video, here are a few things to keep in mind:

1. Everyone makes mistakes sometimes, no matter how experienced.
2. Sure, they could have edited small mistakes out, but then you would miss how an experienced person troubleshoots these sorts of issues - which I believe is a valuable thing to know.
3. He looks up the API documentation on purpose because you will often be doing that in the real world. Being able to see somebody else go through it gives many people a better idea of how to do it themselves when the time comes.

I hope that makes sense. :)

Oh, and personal opinion, but I really like Andrew Chalkey's teaching. Everyone learns differently, though so it's perfectly normal that his teaching might not work for you.

Hanxiao, would you rather learn from a teacher who acted like a robot and new everything like a machine, or one who can teach you to think as you go along and debug? I'll admit, I feel like they were more prepared in HTML and other JS chapters, but I appreciate that he's been showing me how to look through the docs, just like I'd have to do in a job.

Once I started reading more about jQuery I realized how well done his approach was. I used to complain about Andrewºs style but he is really doing a great job explaining jQuery. When it comes to API - programmers are NOT supposed to be walking books of codes. More proficient programmers need to know how to find what you need. Sometimes you will need one method, function etc in a year. You have to be able to find it if such a case arises. Being able to go through a documentation (and doing it) is a tedious yet the most important part of programming career.

I have to agree, I was impressed and hooked with the way the HTML and CSS courses were laid out and taught, however Andrew's way of teaching doesn't leave me feeling as if I'm "taught", it more so leaves me feeling as if I'm watching someone else "learn".

To be honest it gives the impression that this whole course was thrown together and made in the span of a day or two with very little preparation and editing.

I suspect that his methodology is more inline to "think" like an engineer. Although the course is taking a lot longer to finish than others, it does has a teachable moment each time he "intentionally" makes a mistake.

I try to pause that section of the video, to see If I can figure out ahead what the problem is, and skim through my code and the documentation.

Yes, it's painfully slow, but he's walking through real possible scenario that you will encounter eventually in other projects, and how to stop, slow down, and assess what to do next.

I was wondering the same thing the entire course. If he's messing up intentionally to show you how you will likely need to lookup solutions in the real world, then that's a good thing to see sometimes. But I agree, if he wasn't intending to do that then it really needs to be crisp like the HTML and CSS courses where information was presented perfectly clear. No mistakes or searching for the right words.

There have been a few times when I'm trying to get a concept down and I lay out the information in my mind in a way I can memorize it, but then he makes a mistake and i'm like, "Wait, ok, delete that part from my mind, add this part in." It just gets confusing. I remember a teacher in school saying, "the way information FIRST enters your mind is very important".

Agree . Because of that , videos are so long . Waste my time