Two years ago, I was fortunate to join an industrial first-class company (so that I thought it before.: P), when the company was quite a master, everyone has a wide range of the company's library or the game engine And a warm discussion, with the progress of the company's project, everyone has made a lot of efforts, but it is finally unable to see what results. After a year, the company has come to a few blood youth, just from the school, leadership decided to let them Responsible for a project, their enthusiasm for establishing reused codebases is like the original. I observed 1.5 years. Finally, I gave them the conclusion that they were more fail than us. These two incidents have been I am in my mind, I feel very much, I finally can't help but write it. :) Because I mainly talk about my personal project experience, so I have to introduce the project background. The project I said is mainly referred to here. Large game project, the development cycle is generally more than 1.5 years, C / C
Code 300,000, the program participating in the project is generally about 5 people. Here I mainly want to talk three points: 1. Write the code that can be reused to the developer's requirements very high. Write a reusable code Mature developers needed. The so-called maturity must first need to have a wide range of understanding of the history and status of the technical field of themselves. Secondly, it is necessary to develop comparable projects, it is best to be similar, so that What do you need, how to do enough cognition. Change is the progress of the project, such as shadow, this change is not single, referring to the external cause of demand, as a developer, we also change with the project. With the project The development, the more and more understanding of the project, the more you know, more and more proficient, more and more, and the code we wrote is quiet. There. I think I am a mature developer's standard (just right to be with this project or this area), when you grow up with the project, you will change the original intention, ie I want to make a large-scale revision of the overall design of the project. If your project has been half, you are not satisfied with the previous design, and even harsh, then you will use the code you will use. Is there a project? There is a problem that I have made me very confused, that is, there is always the technology or other things we are not familiar with. There is always such ases, let us feel that they are not mature enough, what should I do? In this way, we don't have so much time to learn, practice, so that you will become familiar, we only have mature with the development of the project. I should "reconstruct" this concept is one Good medicine, the project is continuously developed, we will continue to develop, when you send the Bad Small in the current code, you will be immediately cleared. By the module we do now, the company can accumulate as the company's code, the company can always use it. I am a more practical person. I think the project is the first, the code reuse first is the code needs to be Repeated use. I think this is often overlooked, and many people will feel that it is of course, and I think it is not as simple as imagining. For example, the module I am responsible in the project and another colleague is responsible for The module requires a function of generating a simple geometric mesh. But we have two different differences in specific needs. In the end we still wrote a small module. So I want to talk about good communication, good planning And the control of the project is effective to minimize the phenomenon of repeated development in a single project. I still If you want to talk about it, the code is reused from reusing your own code. I have seen a copy of the brother who repeated a code to multiple places instead of using a function.: (Function, template, Class It is the most basic code reusable tool, basically the thing of the Coding level, if these are not good, don't need the code reusable between the projects. 3. You should develop from a small module, if you want to design one More than 100,000 rows of reusable Framework unless you are a genius, otherwise it is destined to fail. For this small software development in my personal - game development, I think I am in a lot of technical points, with Europe and America Many colleagues can write a HDR or Soft Shadow's demo. But I feel that we are too tender (maybe my eyes are too narrow, I haven't seen it), some Framework is common The concept is rare to be in the engine in China. I have seen some of the engines are quite simple in structure, and one engine can be used in three projects. It is already very tenacious. More cases An engine has experienced the use of two projects. It is already full of sore. Finally, I want to talk about why I think there are several blood youths in the company to reuse practices when we come to the company. To fails, let's give those friends who are more young than my young friends. I think they are far from reaching the reusable code, it is too early to emphasize this. They spend a lot of time To improve the document, repeatedly modify the code, however, I observed the code they did to meet the stable operation of the current project. For example, a brother used a brother to write a GUI module for approximately 1 year. , The same module, our project has only used 2 people, but also the last buddy, because the level is too bad!
