Let's talk about cars.
Oh wait, we already did - remember that time we met, a few weeks ago? We talked about cars. In fact, you seemed to be quite the expert on cars. You were able to explain, in detail, all of what's right, wrong, and exciting about the latest Formula 1 race. You knew by heart all of Lamborghini's models, including their price and availability. You even had thoughts of purchasing your own Ferrari 599 GTB Fiorano, and were saving up for it (bet the steak dinner didn't help much.)
While explaining the faults of Toyota in a great, excited voice, you suddenly jumped from your chair and screamed into the air, waving your fists about: "Damn it all, I'm a magnificent expert on all things related to cars! I'm gonna be a car mechanic!"
And so you went. You had an interview, the Boss Man was just as impressed as I with your knowledge, and you were hired. The first client came in. His clutch was broken. You inspected it, and didn't know what to do. As a matter of fact, you had absolutely no idea how to follow the advice the Boss Man gave you. You were fired.
But how could that be!? You know everything about cars! Except for ... everything about cars. You can very well know your dream car has a V12 engine, but you don't know what that actually means.
So you're not a car mechanic, really - you're a car enthusiast. And until you learn how cars work, you will remain an enthusiast.
Now let me ask you. How does
$.fn.text work? And what about
$.fn? What do they really mean? How does
$(something) return a gigantic thingy containing things, and what is that thingy exactly? Can you replicate their functionality, at least a bit, in theory even? Can you cope without jQuery?
Array.prototype.forEach is to
for. It works, for 99% of the cases. And it works well. But for that 1% which isn't covered, you need to know how to use the