Read the "converted framework" again

There are many development frameworks, components, and components, and the trend is increasing, especially in Java. Of course, this does not mean that there are few other platforms. In particular, the framework is becoming more and more divine. It seems that you don't have to break down the keyboard to solve all problems. For a typist like lazy, I still cherish my keyboard.

Why is the framework turned down? First, the framework is the extraction of code and ideas of the same type of N projects. Of course, it can solve many problems. For example, spring, struts, hibernate, Java EE in the Java World, ADO. NET Entity Framework of DOTNET, MVC, Enterprise Library, nhib.pdf, nbear, and Ruby ror. The other thing that the framework is turned into is the framework. Without a framework, it is not a good architecture. Without the framework, problems will occur in later maintenance.

In the world, there are often more impetuous people than steadfast people. They only use the Framework to "how to use it ?", Regardless of other problems. So that the problem cannot be solved. The problems may not cause project crashes, but it is certain that many projects have version disconnections from management or temporary confusion.

This is especially difficult for cainiao like la. Learning about the framework, but a perfect framework must have at least several hundred KB of code, and the Framework Code is all interface-to-interface. It seems like the cloud is in the fog, smoke a cigarette is more vivid. If you don't want to learn it, you will always feel guilty, as if you are using the bean curd project.

In addition, the general problem introduction framework focuses on configuration. The principle is relatively less, and the code sorting is less. This makes the old man afraid to use it. If something goes wrong, who should I find? This means that you can't start looking at the itch. This is a vicious circle, and I am afraid to use it. I can't understand it without using it. However, experts will not elaborate on it. When the bridge was over, those who did not make up their minds were still waiting by the river.

However, you cannot learn it either. If you are new to Java, it is more difficult to directly learn the framework than to skip the building. DOTNET is better and easier to configure.

What is the framework? It is a combination of code reuse, design reuse, and analysis reuse. The framework is also developed using the simple statement keywords that beginners can see from books. For example, JSP, serverlet, and JavaBean in Java seem outdated, but spring and struts are based on those things, but they are well integrated. In this case, it seems that the framework is no big deal. You can also develop a basic learning model and a design model.

Of course, it is actually not that simple. To develop a framework, you must consider all aspects. And these things won't be pulled. It is important to know that basic things are not a kind of backend, and you may not be able to develop good things without using the framework pages. Design and development are two different things. Some people may think that the design capability is very good. They can draw a structure chart after getting a project, which is well divided by layers. But it cannot be developed. After reading the UML for a few days, you can draw the graph. The practical ability of the graph is much more difficult than the painting.

Sometimes I often think about it, try to encounter various problems, and then learn the framework and design more deeply. If you don't meet your needs, you won't have that kind of resonance. You can back up your endorsement, and you don't know where to use your back-up.
From: http://www.cnblogs.com/birdshover/archive/2008/11/26/1341568.html

 

I am very touched by this very old article. Interesting. What do you think?

Read the "converted framework" again