Today the mood is better, put their ideas, drawing an analogy to understand what the chart, to share to share, feel a little harvest, to help me tap recommendation, bored, do not look at the content, look at Figure on it, anyway, you also point came in, right.
With a thought or idea, often guided a lot of people, for example, we were young, positioned as a university entrance exam, and has been working from elementary school to high school, lead us to 10 next year continue to progress.
Written procedures are mostly man, a normal man will love beauty, I'll make a comparison vulgar an example, Figure as follows: 
I prefer to tell the truth, do not like people who loaded B, have something to say to fart put that kind, the general wanted to say directly to say, my mind rarely turn a few laps, I encountered setbacks in previous years more, and some began to improve, before you speak, the brain will think about this being said out? What happens? It will offend some people? Will bad ending? Will there be any bad effects, to tell the truth has become somewhat cunning, and become more sleek little.
Different times, different the environment, able to see and learn different knowledge, learn to see too little, too easy to become a frog in a well, learned too much to see, it is easy to understand and consequently , what is not in-depth, no one can come up with decent hand.
In fact, early on, I heard a colleague say we inheritance in C #, what's the interface, it was carefully listened to, understood the feeling, but to be honest, just understand that time had a foggy, I did not even understand very deeply.
You may ask me, what in-depth understanding? I make interfaces for example, I visited our company's chemical plant, chemical plant Zhenhai Refining & Chemical, surprising equipment, large production areas, is to take these devices sold as scrap, enough to make a person a wealthy . So much equipment, how can organically connected together? Made from crude oil in a variety of products to? When these hardware devices, software as a system, we will think of what?
1. The division of responsibilities clear principles: Each device has a clear division of labor should clear functional positioning, doing this, they should be doing, duties and responsibilities can not mess, you can not expect the car to fly, aircraft seabed it, the doing of it should be doing? Do not write too long a function, also have this flavor, should be doing all distinguish between good, do not write the code out of a thousands of thousands of rows.
2. Input, output clear principles : Each device has a clear input and output, or even have a threshold limit, strict output of the input parameters, what should flow to come in? What kind of processing, and finally flows out of what? To small talk, every day we wrote a similar function, to big talk, which is similar to a sub-system developed by our company, each function, each subsystem should have a clear function positioning, should not be repeated and should not be haphazard .
3. Interface specification principle : the inflow of caliber, thread, material, outflow diameter, thread, material, etc., should be the norm in some industries, otherwise after a device architecture is completed, the next device to be flown to deal with, it is not no flow go on? Or may use a special intermediate pipe, these two devices are connected, the pipe 2, with these devices may have standard connection, the computer as some of the same adapter, e.g. usb to what what the like.
4. Alternatively, scalable renewable principle : a large chemical plant, tend to make some repairs, the upgrade of a device or a device, you can not ask all the entire chemical plant upgrade, it is not a joke, like the establishment of a chemical plant on the scale to tens of billions, this money is used to pull the train, few cars can pull in, do not want to update to update, and do not want to, and do not the.
For example, a screw our car is broken, I can choose to screw A company of the same type, screw B produced by the same model can also be used, and this is because these screws, can have the same function, can meet requirements of the specification.
Of course, more to talk about, though, like the program has nothing to do, but you have a deep understanding to this extent, and the interface is used to do in the end, you may understand, and speak to others can be made very pass, since I visited after the chemical plant of the field, my body and mind feel really improved a lot, gave me the inspiration for a shocking, let my imagination completely let go, I felt that moment, I had a big sublimation .
Our software developers need to go a long way to go, compared with the traditional industries, the gap is still some obvious, after all, many other industries have developed hundreds of thousands of years, the software industry is only just a few years, many of our ideas, thoughts are sublimation from the need to refine some traditional industries.
Learn things is not much, and now the network knowledge is too rich, you will never learn to finish, but you, as a developer, some content is necessary to understand, you looked 100 knowledge, but knowledge of the nature of these all the same, that you look at 1000 useless, are running in place, there is a qualitative improvement is difficult.
If you are a beginner, I suggest a few points of knowledge you need to know: inheritance , interfaces , reflection , commission , design patterns , etc., and some hope to add with the look, the moment I can not remember, is the most basic of those.
Some people work for five years, in fact, with the first year's level is the same, are marking time, and some people worked for three years, the level is high, because he is improving every day, every day learning new knowledge, different knowledge, every year a qualitative change, not just the amount of change.
Although the practice is very important, but there is a theoretical guidance, the concept of the guide, you can make sustained efforts for several years, will support you complete your ideal mind wants to achieve the function, purpose and so on, just like the original communism , so many people go to desperate efforts.
Write programs, too, we need to have a clear philosophy to guide, so that we are not easy to get lost, there is a goal.
Attach several chemical plants picture for everyone to imagine, our software system integration and so on is not the same as a chemical plant? There are many similar places ha ha, the day's work, tired and take a break, some fun.
REVIEW:
Crazy .NET architecture background generic rights management tool demo version 2.0 to download
a step by step teach you how to use common system permissions crazy .NET architecture - how to control user permissions menu displays
a step by step teach you how crazy .NET architecture a rights system - call privileges on a page to explain
step by step to teach you how to use common system permissions crazy .NET architecture - call permission data sets permissions to explain the
madness .NET generic rights design C \ S Admin, B \ S to call the front desk of the source sample program source code download --- authority to operate crazy .NET generic rights design C \ S management background, B \ S front desk to call the source of the sample program source code download --- role permissions crazy .NET generic rights design C \ S management background, B \ S sample program source code source code to call the front desk to download the data set of permissions --- Taobao address: http://list.taobao.com/browse/0/n-8ddf3d8a90550373fa749337efe29f03---- ----------- 40 - commend-0-all -0.htm
Reproduced in: https: //my.oschina.net/iwenr/blog/227773