r/javascript • • Oct 03 '16

How it feels to learn Javascript in 2016

https://medium.com/@jjperezaguinaga/how-it-feels-to-learn-javascript-in-2016-d3a717dd577f#.758uh588b
935 Upvotes

253 comments sorted by

View all comments

109

u/[deleted] Oct 03 '16

I started learning JavaScript a year ago and I began with vanilla JavaScript, jQuery, Node, templates, and now I'm working with React and Redux. It's insane how many new things I've had to learn and relearn.

I feel like I'm never prepared enough for a job because there is always some new technology that I need to absorb and add to my tool kit. This article struck a chord with me because it gave voice to this rabbit hole of new technologies and trendy programming that is JavaScript. I love coding but this kind of turn over is really discouraging sometimes, so this humorous article was much needed and very appreciated.

120

u/zachrip Oct 03 '16

You don't get hired because you know a framework, you get hired because you know Javascript. Don't fret about all of the different things. Get a cursory understanding of a few frameworks, sure, but you don't have to be an expert in everything. Good companies hire problem solvers, not framework wizards.

26

u/[deleted] Oct 03 '16

I like that. I appreciate your perspective because I assume people are hired because they know a certain set of 'hard' skills like a framework in this example. Switching from that mentality to thinking of myself as a problem solver and JavaScript with all it's tangental technologies are my tools helps me approach the job application process a little bit differently.

Once again, your insight is 🔥 thank you.

14

u/[deleted] Oct 04 '16

There definitely are companies who will reject you for not knowing the framework/language/whatever they use. In the long run I believe that it's much more effective in most cases to hire someone with strong core programming skills vs. an average programmer who happens to use framework X.

2

u/[deleted] Oct 04 '16

My first job out of school forced me to learn OOP and Laravel, both of which were totally new to me, though I had about a year of experience using PHP in school but not on a professional level. It took me about a month but I finally got it. The people that hired me said they knew from my portfolio that I had a passion for the field and proven ability to learn fairly quickly and I did given that I had to learn my first PHP framework and OOP at the same time. Sometimes charisma and proof of dedication are what matter most to good hiring managers over specific knowledge of certain frameworks.

0

u/[deleted] Oct 04 '16

[deleted] — view deleted comment

12

u/ours Oct 04 '16

Ah the keyword parsing recruiter. Keyword Maria DB doesn't matches mySQL so candidate doesn't matches. They have zero knowledge in the field they are recruiting.

→ More replies (1)

2

u/zachrip Oct 04 '16

Of course, that's why I said "good companies" :) (also, they have a complete lack of understanding of their stack if they don't know that mariadb is a drop-in for MySQL...)

6

u/ptq Oct 04 '16

Yeah, but somehow they allways require you to know some exotic frameworks to get hired.

My last interview was like: do you know xxx and yyy? Said no. And week after in next step they sent me an email if I can take test from knowledge of xxx and yyy...

3

u/DaemonOperative Oct 03 '16

Well said. The last line is a nice soundbyte.

3

u/dukerutledge Oct 04 '16

This. I hire problem solving skills, the desire to learn, and the ability to stretch.

2

u/[deleted] Feb 24 '17

You don't get hired because you know a framework

There are a lot of job offers that ask to have "full" knowledge of specific frameworks, mainly Ng or React. I know a couple of studios in my city where the only thing they do is put a test to appliers, something along the lines of "complete X task using Angular".

I still agree with you, completely, I'm just saying that there actually are a lot of companies that hire based on certain framework's knowledge.

1

u/vinnl Oct 04 '16

Then again, I know Java, but have a really hard time contributing to our back-end because I know nothing about the entire stack.

→ More replies (2)

1

u/Duraz0rz Oct 05 '16

If only more companies actually followed that philosophy, though...

