"The Road Method Natural - Object-Oriented Practice Guide" can be available in October. On the Internet, there are a lot of friends, I also sell themselves here, post two comment articles I wrote. Programmers need an object-oriented practice guide?
Wang Yougang August 2004
Squad: Of course, of course, the object is the same as Wang Fei's song, listening to time and space, clear, tempting, listening to more, finding that it is so far away from us, it is indispensable. You must have a countless object-oriented noun, you must have a certain amount of UML's icons and tags, you can't work hard, when you face the actual software development project, you don't have a special helpless, don't know Where do you start, or a blank in your mind, can't wait to return to the feeling of compilation? Why is that? Theory is difficult to put into practice!
Contra group: wrong! Your argument has committed the problem of Nanbei. What we have to discuss today is whether programmers need a book for object-oriented development practices, but you have said for a long time, it is to contact practices in arguing the object-oriented theory. The theory is of course to contact practices, but we must never need such a "practice guide"! Theory is the guide guide, theory is everything, theory does not need any extra deduces! When the programmer is familiar with Jacobson or the like, as long as it is constantly exploring in practice, it will continue to sum up the experience, naturally, it will find the correct road, and naturally will be mature every day.
Square: Dude, you are too big! Do you think that all programmers can do not have a good news like you, and give it a non-three? For most people, from the ignorance of ignorance, there is a guide to books. From a stomach ink to a living, the guidance is also required - this is the value of "practice guidelines" or similar books! I will give you an example. The people who begin to learn to be object-oriented. It is easy to remember the basic steps of the use case analysis, which is easy to master the drawing method of the example map, but I have seen many programmers who have just learned the use case analysis in real Only one of the projects, two cases are thoroughly lost to the object-oriented demand analysis, and then immediately invested to the traditional, extensive demand analysis method - organize (actually a repetition) user needs, compiling the text And start design. Don't you think this is because they lack effective guidance and help? If a book tells them how to use the theory of example analysis, how to translate into actual demand analysis results, can you help them rebuild the confidence of the object?
Contra case: Pay attention to it, you mentioned the use case analysis. First, I have to tell you that use case analysis is more than just a demand analysis method that is limited to object-oriented domain, but an object-oriented demand analysis technology not only contains this type of use. Second, I have to inform you that you have a short-lived problem as the Song Guo in ancient times! Even some beginners can't experience the true value of the use of technology in the first few projects, even if some programmers will face the high-class high-oriented high-end, you don't have to force them to read a so-called "guide" "- No book can make the rookie a master! For real programmers, practical itself is the best teacher, is the best guide! When those who don't want to use object-oriented technologies continue to touch the wall during the development process, after they constantly encounter setbacks, they will naturally think, to let themarly learn the theoretical theory truly role - this kind of understanding is produced, they I will not be exhausted in my life!
Square: How did I encounter a brother? I have never said that the case analysis is only applicable to object-oriented demand analysis. I have never said that the object-oriented demand analysis is only used to analyze this Huashan Road, but you are eager to refute this "Monitor" that does not exist at all! Insight is yourself, talking about it, isn't it? Why do you say that "those who don't want to use object-oriented technology" will definitely touch the wall in the development process? Object-oriented is only one of a valid development method. Many programmers using structured programming can also develop elegant and efficient software. What I said "Practice Guide" only applies to programmers who choose to object-oriented technology. For another example, I learned that OOA knows that OOA knows the analysis model, but can they understand the role of analysis model in software development? Will they use the necessary means in practice to prevent analytical models from being too large or too simple? Do they know how to verify the effectiveness of the analysis model? Paralare: Please, I have never said that people who don't use object-oriented technology will have to touch the wall, but the gentleman is frank, I will not be used in general. Don't mention what OOA I will mention me, what to analyze the model, I will come to this. Most people don't really understand the meaning of OOA, they can't even say the essence of OOA and OOD. They don't know at all, the method of refining analysis model, there is still a considerable debate in the object-oriented theoretical circles. OOA is one of the most important concepts of object-oriented technology. If there is no specificity of the theoretical guidance, beginners will be dizzy by various mutual contradictions. Therefore, learning OOA is the most important thing from one, but insists that there is a kind of theory, don't manage other statements. A classic theory book is essential, but what is the "practice guide", I am afraid it is suspected of being added?
Square: Please don't judge your own narrow experience you are not necessarily familiar! How do you know that the author writes "Practice Guide" will give beginners to add awareness burden? This guideline book is itself a good helper for classic theory books, you have to add some coffee partners, why can't you read the master's work, increase under a "Practice Guide" What is the ability to absorb and transform knowledge? In the architecture design, so many times, the programmer of architect designers know that we must patiently learn a variety of architectural design methods, including architecture, subsystem architecture, hierarchy models, etc., but they I saw the classic theory books on those boring bar frames, and I couldn't afford my spirit. At this time, if there is a "Practical Guide" tells them: "Don't be discouraged, architecture design is not so difficult. Hey, for such a practical case, you only have such a case, then this, your software has Can be comparable to Oracle, Apache or Eclipse. "- that is how good!
Contra group: Don't make a dream! Still comparable to Oracle! For most object-oriented programmers, you can design the software architecture into a Chinese rule in the textbook box. If you don't have a big error, you will be thankful. Software architecture This thing is really not all people who want to play. "Ghost" like Bill Gates, of course, you can self-seal as "architect", but more than 90% of the mediocrity, it is best to be old and old, the theory book, the seemingly boring, the essential use of infinite classic architecture For example, three layers, such as MVC models, such as AOP architecture, and more. In this regard, the programmer does not need "Practice Guide" at all!
Square: Calm! calm! Dude, you said that the theory of architecture design "boring", one side, the programmer "old man reciting", are you not drinking water? The "Practice Guide" in my mind is a knowledge and experience that has boring, abstract theory into blood, and has become a book of fun! This book can not only reduce the difficulty of theoretical knowledge, but also inspire the programmer in the bottom of the heart. Yes, inspiration, everyone is inspired, but some people are not conscious. For example, when we read "Design Mode", we admire the four unparalleled masters to the extreme, and it will not summarize such refined design patterns and frustrate. But you think that there is no, "design mode" is dead, the programmer is alive, the software is also live. If you take it out of your heart, you can use it in a software design process with the help of a "Practice Guide", and you can not own and Does the master's sense of accomplishment and pride? Contra group: Forget it, you are ill. Take me from Australia to study, you are "the son of the only girl - not saved". Also "design mode"! Do you know what is "design mode"? Do you know how many famous scholars have been studied by how many famous scholars spent many times? That is in the object-oriented field, it is very correct, very glorious, extremely great design model! You actually want to combine your inspiration with the design model, you still want to "invent" design mode? You are simply tarnished the holy soil in my heart, what is the difference between your practices and those who are crazy, brutal? To make me see, you said that most of the "practice guide" is a propaganda from the extraordinarre evil.
Square: Ah, I finally saw your true face, you were originally a complete fallen, thoroughly fakeful Guardian! Do you know that the theory is developing? Do you believe that all things are in the world? I am not willing to discuss problems with decaying molecules that are medieval. In the object-oriented world, no technique is absolute and eternal. Take the UML language. Since birth, people have summed up many ways to use UML, such as using UML as "sketches", take UML as "blueprint", take UML as "language", and many more. Around the standard of UML, derived different design principles and theoretical systems, such as MDA, which are recently fried by people. Different methods, different theories have advantages and disadvantages, no one is universally applicable and absolutely correct. In such cases, the programmer's subjective energy is particularly important, and they need a "Practice Guide" to help he complete the key choices in software development.
Contra group: "Fallen"? "hypocritical"? "decay"? You are too young, my old man is! I will smell the chicken dance every day, keep the latest object-oriented theory, read all the theoretical books and theoretical articles I can find, whether they are the classics of foreign masters, or works in domestic peers ...
Squire: Then why do you want to reject an object-oriented practice guide? Is it because it has the second word "practice"? Even if you want to criticize it, you always have to read it before you have the eligibility. Specifically, have you heard of a book, is the name of "Daofa Nature - Objective Practice Guide"?
Contra group: "Daofa Natural - Object-Oriented Practice Guide?" How did I not hear it being said? What book is this book? Have you seen?
Square: I have never seen it! But I hope it is the "Practice Guide" in my mind. At least, I will find it carefully to read it. Do you know? Contra case: I? Maybe ... 咦, hit! I suddenly remembered, since you have not read such a "practice guide", then we are discussing for a long time, fighting face, is rough, this is nothing to find, is it full?
[Note: The above debate process is the author according to the imaginary situation and role virtual, does not represent the author's position and point of view. In fact, the real idea of the author is that all beginners who like to object-oriented technology can find valuable things from the "Road Method Nature - Objective Practice Guide". 】
