Code-Quality Tools

Apress eBooks · 2008

Since the early days of computers, programmers have been striving to write “good” code. The exact definition of good varies greatly, depending on which programming language you are examining. It also depends on whom you ask to define what is and is not “good” code. For the purpose of the tools discussed in this chapter, I assume a practical definition of good Java code to include loosely the following: Consistent and easy-to-understand formatting (i.e., indentation and spacing) Consistent naming conventions No compile-time errors No runtime errors (or at least the ability to handle runtime errors) Adherence to best practices and good design Easy-to-understand and thorough in-code documentation These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Read the paper · More papers on PaperTik