(From Lebyte)

The application of a principle or concept is often not limited to a single field. For example, software development and product design, there are many general principles.

My Colleagues at Lebyte recently asked me how developers could interpret agreed-upon design principles if they applied them to programming. Based on my personal programming experience, I would like to share with you four points:

01 –

Good code is innovative

In any case, the possibility of progress remains. Technological developments always provide new opportunities for original design. But imaginative design has always evolved with technology, not as an end in itself.

Many of the problems solved by the code are not new. Instead, many technologies are solving old problems. For example, to make food, clothing, housing and transportation more convenient and efficient.

But solving old problems is not the norm or the end of the road. Technology is constantly innovating and advancing in order to give people a better user experience.

For example, you may feel that the end of the product form is now the ability to quickly fulfill previously impossible needs with food delivery apps and taxi hailing apps.

But you can’t imagine how many innovative technologies are trying to upend existing ways. You can never imagine the power of technology.

Constant subversion, continuous innovation, technology is a lifelong proposition.

02 –

Good code to make the product usable

A product that users are willing to pay for must meet not only the necessary functional requirements, but also psychological and aesthetic standards. Good design gives priority to product practicality.

Don’t program for programming’s sake, program to solve problems.

The availability of code is not limited to a single domain. Front-end interfaces and back-end apis should provide good affordability in most scenarios.

The code base should always focus on the problem to be solved.

03 –

Good code is beautiful

The aesthetic quality of a product is an integral part of its usefulness, as it is used every day and affects people’s moods.

This principle applies well to Web and mobile interfaces, but it also applies to back-end apis.

Because the code to consider its readability, a piece of unreadable, difficult to understand the code, late maintenance and modification costs are very high.

Here are a few suggestions that might help you make your code more readable:

Code style consistency structure clear and reasonable comments, naming and other procedures reusability

04 –

Good code makes the product easy to use

Good product, clear structure. The cost of learning is very low and the user is very quick to learn.

Good code solves real world problems.

Because code is abstract, many programmers write code that ultimately fails to meet their actual needs and deviates from the business direction.

I’ve seen many programmers refactor code because of these problems, wasting time and not reusing value.

A better solution is to document more and confirm more.

In the process of writing code, if there is any uncertainty in understanding, align the information with the demand side in time, and do not keep writing in order to complete the work quickly.

Sometimes, slow is fast.

Above are four points that many programmers probably ignore in their daily work. I hope that these underlying principles can provide a glimmer of inspiration when we feel confused.

PS: Ali P8 strongly recommended 8 Java project combat large collection B station: BV1J64y1R7UN