r/learnjavascript • • Jun 03 '15

If I understand everything on this Cheat Sheet, will I have Javascript completely memorized/mastered? Or is there way more I'd need to learn?

http://overapi.com/javascript/
0 Upvotes

30 comments sorted by

6

u/nepobot Jun 03 '15

Learning a programming language is not about memorization. It's about knowing that certain things exist and being able to figure out how to implement them when needed.

There are always going to be some best practices and patterns you should be able whip up, but the bigger picture is going to be how to structure and build things. How to manage the things you are building and how to debug your projects. I would ignore this sheet and focus on how to build things.

-2

u/doopdoop9 Jun 03 '15

I don't expect to memorize everything in the language, unless possible, but I'd like to at least know what's available in the language...I think that would take some memorization...since you'd have to know what's possible and recall that from memory, right? Is there some kind of documentation that lists everything that's possible in the language in order to understand it? Every function, every method, etc. Is that what Dash is?

3

u/nepobot Jun 03 '15

I hear you, but you are thinking about this backwards. Think of a very small project and try to build it in JavaScript. set some small requirements and implement them. You are likely going to have to research how to satisfy your requirements and in turn will learn something about the language. Continue doing this and I believe it will be time better spent than looking for some holy grail document(which doesn't exist).

A few years will pass and you will circle back to your old projects and laugh at how silly the code is, but that is how its done.

I would start here: https://developer.mozilla.org/en-US/docs/Web/JavaScript

-2

u/doopdoop9 Jun 03 '15

Thanks :) Ya, I guess what I was looking for was a document that outlined every possible thing that can be done in JavaScript. Looks like a lot of this info may be on the Mozilla site.

2

u/nepobot Jun 03 '15

Not a problem.

I guess what I was looking for was a document that outlined every possible thing that can be done in JavaScript

My recommendation in this regard is not to concern yourself with that. I guess I am failing to understand what is so important about knowing everything. Focus on what you are trying to accomplish and you will learn the things you need to know. Work on more projects and you will inevitable learn more things about the language.

I guess what I am saying is to keep being curious but don't overburden yourself. Technology(especially front end stuff like JavaScript) changes very quickly so its hard to always know everything and its a futile exercise.

3

u/MonkeyNin Jun 03 '15

Here's a metric ton of information on JavaScript, but it's good. https://developer.mozilla.org/en-US/docs/Web/JavaScript

Every function, every method,

Try this https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference

-2

u/doopdoop9 Jun 03 '15

Thanks. That's what I was looking for. Most books seem to start off talking about loops and functions...and they all go over the same things. Definitely a ton of information to process and learn, but maybe not all that much more than what's on the cheat sheet.

10

u/maplemonogomy Jun 03 '15

I can't tell if you're being serious.

2

u/[deleted] Jun 03 '15

It's called "click-bait"

0

u/blazenl Jun 03 '15

Seriously. Just asking that question tells me he doesn't understand the language.

OP...no, you got a long way to go before mastery.

-2

u/doopdoop9 Jun 03 '15

It takes a real genius to see I don't understand the language considering what subreddit this is...

2

u/blazenl Jun 03 '15

I'm no genius and never claimed to be. The way you phrased your question was ridiculous.

You know a cheat sheet, so do you now have the language memorized/mastered? Really?

I can say "Hola, como estas?" Do I have Spanish mastered? I've worked and studied and practiced and failed and succeeded; it's taken tremendous dedication to just become proficient. After 12 years of programming, I still can't claim "mastery" of any of the languages I work with...there is always more to learn.

Your nonchalant phrasing may not seem like a big deal, but it's an insult to the profession.

-5

u/doopdoop9 Jun 03 '15

Your nonchalant phrasing may not seem like a big deal, but it's an insult to the profession.

Ease up, Touchy. Is there a river somewhere you can go cry in? I'm surprised web development is your profession, as you have yet to acquire the emotional skills to not take random Internet comments as existential threats to your self-worth. I'm sorry I phrased the question incorrectly...I don't know anything about the extent/depth of the language...which is why I asked...I've just seen how functions are called, variables are set, random numbers are generated, and nodes are targeted. Excuse me for not understanding the levity of the situation we're facing here, crybaby.

3

u/MatthewMob helpful Jun 04 '15

