Views on recent discussions

The recent discussion is intense. In my opinion, there are two main types of thinking: academic research and practical application.
My point is to support the latter one.

For example, whether book. Save () Is Object-Oriented or not, and whether the usage is elegant. For example, whether object-oriented must be generic or not is object-oriented. Based on this topic, there have been at least a dozen posts and thousands of replies to the debate. I think no matter what conclusions you draw, there is no value for me, because it has no practical significance for the troubles I have faced in product development, project implementation, and team development models over the years. There is no silver bullet, but you have to find something powerful to solve the problem.
Just like life, there must be bread. Let's talk about spiritual construction. For software ideas and development models, we should first discuss how to use and practice, solve practical problems, and discuss the advantages, nature, and use and improvement of such ideas in some scenarios, in this way, the development rules are met. In the end, we cannot talk about the actual problem. It is a kind of thinking about the Plato. The progress of the software industry is now fast, and may be a great leap in the history of software technology. The side effects are impetuous attitudes. Are you willing to be the beneficiaries of this wave of development or stepping stone of others?
Therefore, my point of view is to be down-to-earth and discuss how to use these ideas based on the difficulties and confusions in the real development process.
Maybe at some time, the result of practice is that object-oriented + procedural development can achieve a good purpose. After a while, you will feel that those procedural code is wrong; maybe you think you have used object-oriented development to develop a project. After a while, you may find that the design is stupid. Incorrect object-oriented understanding makes the software increasingly difficult to maintain, then you can find that you have a deep understanding of object-oriented, or you should not use object-oriented thinking in such a development environment. Based on these experiences, we will talk about whether or not we should be object-oriented and how to use inheritance polymorphism in some scenarios. In this case, no matter whether we declare our own opinions or disagree, they are all supportive and most meaningful to themselves and to others. This is the discussion.
Without any support, it must be a bit of a chat, because in the future, it is very likely that I will deny these ideas. Such ideas, ideas, how to persuade people and discuss them with others?

A technical idea is to get started first, learn how to use it, practice, think, and Master how to use it, and then reflect on what conditions are available and how to use them flexibly; finally, it is integration. You can iterate in the previous process to further understand its nature, think about its improvement, and combine other ideas with it to think and use it. At present, I cannot see clearly the corresponding level of discussion in the blog Park.

The scope of the design is not only the design of the technical framework, but also the business design and other aspects. Otherwise, what is the software product. Without talking about technical ideas in actual use cases, it is easy for technicians to become an ideal technologist. What are some typical performances here? The technical staff are seriously resistant to demands and demand changes. The management personnel blindly think that technology is the source of solving all problems. Currently, the product is poor only because the technology is not used well, without being flexible, I thought about how to improve the product. I thought about whether the framework should be changed or not, and whether it should be implemented using another technology.
From the development of the development model, we can also see that the waterfall model to the iteration model are now agile, and the matching process starts from the demand and continues to iterate in a small scope, don't worry about the demand.
What is the field-driven idea? Isn't it also a string from demand to development. The topic-driven book has already explained the topic-driven thinking in the previous chapters. Why are there so many additional chapters, it is to instruct the team to use various possible puzzles during the process.
Looking at Martin Folwer, the design pattern goes to parsing Eclipse, enterprise application architecture, and analysis pattern, and the layers are becoming more and more concrete.

The overall environment tends to focus on specific actual problems and apply various contexts closely. However, here, we feel that we need to discuss empty discussions that are separated from the context to the end.

Recently I talked about the Java open source community.
Old Java qualifications, many projects, massive and micro-sized, successful failures, various industries and sectors, with so many foundations, the Community is filled with various ideas and discussions; the topics of discussion and exchange focus on practical application and ideas, which is also normal. The result of a large number of practices must be the collision and evolution of ideas.
For a large number of open-source projects in the Java Community, my point is that these are basically the results of gathering the expertise of the masses and numerous project experiences. Therefore, please treat them with respect and seriousness, even if it is not suitable. net, because the more you take it seriously, the more you understand and learn. Marx has written his own theories and has studied and treated Ancient Greek and German classical philosophies carefully. Although these are not necessarily truth, Marx has obtained his own theories.
When. Net was young and moved open-source projects, it was standing on the shoulders of giants to make itself develop faster. I am afraid some people did not understand and digest the ideas and experiences in open-source projects, so they could say no to it. I would be happy to read this article carefully if I had thoroughly studied all of them and then talked about their advantages and disadvantages. What solutions should I use in. Net.

. Net lacks a large number of project applications such as Java, So Microsoft ERP has four sets at a time. In the early days, finance also wanted to buy but did not buy them. MBS vigorously entered the enterprise application market. Microsoft's products also have many things to learn from the practices in the open-source community. Applying for an open-source protocol on their own also hopes to be closer to the open-source community and adopt cooperation rather than confrontation. This is a good practice and is very beneficial to the practical and perfect development of. Net platform related things.
Of course, now. many ideas in the Net community are also affecting the thinking and development direction of the Java Community. net open source ,. net solution to Java implementation, but it is not mature yet. Just because I learned to use. Net for a few years and thought that. Net is strong enough, this is an unrealistic idea .. Net many technologies and ideas require a large number of projects to prove its advantages and disadvantages.

Finally, the larger the upper layer, the more dangerous it is. Of course, I think the foundation is a lot of practical exploration, while the upper layer is the understanding, exploration, and mining of various ideas. Of course, if you have mastered these two aspects, let's discuss which one is the underlying problem. This is indeed a question of chicken or egg.
From another perspective, the experience gained from falling behind is more profound, so the great mistake may be the beginning of great progress. If you are wrong or right, you can only know it after you have practiced it. If you do not practice it, you will never know it. I am afraid that you will not be able to use these things at all, or you will not be able to use them at all. So the discussion is empty or practical, which can arouse a large number of people to practice, which is also very effective. Even if we are building a lot of people with low eyes, after all, it will be useless. You are the boss, you have the say.