This concept is widely used. In the article of a friend, I said that the concept has been introduced to many areas in daily life. How is the specific situation, I have no opportunity to go to the admission, but from the spiritual spirit of the Westerners, I want to have this momentum is reasonable.
I understand that the model is a way in which it has experienced experience. For example, design patterns, the system is organized some universal elegant design experience.
As a programmer, "mastering some technique" and "can reasonably use this technology to solve practical problems" is not a matter. The former is biased toward theory, and the latter focuses on practice. The former has received the uniformity of people, and the latter has been ignored. In the project, this situation often occurs, the programmer of the new project group does not receive training in this area, and it takes a lot of effort to find a specific application to implement specific applications using specific technologies. This reduces development efficiency, making the program code obscure, readability, and the critical chance of code hide BUG, affecting the stability and quality of the system. The experienced programmer and programming masters in the project have mastered a lot of experience, but these experiences are personal skills and rarely take out. This situation makes the masters differently, so the code readability they have written is not high. And because of the lack of system communication and finishing, the programming mode of masters is also inevitably existently unreasonable, and may even latency some erroneous steps that affect system stability. I think it is necessary to bring this question to everyone, the topic is called programming mode, hoping to attract everyone's attention.
Define the programming mode as: experience in solving practical problems rationally using specific technologies. Programming Mode This concept should be explicitly proposed to communicate, discuss, organize in programmers. Each project group can summarize a set of programming modes for its own development environment before encoding, requiring programmers to refer to these modes, and quality inspections are quality checks in these modes. Of course, programming mode needs to constantly supplement and improve, this continuous improvement process requires common wisdom of all personnel of the project group. Pay attention to this problem, the quality and readability of our software code will be greatly improved. We can take a step-by-step step on the software development level.
It is often the topic that is often hanging in the mouth is "Indian Software Industry". Some people say it is good. Some people are rotten, but the Indian software has been recognized by the international community, I think it should have passed in quality. Quiet, compare, India and our main differences lies in the foundation of the software industry - programmers. Let a group of Indian programmers solve the same problem with the same programming language, they will find that their programs are almost exempt, variables, program structure, handling ideas, etc., are plagiarism, can be said they are using the same programming mode. Standing at a software engineering point of view, all programmers use the same programming mode as template coding, which is a way to ensure code quality. After all, all software systems are built on the code, the base is not prison, the upper building It is useless to fancy. Software Engineering is a domain weighing and practical, and foreign engineering methods come from practice experience, so it is operative. But after passing to the country, it will become a taste. Many people are more willing to study it abstract pure theory. The final theory can only look, not good.
This may also involve a mentality problem, and the inland atmosphere is relatively floating. It is a bit very urgent. Pay attention to the basic issue of software development, I believe that individuals and overall levels can be improved.