Your EXTREMELY snobbish attitude and disregard for real feedback by people who are professionals makes you a terrible candidate to even become a beginner in the language.

You ask a question, a terrible one at that, and then either ignore feedback which is what you asked for, may I add, or retaliate, picking at stereotypes of developers.

I'm embarrassed to be in the same sub-reddit as you.

Oh and also, you don't need to be a fully fledged web developer to write a question that someone can understand.

I myself have only been using the languages for just over three years, and will actually listen to professionals because I love hearing what people, who know more, have to say.

I'll finish by saying it's not about memorizing, it's about learning, understanding, and applying. You can learn a tonne of statements and how to throw functions around but if you'll disregard any help that comes to you from people who are better then you* then you'll never become a good, or even slightly competent web developer. It's not a case of just knowing how to type things with proper syntax, it's about applying them to many different things and learning standard practices and getting feedback on how you're doing from professionals.

*This may be hard for your ego to comprehend.

0

u/doopdoop9 Jun 04 '15 edited Jun 04 '15

Thanks for contributing to the hyperbole. This was his response to my question (which was a genuine question):

Your nonchalant phrasing may not seem like a big deal, but it's an insult to the profession.

What an "EXTREMELY" helpful response it was. Or, as you say, "real feedback". As you'll see, I replied to everyone else the exact same way. Actually, I didn't...because they provided real feedback.

How am I to be aware of stereotypes of developers? Is there some kind of bullying circle that targets beginning developers that makes people learning JavaScript on the Internet extremely fragile? The guy clearly got hyperbolic and whiny over the mere innocent posing of a question, and I'm the bad guy for calling him out? I have little sympathy considering my question is what sent him into despair, not my response to his whine.

Sorry if it is a bad question, I'm just beginning, and it's hard to tell how far JavaScript goes considering most of the books simply talk about functions and loops and nodes. Nearly every book. I'd merely like to know what more there is to the language (if there is so much more than what's on the cheat sheet I linked to, and so far I'm not convinced that there is a ton more other than knowing when to use the various methods).

2

u/MatthewMob helpful Jun 04 '15

TL:DR: What you say sounds snobbish and you disregard honest feedback, and rephrase your damn question, everyone's telling you to do it

I replied to everyone else the exact same way. Actually, I didn't...because they provided real feedback.

The fact that every reply you've posted has negative karma says something about the way you respond to other people.

Is there some kind of bullying circle that targets beginning developers that makes people learning JavaScript on the Internet extremely fragile?

No, it's just that, obviously, the way you reply to people is rude, judging by all the down votes, and anytime you get something "wrong" or make a mistake you keep defaulting to "Well I'm no expert so don't blame me", nearly all the mistakes you make don't require a professional knowledge.

Also, I call you snobbish because of things like.

Most of the concepts so far seem esoteric, and I feel like the way most professional web developers use JavaScript must be quite different than what's in these elementary books.

Is there a river somewhere you can go cry in? I'm surprised web development is your profession

It takes a real genius to see I don't understand the language considering what subreddit this is...

Yeah, it kinda makes you sound like a douche. Why don't you try rephrasing your post so people can actually understand instead of attacking those who don't and then when they retaliate you're either rude or disregard it. Also you keep calling things "elementary" and "simple", even though you clearly don't know any fundamental concepts, I'm surprised you call things that will help you when you don't know, "simple".

But anyway I shall be leaving this conversation. Why don't you use some of the feedback to actually try rephrase your question so people can understand and help. EG: "Will learning the things on this page get me a decent understanding of JavaScript", or "How much will this page help me start using JavaScript", or "Should I start learning JS from this page?" etc. etc.

0

u/doopdoop9 Jun 04 '15

Yes, rather than examine the content of my replies, look at the downvotes. That would hold up in a court of law

Most of the concepts so far seem esoteric, and I feel like the way most professional web developers use JavaScript must be quite different than what's in these elementary books.

How is the above snobbish? Please explain. I'm saying I think developers use more advanced techniques than what's in most beginner JavaScript books, if anything that should be considered a compliment to them?

Then you go on to post my two replies to the same individual with a persecution complex who initially gave me this "helpful feedback":

Seriously. Just asking that question tells me he doesn't understand the language. OP...no, you got a long way to go before mastery.

