Hello there, how is it going?
Welcome to 8bitmen.com
So, without any further ado.
Let’s get on with it.
Agghh… Is it really required? I already know what it is.
Believe me, this will help us a get a better understanding on the whole thing. You will know how…
Simply put, it has the monopoly over front end development 😊
When starting to learn, the first thing is to clear our basics in programming. Be well acquainted with the language syntax, like if-else constructs, for while loops, arrays etc. Get a sense of what programming is.
If you are willing to devote 2 to 4 hours a day, a couple of weeks should be enough to get the hang of things.
There are several code editors available like Atom, Sublime Text, Vim, Brackets, the most lightweight Notepad++. You can pick any based on your liking.
Having a good understanding of OOP is pretty important & naturally, requires time.
Hmm, I would say if you devote 2 to 4 hours a day. 3 to 4 weeks will suffice. To acquire a good in-depth understanding on the concepts.
Now with all the concepts, clear we can get down to writing code. Obviously, we have been writing code. But now we can venture into writing applications. For the start, it can be as simple as a nice calculator app or an app which reminds you of the birthdays of your friends.
If you do not know Html, you can also learn it parallelly but it’s gonna make things a little difficult for you. The ideal way would be to learn Html first.
Getting yourself acquainted with syntactical stuff should not take you more than a week working 2 to 4 hours daily. Then you would have to go through the advanced concepts like the Closures, Web APIs, Event Loop, Prototype chain etc. This is gonna take some time. From one month to a couple of months. Depends on how dedicated you are to learning stuff.
Also, things get a whole lot clearer when you implement these concepts in an application you write from scratch.
More the technology required in building stuff. More job opportunities it’s gonna create.
After we are good with the fundamentals, & have enough confidence to tackle the interviewer’s questions, we can ideally start applying for jobs.
But I wouldn’t apply just yet. Why?
I would recommend, build a good project using it before you apply. And a project can be anything from a small website to a simple browser game.
Oh God… Why a project? I am out of patience already. Isn’t investing a month reading the concepts enough?
Well I know, it’s hard to keep studying but hear me out. Why am I recommending a project, why is it important?
Brood over the below points:
1. It Boosts Our Confidence by Notches: When we build a project from scratch, from bare bones. Doesn’t matter how small or simple. We kinda really get a grasp of how things work. How the lego blocks fit together & turn out into a big functional working thing.
Even if the interviewer tries to mess with you, plays around, tests your confidence in the fundamentals. You know your concepts pretty well because you have built something implementing those concepts. You are confident in what you say, you haven’t just read stuff from some book. You have actually built a real working functional thing.
3. You Get a Solid Hands on Coding Experience: When you work on a project besides writing the core logic there are several other things like handling exceptions well, null checks, following best practices, writing modular code, creating a good object design, writing fail-fast, fail-safe systems. You just cannot learn these things if you don’t write a project by yourself. You acquire project designing skills, along with writing code.
All in all, it doesn’t hurt building projects. The odds of getting a job spike by notches.
More On the Blog
Well, Guys!! This is pretty much it. If you liked the article, do lemme know in the comments.
I’ll see you in the next article.
- What is Lift & Shift Migration to the Cloud? – An In-Depth Insight
- Distributed Cache 101 – The Only Guide You’ll Ever Need
- Facebook Real-time Chat Architecture Scaling With Over Multi-Billion Messages Daily
- Twitter’s Migration to Google Cloud – An Architectural Insight
- What Is an Instance In Cloud Computing? – A Thorough Guide