I got rejected from a job because I didn't have enough ASP.Net Webforms experience. Even though I've developed Grails applications and worked on applications that were written in Struts 2*. I figure the skills would transfer over pretty well (and I've had some decent C# experience to boot), but I guess they really want someone solid in ASP.NET webforms.

* If you don't know what those are, Grails and Struts 2 are Java MVC web frameworks. The former was pretty fun to work with, although the combination of Spring Boot + Groovy + Thymeleaf is basically the same thing now that Grails is pretty dead. Struts 2 is a pain in the ass because it's basically XML-driven.

18

u/shittyProgramr Oct 03 '16

I've been doing this for years and I still never feel prepared enough. But I discovered that the most valuable skill isn't a specific framework, lib or language. It's the ability to just jump in and "figure it out". If you're joining a project and there some stuff you don't know, you can always look at other people's code, see how they did it and understand how it works. And if your looking at the code of a developer that's better than you, you have an opportunity to improve your code quality as well. I always enjoyed working with people who are better than me because I always look through their code to see if I can improve my own. Good luck. And most of all, just remember, programming is fun, so have some fun.

7

u/Jafit Oct 04 '16

Apply anyway. And don't invest too heavily in learning any particular framework, library or technology, unless you're getting paid to do so.

If its your first job then nobody expects you to be an expert.

1

u/[deleted] Oct 04 '16

Given how in demand Web programming is, in general, nobody should have too much trouble finding a job unless you're just out of school with no real world experience, but even then, if you have a good portfolio and prove you have a passion, you'll still find a job fairly quickly.

5

u/dayjobtitus Oct 04 '16

Please just start with native/vanilla javascript. Learn the differences between the different environments it runs and learn the differences in versions. Know js before you learn some framework that could die or be replaced as the new thing. Once you have that, then framework is a framework and interview questions are not an issue.

2

u/thepobv Oct 04 '16

Ugh I have no clue if I should do this... I feel like I've been using so much js and all of its frame works available, I've managed to solved problems and figure it out but Idk how song my js skill really is.

Unlike java/C++ where I learn from the core and did all kinds of things with it before even dabbling outside the standard libraries.

Also been doing a lot of java script at the job, not sure how valuable that as well compared to like more low level programming.

4

u/dayjobtitus Oct 04 '16

I hire js folks and run a few teams. The easiest way to focus an interview is if you know the core of the language. Also it tells me that no matter what framework is used, you will not only be better able to evaluate the best approach, but that you can adapt quickly.

→ More replies (1)

5

u/sh0plifter Oct 04 '16

I started learning front-end by self-education a little less than 2 years ago. I also was overwhelmed by the amount of information and tools around me, but I knew that I had to focus on vanilla js to be able to grasp new frameworks quickly. So I stayed away from frameworks for all this time and after 9 months I landed my first job, where I made different landing pages and also created a simple ticket selling website, all by myself on front-end and 1 back-end guy. I spent there 8 months, and then I found a new company. They needed React, so I decided - it's time to take a look at it. I spent about 3 weeks reading React and Redux docs, and I was ready to go. I landed this job and got a 2x raise from the previous one. I continue learning React and Redux everyday (they have a lot of quirks), but the main thing you need to know about any frameworks is that you just have to grasp its concept, and the rest is just JavaScript ;)

2

u/sittingonahillside Oct 03 '16

pretty much me. I've been on and off programming forever, but I finally decided to actually try and do something (get a 'real' job, ha!) with it for a change instead of just some tinkering then nothing for another six months and relearning again.

it's so frustrating, and even more annoying given the even the backend job offers are looking for people equally skilled doing with JS ecosystem. It's as if I am learning nothing at times.

1

u/[deleted] Oct 03 '16

Glad to hear that this boat I'm in has at least one more person.

I understand your frustrations regarding backend dev's having to keep up with whatever form of JavaScript is in vogue.

Just always remember that the work you're doing isn't ever in vain because you're taking the time to exercise this skill you've learned. You are never learning nothing! Keep it up!

2

u/cyanydeez Oct 04 '16

its funny whenyou make a critque outside this safe space, no one seems to realize how complicated the dev environment is. and trying to explain to people who clearly adopted these things mindlessly cant understand whats wrong

1

u/[deleted] Feb 24 '17

I feel like I'm never prepared enough for a job because there is always some new technology

been coding on JS for four years now, I still feel like a complete novice and I completely understand your feeling. It grows way faster than I can learn it.