1 code style and habits

Java：

// The difference between if (null == userNumber) and if (userNumber == null)
if (userNumber == null) {
         // It's easy to write if (userNumber = null), but it won't be reported when compiling, it's not convenient when checking for errors.
}
if (null == userNumber) {
         // And this is very straightforward, because if (null = userNumber) is reported in Java, so it's easy to find.
}

Intelligent Recommendation

Remember the code habits

1. Protected attributes usually underline_ As a prefix, this is just a simple agreement, which is not forced, that is, it should not access this type of properties and methods from the outside. 2, pri...

Logic habits in some code

Code logic habits or some small operations (own notes) 1. Requires an array or the current element of the string and the previous element to do related operations: Directly traverse this sequence, whe...

Business code habits

Business code habits Be sure before performing for loops, do not let NULL data or collections for FOR cycle Printing the log for the incoming value, the income parameters of the method are also printe...

Develop good code habits

Table of contents 1. Be sure to write a comment 2. Be sure to add a log 3. Java method where you need to pay attention 1. Be sure to write a comment Recommended xxx scenes of the note format, XXX oper...

Code style (1) - naming convention

First, the naming convention The most important consistency rule is naming management. The naming style allows us to quickly understand the meaning of a name without having to look up the type declara...