Emphasize code specification.
I still remember that a few years ago, every time I talk about the software specification, the thick code specification document, how to name the variable, how to write, parentheses, how to write. . . The book "C high quality becomes guidelines" also is also referred to as a classic. After a period of chase, these specifications are found and the role of the software is rooted, but instead of developing these factors. Similar to this work can be automatically completed by the development tools such as NetBeans, Eclipse, such as using the most code brush Japloy (open source project). Obviously, spend more time to specify the code.
Of course, you must admit that the variable is named for the reader, especially for non-author, it is more important. After the opening source of the project, you will have some experience after reading the source code of each open source project. My experience is "Object With Name Naming", for example:
HttpRequest httprequest;
HTTPRESPONSE HTTPRESONPSE
This is very intuitive, isn't it?
Emphasize humanized management.
Also a few years ago, software development was considered to be a high IQ work, and also enjoy special treatment. If you don't go to work on time, who is late, these are known as loose humanized management, experience software CMM After the climax, some people call the people developed as "farmers". As a member of the software development, enjoy the special treatment, it is almost unhappy. In fact, these beside reflected is that the public or even managers lack sufficient understanding of the characteristics of the software development process.
After a few years, I think the software development and other industrial processes are inherently inquiry to improve productivity. Therefore, software development should be controlled like other industries, only characteristics and management The means vary. One taste emphasizes that humanized management may not guarantee software quality, speed up software development progress, and improve profits.
I think the software development is to work on time. I always think that the developer belongs to an alternative group, even this style is touted and hype. The developer is also a person, and it will be old, and it also needs health, and health is most important. An excellent developer can always quantify according to capabilities, complete tasks on time.
Emphasize the advancement of technology.
In recent years, technology updates have accelerated, especially under the wave of open source projects, new technologies always serve as a certificate of certification. When each interview and others talk about technology, how to use it in technology, such as how to configure Hibernate, how to use the LINK label in Struts, how to write how the action and form are configured, then it is the business Strive, in fact, it has been found that these things have a very detailed usage in Manual or Documentation. Is it better to have a memory for a long time? Do you have to see who is watching the document?
The fundamental purpose of technology is to increase production efficiency and create profits. Therefore, as long as it can accelerate the development speed, improve software quality technology is adopted, as for how to write, the statement is a secondary, but I don't understand why every discussion technology is going to these details. Controversy.
Emphasize software engineering.
