Java Code Specification

Referring to code specifications, the general will be directly associated with how the code should be written to be more readable. We can look at the Java code specifications published by SUN (which has been acquired by Oracle), Google, BAT, and Huawei, and you will find that they are not just code-writing specifications, but rather cover writing specifications, performance optimizations, new feature explanations, etc. The code specification of a company with the widest coverage is composed of six parts, including programming protocol, Exception Log, security protocol, Unit test, MySQL database and engineering structure.

Java is no longer just a language, it is an ecological environment, since it is the ecological environment, it must be based on the changes in the external environment constantly adjust their own, and constantly absorb the external excellent design to strengthen their own, it is necessary to constantly change the scope of expanding their own, not limited to language,

How to develop code specifications

I think we should follow the following points: professional things to the professional people to do, code specifications should be developed by the first line of many years of the programmer-led, by a number of people involved in joint development, lead the best is a whole stack of engineers, did many major projects, has more than 10 years of programming experience, modesty, and has been to maintain the learning State; Languages that can survive and are widely used by programmers today, its essence must be not only a language, but built a strong ecosystem, therefore, code specification should start from the engineering point of view, objectively analyze the whole project construction process need to face the coding, design problems, all-round to these technologies normative guidance; It is not enough to be guided by light, should learn Ali output code detection tools or plug-ins, automated implementation of code specifications whether the implementation of the detection, rather than relying on artificial; everything needs reasoning, therefore, code specifications should be divided into two volumes, rolled up for code specifications, the next volume for code specifications for each article detailed explanation, Explain why the code is so coded, what are the technical and engineering stories behind it, convincing people, using technology to convince or crush programmers, and constantly updating. Technical update quickly, engineering process encountered problems are endless, therefore, code specifications will not be a conclusion, need to constantly update, supplement, improve, so as to keep pace with the times, to maintain vitality.