When I was in the programmer, I started to chase this API. How to write more optimized, DCOM technology details, and then I found that the product I wrote in order to meet customer needs, but my code is Sticking together, the first feeling is that a function is too long, a headache, and a function of doing a lot of things. These things can be used for a while, write annotations, then meaningful named, manage errors and memory, and then connect these functions together, then I have made these: 1, small functions; 2, write annotations; 3, meaning naming; 4, manage errors and memory itself; 5, process function; finally I found that I can combine into a variety of processes, my program is finally modified, I am very happy. But I found that my interface and my process are mixed together, and another program also wants to use my function, but I have the code associated with my specific interface. I can't even give him together. Because he has his interface, I have already achieved it, so I made these functions and interface control. I made this. My code is easy to understand, even if new employees, as long as he reads business manuals and The data structure, he understands why my code is written. And my function has a clear and unified error message because it is the verification of the parameters and output parameters, so it is easy to find bug fixes. Since my procedure is a small function, there is clear report, so the error is easy to find, after the test group's professional test, my code is very stable, even if an error, it is not spread, it is small bug, There is no big impact on the overall system. Although I have experienced confusion in the process of advancement, I'm drilling in OOP and design mode. But it is possible that it is not enough, you can't understand it. Looking at the source code of Delphi, there is a lot of OOP and mode, and his class library has not changed many years, so it is very trustworthy of OO and model, and is very discouraged. However, the code has to continue writing, and I want to further improve, so I can explore a set of practices. Even from both simple applications, everyone can do. I think my code method can meet the current product manufacturing and have accumulated some precious experience in software performance adjustment. I found that performance is most prone to improve, the most obvious effect is to use SQL Profilter to optimize SQL. Optimize the code, because it involves the business, it is very bad. Optimizing the database structure, because the code is built on a specific data sheet, this is the most difficult place, but I am happy for a long time, I have encountered problems. Because my program makes it better, the customer's needs are really mysterious. I am answering the user's call every day and modify the user's talented problem. I am annoying. So I made a member. I want to really look at how the customer is going. So I understood a lot. I understand a lot of things not to solve technology and software, but the disadvantage of the real environment. But this disadvantage is not a project to solve, this is a complex network. So I am persuading that users don't use software to handle, because the software is dead, and people's practices are flexible. And I found that the user has given a lot of demand, but some demand can't be used once a month, but it is not easy to modify it. Some demand modifications, but in practical applications, it is not feasible. The need is only a way to solve the past problems at all, and there is no actual check.
Some demand modifications to modify the surface problem, and discover the key issues in practical applications, there is no need to mention, so I have made it a summary: 1. Supreme Data calculations and query, there is data networking Sharing, if the demand cannot play software characteristics, it will not be made. So I have revised some less; 2, some demand is surface demand, modified, but also delay the proposal and modification of key needs, so tell the user to modify the core function. But the user has given a lot of demand, and it is not modified. Later, I found that because they didn't understand the overall ideology of our system, they didn't go online, I didn't know if the new function was used. The user is just out of the whole, thinking alone, how do you think, didn't go online, he didn't know the consequences. How did you say it, you have to let him see that he will repent, but have been revised. This often occurs. Finally, I conclude that only three needs were mentioned once, and I was put forward with written, I waved it was not counted. The demand modification of the core function can meet the daily use of 80%. So, I have revised a lot less; 3, and I have accumulated a lot of experience in actual work, write into FAQ, various success cases, let users see how many old software I don't have to solve before I don't mention the needs. Only buy new software help. New software is something that you can't solve your past solution. If you don't solve something that can't be solved, give questions; my product can finally complete the online, so we can have a large scale, but our product manufacturing has problems. Because more customers have more and more, customers' needs are more and more. We need to develop more systems, but our time is limited, our people are limited, and our people are mostly new. How to do. We have encountered a disaster. Our code quality varies from person to person. Our version of our version is confusing. Our document is no one to write, everyone is assigned to the user to go online. How to prepare a data dictionary, how to switch the system, how to record customer needs, how to manage the system, how to modify the code, we don't have any records. At the scene, I can't leave the programmaker. I don't know what to do if I leave the user. There is no information that can be checked. So I did project management, and we lack a lot of specifications. There are thousands of things, first come. Write a document time to meet the experience of doing things. What are the specifications that need to be modified for implementation and code modification? The most probably wrong mistake during this period is central collecting power, and everything must be a master. Subject, regardless of the big things, please. I can't do anything, I have become a firefighter. My team has fallen into chaos, because I have made a lot of thirst decisions in my troubles. I made a mistake again. I said that you can decide to decide yourself, don't ask me, my rights are off. The result is: each matter is made, and it is not notified with each other. Some things don't worry, some have more people to modify, each has a set. I finally understood, I made the following summary: 1. The project manager is a person who has found a power and guides them to do things. If the subordinates don't know how to make, provide a method of doing things in a timely manner; 2. Develop a specification, in fact, it is a method of doing things; Check the result; 4, there is an emergency to make decisive resolution, continue to advance; my team finally calm down, but everyone is very tired. Everyone is tired, but because of the implementation and modification consumed a lot of money, we did not make money, everyone did not get anything. The team is very discouraged and very disappointed.
