Recently, I read "Shao Kai: Programmer Culture" in the Internet, some of them, some of them:
"The success of UF is reflected in the programmer, there are three aspects: focus on finance and management software, users demand first, emphasize program reliability."
Here, it refers to the requirements of three aspects: industry focus, compliance with customer needs, robustness and stability of procedures, and this, I think this is actually three different levels. First: Industry Focus refers to the company's decision-making layer for the development direction or in the field of perspective. This is probably unobstructed by the general company employees; second: pay attention to customer needs and analysis of customer needs, this may be " Application Experts, pre-sales analysis or related needs analysts, the emphasis on customer needs, of course, is the workforce of applicants and product managers, because the technical staff will not directly face customers directly They should also be relevant to customer needs or other responses should also be based on relevant development, modification tasks, and the third: many aspects will determine the quality of the code. First of all, the most important thing is the architecture of the system. This is not only the application of the scalability of the entire system. It is also related to the quality of the code, such as the rationality of the code hierarchical organization, code execution, calling efficiency, code reuse ... this To a large extent, the method, method, method, method, in this, I think the system architecture is the basis of all technical support, secondly, good internal components are also important factors affecting the quality of component usage. . In the management system, the database operation is involved, so the design of the database structure, the design use of the stored procedure is also significant for the design of the client program. In a component-designed system, the logic and code complexity of the true client code are very low, which is basically a bonding to many components, and organizations for operation interfaces. Therefore, the design of architecture and components has become very important.
"Another important group is an application expert. Because UF is to manage software, let the programmer who knows software technology is unimaginable, and must first be optimized by experts who know how to apply applications. Application model. "
For this, everyone is basically recognized, the key is to implement the extent to which it is implemented. In many small software companies may have part of these two distinctive positions because of cost or understanding, this ultimately leads to demand or operational processes and operating habits that make customers unacceptable. The understanding of business logic is usually different from the understanding of business logic. The deviation of technicians generated by technicians will eventually lead to customers! This is fatal. See the picture:
The last point is about the PREVIEW CODE and the development document. I found that in many software companies, development documents is usually made by the developers based on the code written and written, or the designers written in early documents, these documents themselves are not strong enough, in subsequent The reactions in the development of its changes to design and code are not synchronized. For longer, the documentation is no longer trusted, and it can only be a secondary document for reading the code. Although the document organized by the developer is synchronized with the code, its readability and conditionality are not strong, and many times is to cope with the higher-level requirements, and it is also difficult to understand, or even see the code. Easy to understand! In the documentation, you must not document for documentation, which not only does not meet the results of the effect, even time-consuming, in this regard, I think the XML document in C # is very good, and it is also easy to develop synchronously in the development person. There is a unified format specification.
