NO News is good news

　　There was a bad news from the customer: Ask each form to play a "Save successful" dialog box on the page after it is saved.

The customer representative complacent that the user experience is better, with a hint of condemnation that means "you should have thought of it". Oh...... Well, when I first entered, every page was thinking the same thing.

I thought, this matter is not big, since is not big, that is "nothing", does not and the customer nonsense. Then, after a busy work with colleagues, submit the code.

Look at the add in Git Bash , commit these commands clean and refreshing feedback, can't help but feel a hint of irony.

Git Bash inherits Unix culture, and in Unix philosophy, there's a "No news is good news. "

　　I ' M lovin ' it.

Personally, if an operation is done correctly, the interface will be quietly waiting for the next action. Well, there is no need to jump out and shout "save Success", "Operation Done" (especially if you also bring an exclamation point!)  ）...... It doesn't matter if you display a line of text in the command-line interface. But in the browser to play a dialog box, regardless of whether the box is modal, it forces the user to focus on its existence, which is very disturbing (especially if you also bring an exclamation point!) ）。

　　The success of the message, there is no need to exist (especially if you also bring an exclamation point!) ）。 Software is essentially a service tool, we use a software to perform the operation inside, in fact, the purpose is the result of the action. When all goes well, the effect of the result will certainly come through the business logic behind the program, where you expect it to appear, and that's what you want. When the user could have directly obtained the result, a "you succeeded" message, superfluous.

If the user does not know how to view the correct results, ask him to see the operating manual. (You must have prepared a detailed manual when you posted it, didn't you?) ...... Well, isn't it? Go ahead and write! )

Ask a question, what kind of colleague do you like at work?

Is that kind of words not much to say, assigned him a job, when it expires, beautifully returned to you a full set;

or you set up a task, and then every once in a while you hear him report, "I wrote a function," "I finished a page," "I just finished writing a piece of SQL."    WTF!? SHUT Up!!

　　

They say programmers are not talkative. But in a different way, the same is done, a quiet sentence "submitted" than the chatter of the "report" to be more cool. Several pages, fart big dot function, shout what? I don't know, I thought you wrote a homegrown browser of independent innovation.

　　Linus Torvalds said:

　　Talk is cheap, show me the code.

I have observed that some people like to report their work in broken, mostly because they don't actually do a lot of things. There is a very interesting psychological phenomenon: the more guilty, the more pompous. Because the actual output is not much, or did not meet the expectations, so subconsciously deliberately expressed, strengthen the output, a bit similar to the sense of brush existence. Because if you do not brush, worry that others may not notice, is actually due to limited output.

This phenomenon in the company like to engage in "daily" is very common, in order to fill the "daily", like a pupil writing text in order to gather up the words, the simple things into a number of items to fill, appear to do a lot of things.

I never like the so-called "daily", in my experience of the development of the project, bi-weekly scrolling, is I prefer a posture ...

Pull away and say it back. When the command runs successfully, you do not need to take off the "success" hint of the fart. There is another reason, if every success is to play a window, the user every time to see the prompt to determine, over the passage, the user of the system occurs on the screen prompts will be numb, see the pop-up window immediately to determine. As a result, when the error occurs one day, the interface pops up with a failed hint, and the user is completely likely not to look at it and turn it off directly. This also means that the whole system of the prompt function, waste away.

The success of hoping at, together failed, together collapse.

Speaking of which, by the way, spit out the famous "memory Read and Write Errors" dialog box in the Windows system.

When using Windows before, you will encounter a "0x?????????? 0x???????? of the Directive reference Memory. The memory cannot be "read" or "written". "Error message dialog box.

When I saw this, I thought the computer was going to explode.

Later into the profession, surprised Microsoft actually will have this kind of window, can't think of Microsoft to the memory address to do what the user do, and do not say that the vast majority of users are ordinary users, even programmers, see such original error hints, and can do? You expect me to open the case and talk to the memory address?

So, when I first met this dialog box, when I was careful to click OK, found that the computer did not explode, and then see this box immediately determined to eliminate, and then formed a habit.

This box, all the time until Winows 7, I have not used 8, jump directly to 10, inside Windows 10, it seems no longer see this box, I do not know is the product manager of Windows (if they are called "Product Manager" Redesign this place or the system stability has improved so that I have not met. In short, this box, like a blue screen, has been deeply rooted to represent Microsoft.

　　

　　

Hush...... Be a quiet person to write code, write a quiet program.