How to become a JavaScript master "reprint"

Original URL: http://www.cnblogs.com/keva/p/how-to-become-a-javascript-badass.html

English website: http://www.clientcide.com/deep-thoughts/how-to-become-a-javascript-badass/

Last week I wrote a rather lengthy article, lamenting that finding a talented front-end developer is quite challenging. This article raises some comments and e-mail discussions, and I don't just want to complain about this objective fact here, but to make a personal suggestion about the status quo; Here are some tips on how to be a good JavaScript player.

My stories, in Brief

The experience of how I became a javascirpt development is not fun, but if you must ask me, here are some key highlights:

1, I study in high school and university some music, photography and painting art, although this is not my major (this is jazz guitar).

2, I learn HTML to home to the mosaic is still in use, each time the browser update to learn some new web skills.

3, I participated in an activity (at that time HTML is very popular) in 1997, I learned a little programming (JAVA). I'm not very good at it. I built a very simple CMS with Java.

In the 4 and 1999, I developed a site about music (http://www.epitonic.com), which I designed and built. A very small development team built a more powerful CMS. And a lot of JavaScript.

5. In 2003, I joined CNET as the product manager. I didn't write a lot of code, but whenever we needed some javascript, I rolled my sleeves into JavaScript, inadvertently became a "JavaScript developer" and shared my research with my blog (clientside.cnet.com).

6, at first, my focus is prototype.js, moo.fx.

7, MooTools deeply attracted me, I wrote two articles for Mooltools research.

8, while doing the product manager, while doing JavaScript development.

9. At the end of 2007, he left CNET and started iminta.com. At the end of 2008, after the crisis, I started thinking about finding a job and finding Cloudera (or, they found me).

My career is a strange roller coaster track, and for me JavaScript and web development are always a means of hitting the target. I like to create interesting products. I don't really care if I write some JavaScript or server-side code myself.

Enough about Me, let's talk about becoming a JavaScript Ninja

The above experience I just want to tell you that I can't tell you exactly how to be a front-end development engineer, everyone has his own experience, unlike mine. I spent a year in CNET learning JavaScript and JavaScript frameworks, but you can spend less time learning this in other ways, and here are some of my personal suggestions:

1. Study design and designers. Does not require you to have a designer's skills, but it is recommended that you look at the perspective of the designer, when you browse the Web, try to tell which 1 experience good, which pages good-looking. I often ask interviewers what sites they admire and why.

2,Study JavaScript. I mean the real research. Watch all Yui Theater on the Crockford video. You can also watch the other videos here, I am not 100% agree with all they say, but for learning is very good. Read Crockford's "javascript:the Good Parts". Again, I am not entirely in agreement with all this book, but I can learn from this book the earnest and solid language Foundation.

3,Study JavaScript frameworks. Note that not a frame, but multiple. I wrote the original document for Mooltools, which I think is the most important thing in my learning experience. To write a document, I read the mooltools source and try to understand why it did it and why. I learned a lot from it, but the study is gradual, never one thing let me take a big step. When I created jqueryvsmootools.com, I did this again, and this time the object was jquery. To get a sense of it, I read all of its source code. There's also dojo. From these experiences I learned some of the coding styles of these framework authors. Don't just use jquery or MooTools. Try to get to know them, understand their differences, characteristics and interesting places. Don't stop this knowing that you really understand what these frameworks are doing. Don't hesitate to share some of your ideas with the framework authors, and they'll be happy to.

4,Get involved with a framework. The second important thing for me was to be involved in the Mooltools project. Participating in an open source project will add a lot to your resume. As long as you are willing to take the time, some existing frameworks still have a lot of bugs, try to solve some! Go write some test cases! Write a blog about how you use these frameworks. Try to do these things, I promise you will get a lot of interesting offer.

5.Release Some of your own code. This is important! If you don't have the code on GitHub, you'll lose a lot of chances. You can make your potential employer aware of your code capabilities.

6,Blog about it. Try to write down what you learned in your blog that 3 years of time can accumulate a huge wealth of knowledge. You raised a question in your blog that might attract a large number of developers interested in the issue. Inadvertently, you may become an expert in this field. If you continue to publish some of what you are learning and what you are doing, you will find that one day someone will automatically find you. It's a time-consuming job, but it's a very meaningful job.

7,Build something interesting. In order to create a PHP picture library, I spent a month or two to learn PHP and Smarty, because of the project, I created a lot of excuses to learn some new technology. Forcing yourself to do some projects has never been faster than learning new skills in the process. Don't rely too much on the skills you have now, always look for opportunities to solve problems with new technologies.

8,Join a startup. I know it's tricky. (seemingly not suitable for national conditions, brushing)

9. Take the time andlearn why solutionswork. Use Google to find solutions to problems while trying to understand the real cause of the problem or what is the underlying reason.

10, becurious, and fight off laziness. Finding opportunities to use new technologies to solve old problems, knowing these opportunities and seizing them, is nothing better than taking a paycheck and learn to work. Communicate technical issues with your colleagues, he has techniques you don't know, you have the skills he doesn't know, and learn from each other. And don't just stay in the small area of JavaScript.

I can also speak a lot of things, but the premise must be that you want to be a front-end developer and be happy with it.

How to become a JavaScript master "reprint"