Why should I call myself a Javascript programmer?

Aaron Griffin wrote a wonderful article about various frameworks and functional features that can extract programmers from major business programming. To sum up his main points, when you become a "Rails programmer", you use something that is easy to understand but not universal, it is abstracted from something that is easy to understand and common, such as HTTP and SQL. The knowledge on Rails is not universal. If you turn to a new frame, You have to discard your current skills. There is no intersection between Rails and your new framework.

Aaron has a lot of arguments to discuss. He does a good job and I don't want to summarize them. You can read them yourself.

But I want to talk about an episode. In this article, he said:

There are too many, too many 'developers' who like to falsely advertise themselves as "PHP programmers", "Ruby programmers", or "C ++ programmers"-This is meaningless. Programming Language is just a tool. Each has its own problem areas of expertise. Calling yourself a "C programmer" is like saying you are a "hammer Carpenter", a carpenter who only uses a hammer. We all know how silly it sounds.

What I want to say is, "This is an inappropriate saying that is clearly incorrect in all his wonderful views ." I think the level of his metaphor is totally unequal. The knowledge and experience of the term "C programmer" is totally different from what the hammer carpenter expresses. If we want to find something of the same level, we can find some titles related to this industry tool: crane operator, train operator, and numerical control equipment operator.

But this issue is not important. I agree that Araon has obfuscated tools and tasks. Being a tool expert, rather than a task expert, can make your work a bit biased. Being a tool expert can make you work very efficiently when using the tool, but when you need to leave the tool environment or worse, you need to use other environments, you seem powerless.

If you do not understand relational databases and SQL (the current standard language), when you switch from ActiveRecord to LINQ, you will find that it is quite painful, because you need to find a ing between LINQ and ActiveRecord, rather than between LINQ and SQL. Aaron is right.

In the above section, I think there is a problem comparing the title of "C programmer" with that of "hammer Carpenter. I also found another problem that brought me closer to Aaron's perspective. I don't think programming language is a tool, but I think it is a sign of thought. If we can compare something with the wood industry, I think language is in programming architecture.Wood.

C cannot be compared to a hammer. C should be wood. Therefore, a C programmer should be a carpenter. You are proficient in all woodworking techniques and do not mean that your skills can be used to handle wire and cable, light laying, or aluminum products. However, it is competent to do all kinds of wood products.

The tool for processing wood is the IDE we use. If you call yourself an "Eclipse programmer", you do not need to know that it is doing automatic compilation and automatic reflection, you do not know how to use git or SVN or those plug-ins that do not know it... Then, you are like a hammer Carpenter.

That's what I think. Thanks to Aaron. Good discussion.

Original article: Why I call myself a Javascript Programmer

Http://www.aqee.net/2010/11/02/why-i-call-myself-a-javascript-programmer/.