software development efficiency

Quite simply, the efficiency of development is determined by the amount of engineering and development time. This question is so simple that no one is willing to go into depth to discuss what the specific amount of engineering is.

Of course, there are many people who study software engineering who have done research on engineering quantities, and there are many elaborations. There are also many quantification methods, such as function points, use case points, story points, in short, this point, that point, there are a lot of points. But people often overlook the big chunks, that is, the amount of work that learning needs and related knowledge bring.

A requirement is a pile of knowledge, and solving the problem the requirement raises requires some knowledge. This knowledge is not generated for no reason, and it is not born in the programmer's mind. Both learning and mastering them undoubtedly take time.

The good news is that people have memory and can learn and master knowledge. That is to say, if this knowledge is learned once, and the project does not need to be updated objectively, this knowledge can be learned by the program developer at one time. Therefore, experienced developers and development organizations will be stronger in openness than inexperienced ones. And a project, if you need to learn more things, the greater the amount of engineering development.