Meeting Summary and reflection

At the review meeting today, I raised a few questions and I will come back to summarize them.

1. After the interface design is complete, there is a question about how the public module for input verification is implemented.

2. Check SQL statements to find logical errors. We recommend that you check SQL statements carefully. dt testing is also a review process of SQL statements. Only by reading SQL statements can you know what the report is going to do.

3. interface and business logic separation issues, some even in the most common main interface mainfrm. in CPP, open the database, read the information, and verify that these actions are incorrect. it completely breaks the hierarchical design, and the MVC separation principle is a big problem. the root cause is that the concept of the design pattern is unclear. The direct manifestation is that the group does not clearly define what classes should be written and what classes cannot be written.

 

In addition, what other colleagues have mentioned is also very valuable:

1. Load the DLL file in the code, and duplicate loading is messy, resulting in low code execution efficiency and large package installation.

2. The configuration file is messy. If a small function is configured with a file, multiple formats are different and the configuration file is messy. The configuration file should be designed in modules or systems.

There are some old problems that have become increasingly prominent.

1. the import performance is slow. This problem is caused by two bottlenecks: High memory usage and slow import of large volumes of data to the database. A fundamental solution has not yet been found, and it will not be so slow as desired. If a solution can be found, this is a major breakthrough.

2. query performance problems are caused by unreasonable SQL writing. Too many temporary tables are used, and the returned data is often operated cyclically and unnecessary Io. this problem can be solved. The problem is that the existing code architecture is already so bloated, and some are still something in the public interface, which cannot be changed. in the next iteration, we can use the best design to solve the problem.

 

In summary, the above problems may not be solved even if the import performance is re-developed. Others can be well designed when a new framework is developed.

 

At the meeting, the boss affirmed my opinion and saw my motivation for studying hard. although I do not want to show it to the leaders, I want to improve my abilities, do a better job, and have a better future, the boss certainly gives me a lot of motivation. this is very important. After doing this, the leaders can see it and give an affirmation. I will also constantly strive to improve myself.

I recently focused on the design model. I saw the design of the factory class yesterday, which is basically a pure virtual function that implements the specified function at runtime. A uniform external interface is provided through virtual functions. I have read about this in Objective C ++ and C ++, but it is not actually used in actual work. Remember that this idea will be used one day, or you can understand it when you see other people write this usage.