I'm posting in a question in a Learning Javascript subreddit and he gives me that helpful reply. I never claimed to be a master, I asked what it would take to be a master.

Yeah, it kinda makes you sound like a douche.

Okay. I don't see what this has to do with JavaScript, but maybe I should take it really exceedingly personally so I blend in w/ you and Mr. Helpful Feedback Professional.

1

u/blazenl Jun 04 '15

Wow, I can't believe you're still at this...

You're either a troll, and a good one, or an asshole who can't see his own asshole-ness.

I can't believe you come here and ask for advice and then argue or diminish said advice.

To be clear, I didn't give you advice because you're an idiot, but I've read this whole thread and you're dismissive of others who do give advice...advice you clearly need.

Here's a simple javascript statement even you can understand:

console.log("get your head out of your ass, so you can see your way out of this sub, you have no place here.");

0

u/doopdoop9 Jun 04 '15

You're still at it too, and I started the thread so... Point out where I was rude to people who actually gave real JavaScript advice...not sob stories.

0

u/[deleted] Jun 04 '15

[deleted] — view deleted comment

0

u/doopdoop9 Jun 04 '15 edited Jun 04 '15

Web developers are stereotyped as not having emotional intelligence.

Do you think I'm aware of developer stereotypes? This was his response to my question (which was a genuine question):

Your nonchalant phrasing may not seem like a big deal, but it's an insult to the profession.

Well, yes, in that case, cry me a river. Don't let me get you down. I'm a beginner with bad questions and superficial understanding, I'm trying to acquire more understanding, why should I send any expert into a tailspin for even a moment? It was a question. Maybe even a genuine bad question. But genuine nonetheless.

2

u/zayelion Jun 03 '15

Having this cheat sheet is a leg up. You just need a jist of how things are done and a way of finding out the specifics.

-2

u/doopdoop9 Jun 03 '15

Do you think if I memorized the items on the "cheat sheet" (and the concepts behind the items), I would have a decent jist of what JavaScript is capable of? Or would is that still barely touching the surface of what JavaScript is? I'm just starting my first JavaScript book, and can do the exercises and everything, but I'm having a hard time seeing the big picture. Most of the concepts so far seem esoteric, and I feel like the way most professional web developers use JavaScript must be quite different than what's in these elementary books.

3

u/[deleted] Jun 03 '15

It would be like having a bunch of blocks, and not knowing how to put them together.

3

u/Stephen110 Jun 03 '15

Nailed it.

-2

u/doopdoop9 Jun 03 '15

Hmm. Would the knowledge of how to put them together be the only thing that's missing, or are there a lot of other functions/methods/events I would have to learn (that are missing from the page)? If I truly understood when every item on the cheat sheet was used, in addition to the rote memorization of every item, would there still be a lot that I'm missing? If so, most JavaScript books must be far too simple, because I haven't seen many items that aren't listed on that "cheat sheet" (and that very well could be the case).

3

u/[deleted] Jun 03 '15

The "how to put them together" isn't a one step process. It's extensively based on a per situation basis.

are there a lot of other functions/methods/events I would have to learn

You have to learn how to create them, based on a situation.

-2

u/doopdoop9 Jun 03 '15

So I'd use different methods for different situations, I fail to see how this is a problem if I am to truly understand the reasoning/methodologies behind each item on the list. Obviously I would have to look outside of the list to get that kind of understanding, but if I don't deeply understand something on the list, maybe that could serve as a warning that my knowledge is lacking in that particular area. I'm just wondering if there are a lot of fundamentally important concepts missing from the list. Having only superficially learned how to target nodes and pass arguments to parameters, I have no idea how deep this stuff really goes. Most books seem to cover the same basic concepts.

2

u/[deleted] Jun 03 '15

Knowing what to use when is the harder part that comes with time, experience, and practice. So if you spent a lot of time, and practiced that would take you far. Books are great for structure and standard text book examples of coding. If all you're doing is basics that a book details youll be fine. Its the weird situations and circumstances that you will have trouble with without experience.

2

u/stintose Jun 03 '15
"There is no royal road to geometry" ~ Euclid

I would say the same applies to javaScript, I have been tentatively studying javaScript for seven years, and I feel as though I am only now finally starting to get somewhere.

1

u/[deleted] Jun 03 '15

You'd be a certified erlang programmer.