A brief discussion on learning Java's impetuous mentality-analytical articles

Knowledge needs to be precipitated, and thought is maturing in constant learning and discipline, and technology is being developed in constant creation.

In the "derivation", I simply gave a side of the example, and exaggerated description of a impetuous learning state. These are simple points of view of impetuous mentality, so let us now analyze some of the root causes.

In the "derivation" of the discussion, a friend referred to the "software industry impetuous" A word, also suggested in the "analysis" from this aspect analysis. About the "software industry" such as the discussion, in the major forums or websites abound, have a positive attitude, there are sighing, there are complaints, there are grievances-but these far beyond the theme of this article, but also beyond my vision as a developer.

As the topic says--"small Talk". From your point of view, from their own perspective, from their own side more Java developers to talk about.

In fact, in reality, the vast majority of developers, have more or less impetuous mentality, really able to maintain a "stable, reserved" or very little. Because in the beginning of learning Java, it is inevitable to take some detours, go wrong way, in more and more rich experience, it will inevitably be because of one or two times the success of pride.

The following is mainly explained in three aspects:

(a) The impetuous mentality in career change

(two) Beginner Java's impetuous mentality

(iii) Experience more and more, and the impetuous mentality that leads to




(a) The impetuous mentality in career change

Among Java developers, there are many careers that have been turned over from other fields. Whether it's a career change, or a career shift due to the company's transformation.

1. From the Independent career change

Let's start with an autonomous career change, which includes two types of developers:

A class is mainly students, especially the computer software professional learning. Career change is mostly in junior or senior years, because at that time to find a job. These two years, from the Java employment situation, is still relatively good. Many of the original learning VB,VC began to turn java. A class is just the main work. Career change, mostly in a two-year graduation. In particular, after a year or two of work, found that the industry is increasingly depressed, the language is increasingly difficult to find work, and at this time, Java is gradually hot up. So I started learning Java, preparing for a career change or job-hopping.

From these "autonomous career-changing" Java developers, we can see that the career change is very large on the one hand is "interest" driven. Whether it's to get a good job, or to get a good salary. This is understandable, I used to learn Java because of employment.

But because of this, learning Java is likely to have a large "industry epidemic." For example, now very popular struts, there will be a lot of people just contact Java, began a swarm of learning struts, whether or not understand the servlet, whether or not understand Java/io.

This kind of impetuous mentality, very easy to be affected by outside environment. It is also easy to learn to correct later, of course, it is easy to make the following (iii) mentioned because of more and more experience and impetuous error.

There is a very philosophical word, called "we live in this environment, in order to survive, we must first adapt to this environment." In the face of this impetuous mindset, we may have to say for the time being-"If you have time, please go back and take a moment to look at the Java basics." Even if it's just an amateur time, take a look.


2. From the transformation of the company

Then let's take a look at the career change that is caused by the company's transformation.

Companies in order to develop, transformation is a more normal commercial behavior, whether from Java to VC, or from VC to Java. Anyway, the end is the same, career change. Let's see what kind of impetuous mentality there is.

The main performance in, after a simple training, can use Java development, to meet the company's application. At this time, the developer will think Java but so simple: anyway VC and Java are object-oriented, anyway JSP and ASP are programming, long and long, this mentality will spread, and then the result is not think enterprising. Plus a very popular saying "What matters is thinking, what language doesn't matter".

In the face of this situation, there are some difficult to deal with is that, influenced by previous experience, the average person is hard to persuade this type of change: For example, you learn Java one year, one of your career change colleagues in the previous years of other language development work, now began to switch to Java. This time, if you tell him that you should learn Java, you should pay attention to this one. So what do you get? In addition to getting other people's roll, it's hard to get another one (of course, if you're lucky, if the co-worker is a humble person, it might be a different story).

Of course. For some very solid basic skills, thinking is also very active developers. Switching to Java is just another language. Although the Java system is very complex, but for them, understanding or application is only a matter of time.


(two) Beginner Java's impetuous mentality

The first to learn Java enthusiasts or developers, most of them are more open-minded to learn. But in the learning process, it is easy to be misled by other developers, or the impact of the industry wind, of course, will be some of their own "anxious" psychological impact.

1, because to learn too much, and impetuous

Java is now an increasingly large architecture (associated with the Xml,web service is also the rapid development), light J2SE has more than 10 core APIs, let alone the application of Java EE. All of a sudden the face of so many APIs, many beginners will face the "how to start, how to start" problem. And a lot of beginners, after learning one or two APIs, began to "swallowed" the study.

Many people, when the RMI is still vague, to talk about what EJB. When the web app doesn't know what it is, ask "How to configure WebLogic" everywhere. There are so many people on the forum.

Now there are more and more branches of Java, some APIs may have a variety of implementation packages. As developers, both beginners and experienced people, we can not in a short time, master all (or even most). However, in the real world, most cases require a combination of multiple components or APIs, which requires a lot of learning and the ability to use APIs in a relatively short time. This time is a solid basic skills and the embodiment of learning ability.


2, because of the success of one or two times, and impetuous

In the forum, often encounter such a post-"I have learned JSP, what to learn below." In fact, many beginners, asking such questions is also an unintentional loss, but also the desire for new knowledge. Like a drifting in the Si gu of the vast sea, if no one at this time to guide, it is really difficult to find out what direction to swim. However, for any developer, you should never say "finished".

Unfortunately, in reality, there are a lot of developers, always after one or two of success, become more and more impetuous.

As I in the "lead" in the example, in the JSP to write a few pages, I think mastered the JSP, with JDBC will operate the database, think almost can be, according to gourd painting scoop to write an EJB, the self-proclaimed master of EJB, there are many.

(iii) Experience more and more, and the impetuous mentality that leads to


If this time, still some impetuous. It's really a pity.

For the more experienced Java developers, experienced a beginner's turbulent period, should be more mature and stable. At this time also will cause impetuous mentality, I think the biggest possibility is a kind of pride of mind direct performance.

On the topic of pride, I will not say it.

In the face of this situation, can only one sentence-"mountains outside the castle Peak Louwai Lou."

I would like to go on to write a section on "(iv) the misguided attitude of the academic atmosphere". But think about it, some of them are also vague, after all, the vision is not so high level, also stopped.

In reality, I think far more than I mentioned, these are only some personal feelings, it is inevitable that some of the thinking is not comprehensive. If there is anything wrong with the words, look at treatise.

Write here, think of the primary school, the front wall of the blackboard is always affixed with eight characters-"good study, Day day up."


By the way, to say so much about "fake arrogance and abstinence" is not to make people too cautious or to learn in a step-by-step manner. In reality, you can never look at Java school jsp. But in learning new things, you should pay attention to remind yourself "constantly make up for the defects of the foundation." This passage, originally intended to be placed in the follow-up "Persuasion chapter" in. Just because in the "introduction" of the discussion, there are netizens mentioned such a phrase-"so far has not learned the part of the Java EE, always feel j2se learn well." I think such a mentality, also big can not need. Although many of the Java EE needs to be framed on the basis of J2SE, it is not necessary to j2se more than 10 core APIs straightened after the Java EE API (such as Jsp,servlet or even EJB).