Standardization from a trivial matter

Standardization from a trivial matter

 

Please indicate the source when reprint: http://blog.csdn.net/absurd/

 

The Ministry of Human Resources recently asked all employees to upload photos to create employee cards. The upload directory, photo resolution, and deadline are described in the notification, but the file naming method and format are not specified. I found:

 

About uploading Directories: The root directory is in the specified directory. However, some are placed under the root directory; some have created sub-directories by department and put photos in sub-directories; some have created sub-directories by personal name, and then put photos in sub-directories.

 

About photo resolution: The rule is 1024x768. the maximum number of people who provide 2000 X photos is the largest, but more than photos can be taken as small as X photos.

 

About deadline: Most people upload photos within the deadline. A few people upload photos only after the deadline, and a few do not upload photos at the end.

 

File naming. Since no provisions are made on the file name in advance, the file naming method is the most different. I have counted 11 types of file names, which are basically composed of the Department name, name, employee ID, minus sign, and brackets. In addition, the random file name generated by the camera is used.

 

File Format. No file format is specified in advance. Most photos are in JPG format, and a few are in BMP format. This may be because most cameras use JPG format.

 

For the first point, there is a standard description, but the description is not accurate enough. Do you want to create sub-directories or create sub-directories according to the standards? If no accurate description is provided, everyone should follow their own judgment.

 

For the second point, the specification is accurate, but the importance of it is not emphasized, so the implementation has not been effectively implemented. We all think that the size of the photo is irrelevant.

 

For the third point, the specifications are accurate and the importance is self-evident, but there is no inspection mechanism. Some people forget this because of their busy work. Later, the Ministry of Personnel asked the Department assistant to assist in the inspection, and the incident progressed rapidly.

 

The fourth point is not described in the specification. The results are all named in the desired way. This greatly demonstrates everyone's innovation.

 

The last point is not described in the Specification, but there are not many choices, so there are not many tricks to play.

 

Standards may not be important for uploading photos. These differences will not cause too many problems. For software development, if the format of the document is extraordinary and the style of the Code is blooming, the problem will be a big deal. Therefore, appropriate specifications are necessary for software development. The specifications themselves must be accurate and clear, and they must be implemented effectively when implementing the specifications. Finally, there must be a necessary inspection mechanism, but few of them cannot, otherwise, the specification is just a false one. Of course, there cannot be too many specifications, which are too well-organized. Otherwise, the same harm will occur.