How to write elegant code?

The responsibility of the author of a piece of code shouldn’t just be to get it out there and test it. It should also include complete unit tests that go through code reviews and then go live.

To ensure the quality of the code developed by team members, you must have a complete code writing specification.

In addition, code review is an essential step and process. Code clarity should be at the top of the list. Because code clarity solves the problem we have when getting new code. The purpose of code review is very clear:

• Make sure the code does what it’s supposed to do

• Make sure the code is easy to maintain in the future when someone else takes it over.

If you want to write elegant and readable code, there are a few things you can do. For example:

• Develop uniform team coding specifications and strictly adhere to them.

• Name objects as nouns and methods as verbs.

• Variable names should be given by name.

• Do not name a method with a noun. Name the method with a verb.

• Establish a threshold for maximum cycle complexity. Make sure you don’t exceed this threshold as you code.

• Comment on key code, why code is written there.

• Reduce unnecessary redundant comments.

• The process of coding in accordance with the SOLID principle, the so-called SOILD principle is: single responsibility principle, open and closed principle, interface separation principle, Richter replacement principle, dependence inversion principle. If the above principles are not clear, you can see this link: blog.csdn.net/Vanya_Xue/a…

• Test every line of code for coverage to ensure that every line of code you write can be executed.

• Be responsible for code compatibility and ensure that exceptions are handled properly when they occur.

• Try to achieve code encapsulation, small and beautiful, not recommended long and redundant. Always remind yourself not to be a CV warrior.

• To master the professional vocabulary of programming, so that they can be professional enough in the professional words, close to the standard.

Now because the domestic Internet enterprises are many, the business volume is large. Developers are so uneven that many companies’ code is often a jumble of things that one person can’t write and the next person can’t take over. It’s not that I don’t want to, it’s that I can’t.

In the process of programming development, if you can do these things, at least the code quality and readability of many people have been.

Just some of their own views, do not like spray.