Keep your sensitivity to Java-learn how to use it, study it, and think about it

 

Keep your sensitivity to Java

-- Learn its usage, research it, and think about it

 

Author: Hu Great Wall (silver fox 999, james999)

Home: http://www.javafox.org

Mailbox: james-fly@vip.sina.com

 

 

I shouted out loud, hoping that more java developers would understand "what it means, know what it uses, study it, and think about it ". We not only need to explore technology, but also ideas ······

 

This is the small discussion to learn the impetuous mentality of Java http://www.csdn.net/develop/article/21/21764.shtm brother. I was originally planning to write something else. Later on, I had such insights and sorted them out.

 

Let's talk about what happened to you first:

In the second half of 2003, the theory and technology of workflow were more focused, but the updates of new knowledge were ignored. By chance, I found that MDA and AOP have grown up, but I have almost no idea. I have been asking myself for a few days: "Why don't I know?" "Why didn't I pay attention to it ".

However, when I spent some time reading AOP materials, I suddenly asked myself, "why do I need to know ?". Yes, I only need a brief understanding, or I just need to know a little about what problems this AOP can solve. If this new creature is not what I need, or the problem solved is not what I have encountered, why do I need to spend time researching it?

In the next few days, I gave up further research on AOP. Only the concept and problems that can be solved are left in the brain. See it. In this way, I can save some time and invest more in my workflow drill.

 

I thought about it for a few days. Consider why this problem occurs and how to solve it. Here, we have this sentiment.

 

In fact, most Java engineers with several years of experience will suddenly feel that their reflection on new knowledge becomes increasingly slow. Looking back, I suddenly realized that there were a lot of new concepts and APIs in just half a year. However, in more cases, we have to shake our heads-we have too much new knowledge to learn.

Maybe everyone thought of the strange it situation before: Old people cannot beat new people. (Fortunately, the situation has been much better over the past two years ). Although it is a "energy" problem, the sensitivity to new things is reduced. I think it is also a problem.

 

The development of Java in the past one or two years is far more rapid than that in previous years. Whether it is information flow or knowledge breadth, it is larger than the previous years. The following figure shows the development of Java (J2EE) based on some of your own experiences. It is a personal opinion. I am not familiar with the field of j2's because it does not include the j2's.

If we compare the development of Java to a flowing river, the new knowledge (Application concepts, technical standards, and so on) is like a branch of a consortium. As we all know, where the consortium is, the consortium is more or less a "jet stream", a "vortex", and a "wave ". Of course, the more confluence, the more frequent the response, the more intense the response.

 

So how can we better solve our technology problems? This is the core issue I have been thinking about over the past few days. Here are some of my views:

In fact, this is also a matter of grasping the new knowledge. In general, it is divided into four levels: knowing its usage, researching it, and thinking about it.

Now, you can understand the new concepts and technologies that have emerged recently, and simply know what problems they can solve, and analyze whether they need to be applied recently or can be used better.

Know how to use this new technology. Simple applications usually take a lot of time, but it takes much time and energy to think about complicated applications. If you are not sure, blind application and learning will waste a lot of time.

Research: the new technology and new ideas are deeply studied in terms of its principles, framework, and structure.

Think about it: this is the most difficult layer. First of all, we need to study its Foundation. This is a difficult thing in itself. After the research, it is even more difficult to expand or localized the thinking.

 

Therefore, doing well is a key issue for most Java enthusiasts. Doing well does not mean learning much. Each developer needs to analyze their own industries, hobbies, and fields. In this way, when ideas or technologies are innovated, we can quickly identify those that should be focused, those that should be followed, and which ones should be used, those who need in-depth research... that is to say, how can we "Know what it is" and "study it" if we cannot "get it done ".

There are only two purposes for doing so:

(1) Keep yourself focused on new knowledge, new ideas, and new technologies

(2) Use the limited time for effective and reasonable use. From the management perspective, it is called: reasonable resource allocation.

 

To be honest, I really hope that more java developers will be able to "think ". China's software industry needs more talents who dare to "research" and "think", and more research talents who stick to the technology path.