Things of the project (11)-the ability to enjoy [project standards] From top to bottom

As I mentioned earlier, I have divided 200 functions into six interfaces. as long as six interfaces are completed, 200 function operations are supported (hopefully you will remember ).

The six interfaces must comply with the specifications. Who will make these six interfaces?

Qi gefei, the first technical leader in this project, is introduced here. (This series uses the legend of Galaxy heroes for all characters.)

Qi gefei, from Huangshan, Anhui province, the 13th anniversary of the founding of the People's Republic of China

As a warrior who has been in the IT industry for five years, Xiao Qi has always been a self-taught talent. Practice. Net martial arts

Qi gefei is here to let him do one thing. Of course, he has done many things in the project team. I will only talk about one thing this time.

 

This is called technical specifications in our project team. Qi gefei is the person in charge of technical specifications, and he is also a senior engineer (software) of the project team ).

The technical specifications that Qi engineers are responsible for are not specified in any document. But the real code.

Incredible? Since the document can complete the specification, the code can also. Because I believe that code is the best document.

The procedure is as follows:

1. The Project Manager (that is, Yu Zhi) selects one of the 200 functions and submits them to Qi engineers.
2. Qi gefei will complete this function based on the Use Case, database design, and communication with the project manager. (Of course, they must comply with the specifications and be qualified in terms of efficiency)
3. Qi gefei submits the completed functions to the project manager for confirmation.
The above steps are repeated six times, which is Qi gefei's work.

These six functions are the representatives of the six interfaces. The six functions completed by Qi are technical specifications.

Now that the project manager is active, he wants to allocate the remaining functions to every programmer, except Qi gefei, because he has other functions.

Other programmers perform functions based on use cases and database designs. It seems that something is missing, and Qi gefei's technical specifications are also missing.

All programs will copy Qi gefei's technical specifications and then modify them to complete their tasks.

Now, programmers can have fun. The original development work has become a change job. Variables can be directly used in technical specifications. If they are not used, they are created in accordance with the mode of technical specifications. All class plans participate in technical specifications.

This guarantees the code standardization to the maximum extent, because all code is done in accordance with the technical specifications. The Code architecture, naming, and comments are all unified.

The efficiency will be greatly improved. Because the most workload is copying and pasting, rather than writing code.

Later, I found that the effect of code standardization is more effective than that of the document. The main reason is that programmers are willing to read the code, rather than reading the document (it seems that you still like to see what you can touch ).

But this rule must be done by Qi gefei. The reason is simple, and he is the most technical. This is shared by all groups. Therefore, copying Qi gefei's code is not a matter of personnel loss, and no one will find junk code in technical specifications. This is not conducive to stability and harmony.

It's amazing that the development of our project team did this. It's estimated that a smart friend found a problem. "Why didn't you develop it without designing documents ?"

Yes, my project team has no design documents, because the design is in the technical specifications. Qi gefei not only wrote the sample code, but also completed the system design.

It seems that the system design time in the project has been saved.

The effect is very obvious. This project has been launched for the first time (more than 80 functions ), it took only two months (the last 20 days for demand and database design) and no overtime.

This clever method was not my original idea, because earlier, a big brother in the industry developed it in this way. The name of this big brother is Microsoft.

Microsoft manages this practice as synchronization. To ensure synchronization, Microsoft also proposed the concept of stability. Of course, its method is much more complicated than mine.

Post

The standardization description is now complete. Later, you will see more of the first man, Qi gefei. You will see how he turned my team into a programming machine.

With regard to standardization, I did not expect to bring a lot of comments from my friends. Someone specially added my MSN to talk about standards, some friends wrote a special article "The event of the project" to discuss the standards. What's more interesting is that the click rate of the version is higher than that of the genuine version. It is estimated that it is affected by the mobile phone market.

From this we can see how high the software industry is talking about standardization. This is a good thing. Standardization is progress. After all, we all want to be Qin Jun, and we don't want to be Zhao pawn.

We hope that we will discuss standardization more in the future, and hope that the standardization will become better and better.

In fact, the development idea of my project is also named in the industry-beyond the software factory. I will explain it in detail later.

Next I will start to talk about the most interesting and difficult part of the project-the team.