Historical product conceptual integrity

I have been bored over the past few days!

First, the current project is in the testing stage. due to some reasons, many module interaction problems have been found. Now we can "Assemble" these modules into a decent system. These problems must be solved, and currently we can only discuss with other developers!

Seven people participated in the design of this project, including all developers of the Development Department. At that time, we first discussed the design of the entire framework, and then divided the design of each module into one or two. Then we went on to have a meeting to discuss and discuss it, that is, everyone writes their own module interfaces into workbooks (some of the internal design of the module has documents, and some do not have documents, because the designers of each module are basically the coding personnel of this module, ), and then everyone starts to implement their own modules. Later, due to insufficient manpower, I recruited several code writers and assigned them to the persons in charge of each module to assist in coding. In fact, there are only three persons in charge of the module when they enter the encoding phase. What about other persons? Two employees left the company. One was the company leader who did not participate in the actual code. The other was because of kaobo, who did not have time to participate in development. One of the remaining three members is the development team leader, who coordinates the development work of the development team, and of course participates in the actual development.

It can be said that there is no real product owner (or the chief designer) throughout the development process, which is used to take charge of the overall structure design of the product, the interaction between modules, functional design, and the trade-off between implementation solutions. He must have a good understanding of the entire product and design scheme. He can leave no code, because the work of maintaining the entire product design scheme runs through the entire development process, and the workload is huge. He is the person who maintains the conceptual integrity of the product!

There are still many problems! In the near future, I will take the time to sort it out and find the root cause of the problem to avoid making the same mistake again!

I bought the Mythical man-month that I bought last year. I didn't understand it at that time. I took it out some time ago and finally finished reading it completely.

Why is the new version of man-month myth available in 20 years, and it once again caused a great sensation in the industry, because we did not learn from the lessons learned by our predecessors 20 years ago, making the same mistake again and again!

......

This project is a secondary development kit. After that, many projects will depend on this. The Secondary Development Kit makes it difficult to predict that projects dependent on this development kit will bring people into the new "tar pit ". I do not know when to develop the second version, at least this year is unlikely.

Overtime! Overtime!

(Sorry, the source of the original article is no longer available .)