Experts' fear and expert's "anti-terrorism"
Mengyan
The People's Posts Publishing House recently published a book called "Application MDA". As far as I know, it is the first book for the first introduction to the MDA concept. At present, MDA is still in the state of "paint is not dry". For me, it is urgent to establish a preliminary impression of this technology through reading some information. Therefore, when I read this book, my purpose is very clear. I want to know if MDA is an answer, then what is the problem? I thought this question should be very simple. After reading this book, I feel that things are actually not simple. Mr. David Frankel, the original author, is an active molecule of MDA movement in OMG.
In this
Mr., I don't know, there is no further detailed introduction in the book. From this book's overall layout, the author seems to have insufficient experience in the overall situation. Of course, any kind of reasoning people will not expect to truly master MDA application technology through a 328-page book, this book is not certified. However, Mr. Frankel mixed a lot of background information and personal discussions in the narrative, which is precisely what I like to catch. The biggest advantage is the feelings behind the text, which not only allows readers to receive the techniques described in the book, but also leak some small secrets or even secret. For me, these secrets may be truly valuable and worth discussing. Mr. Frankel looks a more cautious person, nevertheless, he still gave me a hint. Show this: "We have to make this conclusion: our only forecast we can make for the platform of the platform is that things we can't predict will happen. Even IT managers have the right bet on the platform The platform is not too likely to keep it, but will evolve over time to almost completely different new platforms. Even if the manager's guess is correct, the code dependent on the platform may also be too fast, fast It is a heartbreaking. "I am really meaningful, isn't it? Mr. Frankel is not controvers, because he is here to use "IT Manager" to take a spicler, but no one can see it. In fact, he is saying "IT Technical Experts". Despite this, I will leave this little unexpected white, and Mr. Frankel has disclosed this today's software technology field, that is, the "expert class" in the field of software development has been psychologically depressed. Fear. Since the author doesn't know, then this conclusion can only be my impression. The impression is impression that it is not easy to explain. The first problem is to demonstrate that there is a so-called "expert class" in the field of software development. The noun "class" is really not good, I even difficult to explain the difference between it and the more difficult "class", so I don't want to fall into the debate of this problem. However, there is a group of so-called experts in the field of software development, and those who have a technical idea that they have considered high people through articles and books and speeches, those who have surface confident because of their previous success, those who dare to "literati Light "and there is a little" personally "capital, if you admit that these people have indeed different CODERs who have just entered the battle, then please temporarily accept this premise. In this circle in software, experts are looking up. However, these people who make people look at it today is in fact, in a deep collective anxiety and fear. Yes! These food and clothing are worry-free, arrogant, the emperors of the words, the experts waiting for them, they are fear! Since the 1990s, a basic phenomenon in the software industry has become the more and more reforms of the basic platform and tool technology, exceeding the expectations and willingness of anyone, but also exceeds the scope of the individual. In just more than 10 years, basic technology has experienced three-oriented object from the object-oriented-oriented object from the object-oriented, from the object-oriented component, and there is a GUI revolution, 32 revolutionary, relational databases. Revolution, Web Revolution, Migration to C and Java, Design Pattern Sports, Open Source Movement, Object-Oriented Battle, Distributed Middleware Battle, J2EE Battle, COM and Windows DNA's flower, VB developers Faced .NET messages, etc. The development of the software industry is basically in the strategies driven by the rapid transformation of platform technology.
This rapid change makes it today, and it is often abandoned tomorrow. Some people are still complacent today, and will face the destiny of abandoned destiny tomorrow. Every change in the software platform technology, every tool war, and there are thousands of sad stories. How many people fall from the peak of honor? How many people have to swallow bitter mood, throw a few years of hard work, all overturned? How many people have easy to say "must work hard to keep up with the times" nonsense, and grow more and more powerful courage to fight the rivers and lakes? The rapid changes in platform technology, exceeding everyone expects, and its revolutionary and subversion makes the knowledge and experience of knowledge and experience in this industry, the difficulties of technology accumulation, and reach the desperation of the industry to feel humiliated. The practitioners of the entire industry are as if they stand on the summer of Greenland, which is full of fear for fear, and they look for more solid floating ice, and take power. However, if you even have a giant floating ice such as MFC, VB6 and CORBA, now face the danger of disintegration, then what can you trust? In the book, Frankel said: "Homer describes the story of Si Sichi in his epic, he must push a boulder in a hill of Hisis, but whenever it is close to the top of the mountain, the boulder will roll down, so Sisifus's bitter is never end. Today's IT manager is a modern version of Siivus. "Yes, this is the fact! You think that those "master", "experts" in the field of software development are really warm about the new platform revolution on the big company in a wave of waves? You think that the propaganda slogans on "Improvement Development Efficiency", "make your work more easily" really let experts women live? They are just a laugh! Its inner anxiety and fear are the basic truth. Yes, there is indeed a small part of the newly involved in the world, the arrogance, the passion, but this is just the beginning of the next tragedy. Any professional area, only keeping the opposition and unchanging opposites, there is accumulated, and there is something to abandon. The software technology is used to rapidly oscillating on the basis of platform technology, and there is no effective way to isolate such shocks so far, so that this shock is seriously affected by the entire industry and expert class. This situation is not a beginning, Frankel reviews the rule of Cobol language in the commercial host system in the book, and the DOS era of more than ten years, this is the history of software development. Gold period. However, in recent years, the glocking of platform technology is too frequent and intense, and the technicians are exhausted, and all efforts to master the technical features of the platform, completely become the slave of documents, and there is no more powerful force to consider truly important technical issues. What a serious situation is this! As a group of software development experts, the number is still relatively small, even if it is serious, it can only take "artificial knife, I am fish meat" for them. Most people use two ways, one is deeply drilled into a certain segment, even simply reform, protecting themselves in other industries (rather than software technology). Another method is the choice of the brave, that is, constantly catching up with the wind, fighting for the tide of all ages, or changed a perspective, willing to be repeated by each era. However, with the number of experts groups, when it is sufficient to form a class, escape and passive attitude are too weak. At least in the field of software development processes and methods, the vested experts have begun to try active attacks.
Instead of derived from the technical wave, it is not as directed to the palm of the palm, which is not as directed to formulate the rules of the game, establishing the professional class in the anti-tread, stabilizing the software technology industry. This is one of the key destinations of MDA. It looks very good, but what is it? Basic ideas are very simple, Andrew Koenig once quoted an English writer: "Increase a indirect layer, this is a solution to any problem," and pointed out that this sentence is that the statement of the bureaucracy of the self-expanded bureaucracy is placed in software field. It is indeed a rumor. Follow this rumor, experts are ready to create an indirect layer, isolate floes under this layer, so that you can start, and you will worry about it. "MDA is to use the modeling language as a programming language, not just as a design language." Of course! If the modeling language can be used as a programming language, the change in the base platform that is mainly used primarily through programming languages will be largely isolated under modeling language. "MDA is unintentionally uncommon, so that other methods have been eclipsed, but in contrast, it complements other methods." Of course! MDA wants to make other methods become ice floes below, let me go to collapse, kill each other, I can't move. "Modeling language programming can improve productivity, improve quality, and make software products longer." Of course! Only by providing higher productivity can we obtain more powerful support for more powerful people. Only under this supported shelter, the interests of the expert class can be maintained. It can be said that the goal of MDA is very clear - through the establishment of new ideas, technology and tools, the "Software Design" is turned into one and writing code, truly independent professional, through specialization, to prevent lower layers Platform technology constantly oscillating and even subverting the accumulation of experts in expert class. Therefore, this is a professional division of professionalism with specialization to maintain professionalism, fighting professional fear mentality. Of course, this definition is not strict, formal. When in the face of the audience, we need a reasons for more crowning, such as promoting software project progress, improving efficiency, and improving quality. But I think "confronting the fear" This psychological level does not have any embarrassment, at least in my opinion, this is the reason for the bright, no need to cover up. Moreover, from Mr. Frank E L, he can't hide it. The MDA is not fabricated in air, it is the inevitable development of traditional software engineering. Traditional software engineering (corresponding to the current popular agile method) is essentially mimicing civil construction projects. Civil construction projects, the opposite of many people, has always emerged in a lot of innovative technologies, however, the emergence of new technologists in this field is almost always one Good things, they never need to worry about the emergence of new technologies to subvert their professional status. This expert in the field of software engineering is envious. They have worked a lot of efforts to try to solve such problems through research on the development process, but for software designers combined with technology, the software process is tantamountable, and there is no problem. MDA wants to express the essential tools that belong to software design, as if architects only need to draw architectural paper, the structural staff only need to draw structural drawings, in software engineering, engineers use MDA, only The model is required to be constructed. With a model, the redeementation of software designers dreams of: no longer the structure and design of the software depend on the lower platform, but the lower platform is forced to meet the needs of the expression model.
