Superior from detail and mature software designers

As software designers and developers, they often focus on a software system. Overall process and function structure, often ignoring or ignoring the details of the "peripheral" Function The user, on the contrary, is very specific, and the designer seems to be harmless. "Function.
For example, if a software designer introduces his paid software, the process of our software is First, set the charging range and charging standard, and then generate the pay-as-you-go And then enter the billing information. Big and macro.
A user will interrupt you after you finish the process: You can print the invoice. ? We charge a lot every day, and we need to be able to print invoices automatically and in batches. Or : How much is billed for each person per day? This is nothing. For example, where are the deletion buttons? It is inconvenient for you to perform this operation. I used to enter numbers on the keypad. Press enter and the cursor should jump directly to the next line. You only need to press the direction key!
Sometimes software designers may feel overwhelmed or even wronged. : Why do you have to ask these corners if we have made so many "core" functions? ? Obviously, the user is right. If you cannot accept it, it means you are not mature enough (for software ). It is said that Microsoft's development team has a special role called user experience, and they find out where their software is not user-friendly.

The principle is simple. Software designers and programmers often consider issues from the perspective of producers and consider their production processes (such as algorithms and designs ). The quality of software is determined by users. Most users directly judge the software, that is, their experience in operating the software. It is very simple. It is nice to operate the software. He doesn't care what advanced algorithms you use in this software, and what kind of architecture does it use!

I always believe that "excellence comes from details ".

In fact, the above facts reflect the level of the software designer. A software designer will neverThe system's "basic functions" and "core functions" can be achieved with confidence.Because it is "rough" at best ". This is what most people can do.Although this part of work accounts for a large part of the work. As a software designer, you should never just stay here.

In fact, we certainly have some experiences in downloading small software online. After using some small software, you will say this to your friends: I took the test, the ××× software is awesome, and I even thought of such a function.

When I was a child, I could not sweep the floor, but I was always killed by my mom. I have this feeling.If you do not need to scan the corner of the room, the broom will be enough.But Mom will never be satisfied with this result; she always forces meUnder the stool, under the bed, etc.) to scan, so scan for half a dayBut those places only occupy a small part of the room area. But this completes mom.Will be satisfied.
This is the best interpretation of "excellence comes from details" in life!

So should software designers not pay attention to the overall software process and framework?? Of course not. On this basis, we ask our software designersNote more knowledge and focus more on these details (this is the software availability that many people are working on recently. software availability is one of the important requirements of software ). SoOur software designers are not doing well, but are not enough. Not enough!

These details are often boring and repetitive, So we oftenThe "software engineer" did not give enough teeth or even refused to do this. Is widely recognizedFor "smart people" software engineers, technical difficulties and difficult AlgorithmsAnd the pursuit and deception of new technologies are the true use of their IQ. I said, fart!
It would be ridiculous to have such an idea as a software engineer for commercial software.

As a result, developers have matured and become software that people like to use!