So, you wish to learn JavaScript, right? Well, you're in the right place. I am starting this series in an attempt to give back to the online community, and help anyone who wishes to take their first steps toward learning JavaScript.
You may be thinking "there's already loads of free online material", if you are, you're correct. I am not trying to replace the amazing resources already available -- I'd fail, miserably. My goal is to assist learners as they attempt to navigate the endless ocean of tutorials, online courses and podcasts.
Time and time again I would read a tutorial about, for example, the use of the var tag, just to read that it is "hoisted". The writer of the article would fail to explain, in pure layman's terms, what hoisting is, whether it is good or bad or when/where to use it.
The result? Spending more time to then define hoisting and answer the questions which resulted from reading the original article. This isn't the biggest issue in isolated cases. However, it can become quite cumbersome when it is a regular occurrence.
So, in an attempt to help anyone who may be facing similar issues, my plan with Learning With a Layman is to supplement the plethora of great material which is already available. Not to compete with it.
These interactions include everything from interviews with fake press to the outcome of a matchup. The e-fed's community then votes on the quality of the post and the winner gets bragging rights. This is where my interest in web development and coding started.
However, until the beginning of this year I'd never really taken web development seriously. My approach to learning was, at best, haphazard. I leant what I needed, when I needed and nothing more.
This meant, when I decided I want a career as a JavaScript developer thus had to take it seriously, I had a lot of blindspots. And it is this which lead me to the decision of starting my learning journey from the beginning.
Since making this decision I am comfortable to say that I am at least at an intermediate level of expertise. I have started getting my own clients for development projects and am slowly, but surely, progressing toward my goal.
This leads me on to my first lesson, which isn't really a lesson, more so advice for anyone thinking of entering the field...
We all get mesmerised by the increasingly complex apps which are being rolled out through the glory of JavaScript. However, it is easy to completely bypass the fact individuals do not make these apps. Teams of highly skilled developers, who have been polishing their individual toolset for years, do.
These developers have taken the time to read what, for example, hoisting is. They have read all the boring differences between objects, arrays, strings, numbers and booleans. They know what a truthy or falsy value is, and the difference between == and ===.
The point is that these apps are made by people who know the basic principles of the Javascript language. And, while it may not be what anyone wishes to hear, in order to reach a level of skill where you can seriously consider working on something like the next Tinder, Uber or Spotify, you need to learn the basic principles first.
By doing so you will find that you achieve a lot more, in a much shorter space of time. And time is important. If you plan on seeking a career in web development, as with many career paths, you are going to need to be able to stick to deadlines. When you find yourself having to constantly research the basic principles, which you should already know, you will make mistakes and fall into bad habits.
Now, if you are a newcomer to the world of development and coding, your first port of call will probably be to Google it in some form or other.
You will then, no doubt, be presented with a load of ready made functions for you to copy/paste. Seems harmless, right? Copy the code, paste it in your project and voila! Job's a good'n. You've achieved your goal and saved time having to write out the function yourself. The problem arrises when you need to make a change.
Let's say you need to change the number of results listed per page, how are you going to do that? The chances are you're going to have to return to your trusted learning resource (Google) and spend time finding a new function to copy. This can be time consuming and, as your requirements become more obscure, you will eventually hit a brick wall.
When you're at that wall you kinda have three choices:
None of these scenarios are desirable. It is fair to assume that a paying client will expect you to be able to tell them what is going on with every line of code you have delivered to them. This brings me on to my final piece of advice for this inaugural post...
Now you find yourself in a position where you are back at the drawing board. You have literally learnt nothing and the hour you spent searching for the initial function is an hour wasted.
You decide to spend another hour searching for a more specific version of the function, and fail. Then you decide to try and blindly change variables in an attempt to solve your issue. This takes another hour and, again, proves to be an hour spent in vain. As a final, last ditched solution, you decide to make a post on StackOverflow and ask for help.
After another hour of waiting you get a response which marks your post as a duplicate and sends you back to the original post which you copied the first function from. You have literally just wasted four hours and ended up back where you started.
The kicker? The page you initially copied the function from fully explains exactly what the function is doing and why it is doing it. It provides multiple resources which explain relative concepts such as event listeners, destructuring objects, loops and DOM manipulation. Had you of simply spent the hour reading the full post, and its associated material, you'd have been able to change the function at will.
Not only would you have been able to edit the original function to suit your needs, but you would have also acquired vital information about principles which are applicable to an infinite number of use cases. As well as saving three hours.
Love, peace and happiness.
Original article: https://somethingdecent.co.uk/guides/development-and-coding/learn-with-a-layman-an-introduction/
