That's how I use the data: small body, big taste.

I have done such a strange design.

The situation at that time was, need to trace n production line of tens of thousands of daily output, when the product found defects can be traced to the end of which line of products, because each production line may adopt a special assembly method, we need from the point of view of data analysis to identify their pros and cons, in order to continue to improve.

Well, the background is finished, start to do software, this is actually quite simple, an input box collection product bar code, an input box to collect production line identification code, submitted, completed.

Then I was rewarded by the leadership, the leader thought this thing is very cow x, I have a few days to get out, verbal rewards plus lunch (the leader's menu is different OH).

However, when the deployment, I was scolded poured, because this thing is too difficult to enter, the original day tens of thousands of production, is very busy, but also every product registration once, attitude is: never accept! (few developers dare to stand around the front line users naked, but I do this every time, because I think this is the most interesting part of doing software, whether scolded or praised, others do not ignore your existence!) ）

I have previously shared an attitude toward demand (I do not cater to demand), but I am fastidious about the deployment of exceptions, as long as the deployment of the thumbs up to the standard, I have to force the request for improvement.

Removed all the statistical work stations, assembly personnel affixed a bar code, indicating that this thing is I do, so that the task of collecting information to do, all the N-line tens of thousands of products by a unified collection of people, so that the burden of the production line is a lot smaller, labeling on the finished. Then cultivate a person, skilled, special deal with the acquisition task, the lever!

The story is not over yet, this evil label brings me new thinking. Because the amount of a day, a label cost 2 cents, one day down is also thousands of yuan, the meat hurts Ah!

Since the line identification code is similar to: 00000000000001, 00000000000000002

In fact, only 1 digits, I will print a shorter bar code, such as 00000001, 00000002, not too short, too short to recognize

When we shorten the bar code to four digits (0001), found that it is easy to make mistakes, often wrong to identify a bit, which makes me very headache, because the reduction to 4, you can cut a bar code to 8, and then the knife work better, perhaps 12 can also do AH.

At this time, I came up with a trick: let the bar code 0001 into 1111, even if the scan gun mistakenly identified a such as 11x1, but 1 or more occurrences of the most characters, I can recognize that the number of occurrences of the most characters prevail.

After detailed testing, we have been corrected after the correct rate is 100%, I am ecstatic! This also accidentally led to the need to buy fine bar code paper, the overall cost reduced to a few one-tenth below, a day down 100 yuan, the problem was solved.

It's just a little problem, in fact, the problem of bar code is not my business, if my hands a booth, said the cost of high that no way, then the company lost thousands of yuan a day, if I do not track the source of defects because of high costs, then the production line can not be scientific data support, if the xxxxxxx

Barcode This small stature, gave me the big taste! Why do programmers feel so proud, just because we can create! How can we be proud? is in the most ordinary problems, you dare not stand up, has been constantly saving time, save money, create value, and really do.

For the sake of honor, I asked myself to integrate into the user, from their perspective, in their way, feel their own, if this software is very troublesome, I will really do a day to see how much trouble, sometimes people are very cheap, you do not personally to experience, you think you know everything, in fact, you do not know, so, The real use of their own software, inconvenient when not to stop, exhausted yourself, you just know that you do not a thing of software!

This matter has been a long time, but I often take to say that we warn every member, whether the new or old fried dough: software to be responsible for the end!

Well, in charge of the end, a simple word, so that I in the software development on the way to walk a small step, taste the big taste!

See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/Programming/project/