Yesterday I wrote"CodeThe code behind ", I began to think after work, this approach is too general.
What is the code behind the code? Currently, frameworks are constantly emerging. Net framework1.1 is not completely visible yet. Net framwork3.0 is available, and WPC, WCF, and WWF business model concepts are also available in version 3.0. This is only Microsoft's. There are also sun and others.
In the face of such a large knowledge base and a knowledge base with a high elimination rate, how should we study the code behind the code?
There have been too many things in the past few days, and some strange ideas are always coming out of my mind. We need to draw DFD diagrams in the system design phase. In fact, this diagram implies the essence of our work.
What we do with development is data conversion and data transmission. Data conversion can be divided into physical form conversion of data and logical form conversion of data. Here I emphasize physical form conversion of data (logical form conversion is related to system logic design)
We can figure out these two things. When we face those complicated frameworks again, what are our fears?
However, it is difficult to understand the two things"