[Reading Notes] iOS-Precautions for writing code, and Reading Notes ios-

[Reading Notes] iOS-Precautions for writing code, and Reading Notes ios-

 

I. I am a strong supporter of early compilation and frequent compilation. Generally, after writing every method or code that is a little difficult, you must try to build it. This is a good habit, because if the amount of code added since the last successful compilation is small, it is very easy to narrow down the scope of compilation errors. This method also limits the number of errors or warnings received. If you write 2000 lines of code before compilation starts, you may be overwhelmed by a large number of errors (or warnings. Sometimes it is difficult to find the source of these errors, because the errors given by the compiler and the linker are often vague.

 

Second, it makes no sense to try to re-invent the wheel. Others have found many solutions to problems encountered during the software design process. These solutions have become the design model. The key aspect of these design patterns is to provide effective design to developers in a way that everyone can understand. These patterns are time-proven and provide a public vocabulary that is useful when you communicate with other developers about your design.

 

Reference: iOS database application advanced programming (version 2nd)