Confusion and Analysis of missing mechanisms

Confusion and Analysis of missing mechanisms

Wu Yu

Taiyan Network Studio

 

I have designed a questionnaire and asked friends and friends around me to answer:

Every city in China has 110, 119, 120, 122, and 110 emergency calls. Now, if 119 (OR) is canceled, could you tell me when you encounter a criminal case (or fire, what do you do?

The answers I have collected are similar. Basically, 110 is required, but 119 is not required, but 119 is required.

I further suggested that 119 cannot solve 110 of the problem. Fire fighters have gas masks, but there is no bulletproof vest, and water-gun cannot uniform the pistol of terrorists in any way; and vice versa. A gun in 110 hands won't be able to save the fire.

The answer I collected is: 120 and 122 are more unreliable!

I carefully analyzed their subconscious: Although there is basically no alternative between 110 and 119, people will be able to find a more likely option: Compared with 120 and 122, the similarity between 110 and 119 is still higher.

If the above situation is true, 119 of the staff will be complaining! There is no error in alerting the masses in case of danger, and there is no error in alerting 119 of the people who receive the police, but 119 of the people who do not do well should do the same thing! If the work is not good, the people will not be satisfied, but may still blame 119. Instead, there is no responsibility to stand up for 110.

 

Sometimes it is so strange. For example, software developers are invited to design the following development scenarios:

A company needs to monitor the working efficiency of workers on the production line in real time. The data displayed on the display terminal in front of the monitoring personnel is:

1. employee ID (INT data, 4 bytes );

2. employee name (char array, 8 bytes );

3. Work Efficiency (float data, 4 bytes );

In general, we will consider this: the data collection end collects the work efficiency based on the employee ID, and then uploads these two fields (8 bytes in total) to the display terminal, the display terminal then finds the employee name based on the employee ID, and finally displays the updated information on the screen.

The current development situation has changed a little, that is, the terminal display developer said that we have not developed the ID lookup name function (in fact, the mechanism is missing ), can a data collection developer upload the employee name together (apparently, the data collection end has this search mechanism )? To put it bluntly, the original 8-byte upload is changed to 16 bytes to replace the lack of the terminal display mechanism.

In general, both developers and Technical Directors will feel that it is simple and convenient to upload 16 bytes at a time, but it is a hidden danger, everyone tends to turn a blind eye:

1Traffic is doubled.When the data volume is relatively small, you cannot see the problem, but when the data volume is large and the data collection and monitoring terminal is not in the same geographic location, the problem will become irreconcilable immediately;

2Improper Function Positioning leads to difficulties in expansion and development.For example, the customer thinks that the employee's gender and age are also an important parameter. Who will do this query during display on the terminal?

3Unclear responsibilities lead to chaotic management.If a problem occurs, the responsible party should be held responsible, but the responsible party should not be held responsible. Just like 119 cannot do 110 of jobs, the result of hard substitution is only unsatisfactory for most people. In addition, when there will be similar problems in the future, it will be a headache for the other party to solve the problem. People who suffer from the loss cannot be willing to suffer from the old one, and those who take advantage of the cheap will certainly be willing to continue with the lack of functions. A team that lacks justice and leads to mutual promotion is an irresponsible team, and a team that cannot work better and better!

4Lack of mechanisms is a serious functional obstacle.For example, how can I deal with software and hardware problems in case of unavailability? Do you need to wait until the problem is solved, or enable a backup solution immediately to meet your most basic needs? The ancients said that everything should be done in advance, but nothing should be done in advance. Our responsible personnel may wish to think about it more.

 

The most humorous project owner I have ever met, and the answer to my project scenario above is: in this case, we usually compress the data and then upload it out, so it's okay.

After hearing this, I had no brains. This answer is far beyond my imagination! I just understood that he doesn't know what the compression of a 16-byte group means or how complicated the compression algorithm brings to the entire project! Or in his eyes, all the staff who can solve the current problem can be competent.

 

When such a project owner encounters software development, it is really not human work!

Smile.