AmbySoft Inc. Java Coding Standards
is a revisited mirror (published with the agreement of the original author Scott W. Ambler) of http://WWW.AmbySoft.com/javaCodingStandards.html by Scott W. Ambler (ambler@hookup.net)
Includes 2 PDF files where the author seriously documents his proposal. You'll find here a structured sum of ideas and proposals gathered from miscellaneous authors.

  1. 1. GENERAL CONCEPTS in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 1

  2. 1.1 WHY CODING STANDARDS ARE IMPORTANT in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 1

  3. 1.2 THE PRIME DIRECTIVE in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 1

  4. 1.3 WHAT MAKES UP A GOOD NAME in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 1

  5. 1.4 GOOD DOCUMENTATION in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 2

  6. 1.4.1 The Three Types of Java Comments in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 3

  7. 1.4.2 A Quick Overview of javadoc in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 4

  8. 2. STANDARDS FOR METHODS in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 5

  9. 2.1 NAMING METHODS in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 5

  10. 2.1 NAMING METHODS 2.1.1 Naming Accessor Methods in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 5

  11. 2.1 NAMING METHODS 2.1.1 Naming Accessor Methods 2.1.1.1 Getters in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 5

  12. 2.1 NAMING METHODS 2.1.1 Naming Accessor Methods 2.1.1.2 Setters in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 6

  13. 2.1 NAMING METHODS 2.1.1 Naming Accessor Methods 2.1.1.3 Constructors in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 6

  14. 2.2 METHOD VISIBILITY in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 7

  15. 2.3 DOCUMENTING METHODS in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 7

  16. 2.3 DOCUMENTING METHODS 2.3.1 The Method Header in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 7

  17. 2.3 DOCUMENTING METHODS 2.3.2 Internal Documentation in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 9

  18. 2.4 TECHNIQUES FOR WRITING CLEAN CODE in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 10

  19. 2.4 TECHNIQUES FOR WRITING CLEAN CODE 2.4.1 Document Your Code in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 10

  20. 2.4 TECHNIQUES FOR WRITING CLEAN CODE 2.4.2 Paragraph Your Code in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 10

  21. 2.4 TECHNIQUES FOR WRITING CLEAN CODE 2.4.3 Use Whitespace in Your Code in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 11

  22. 2.4 TECHNIQUES FOR WRITING CLEAN CODE 2.4.4 Follow The Thirty-Second Rule in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 11

  23. 2.4 TECHNIQUES FOR WRITING CLEAN CODE 2.4.5 Write Short, Single Command Lines in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 11

  24. 2.4 TECHNIQUES FOR WRITING CLEAN CODE 2.4.6 Specify the Order of Operations in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 11

  25. 3. STANDARDS FOR ATTRIBUTES (FIELDS/PROPERTIES) in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 12

  26. 3.1 NAMING ATTRIBUTES in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 12

  27. 3.1 NAMING ATTRIBUTES 3.1.1 Naming Components (Widgets) in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 12

  28. 3.1 NAMING ATTRIBUTES 3.1.1 Naming Components (Widgets) 3.1.1.1 Alternative for Naming Components – Hungarian Notation in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 12

  29. 3.1 NAMING ATTRIBUTES 3.1.1 Naming Components (Widgets) 3.1.1.2 Alternative for Naming Components – Postfix-Hungarian Notation in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 13

  30. 3.1 NAMING ATTRIBUTES 3.1.2 Naming Constants in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 13

  31. 3.1 NAMING ATTRIBUTES 3.1.3 Naming Collections in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 13

  32. 3.2 ATTRIBUTE VISIBILITY in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 14

  33. 3.2 ATTRIBUTE VISIBILITY 3.2.1 Don't "Hide" Names in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 14

  34. 3.3 DOCUMENTING AN ATTRIBUTE in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 14

  35. 3.4 THE USE OF ACCESSOR METHODS in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 15

  36. 3.4 THE USE OF ACCESSOR METHODS 3.4.1 Naming Accessors in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 15

  37. 3.4 THE USE OF ACCESSOR METHODS 3.4.2 Advanced Techniques for Accessors in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 16

  38. 3.4 THE USE OF ACCESSOR METHODS 3.4.2 Advanced Techniques for Accessors 3.4.2.1 Lazy Initialization in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 16

  39. 3.4 THE USE OF ACCESSOR METHODS 3.4.2 Advanced Techniques for Accessors 3.4.2.2 Getters for Constants in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 17

  40. 3.4 THE USE OF ACCESSOR METHODS 3.4.2 Advanced Techniques for Accessors 3.4.2.3 Accessors for Collections in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 19

  41. 3.4 THE USE OF ACCESSOR METHODS 3.4.3 Visibility of Accessors in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 19

  42. 3.4 THE USE OF ACCESSOR METHODS 3.4.4 Why Use Accessors? in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 19

  43. 3.4 THE USE OF ACCESSOR METHODS 3.4.5 Why Shouldn't You Use Accessors? in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 20

  44. 3.5 ALWAYS INITIALIZE STATIC ATTRIBUTES in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 20

  45. 4. STANDARDS FOR LOCAL VARIABLES in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 22

  46. 4.1 NAMING LOCAL VARIABLES in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 22

  47. 4.1 NAMING LOCAL VARIABLES 4.1.1 Naming Streams in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 22

  48. 4.1 NAMING LOCAL VARIABLES 4.1.2 Naming Loop Counters in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 22

  49. 4.1 NAMING LOCAL VARIABLES 4.1.3 Naming Exception Objects in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 22

  50. 4.1 NAMING LOCAL VARIABLES 4.1.4 Bad Ideas for Naming Local Variables in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 23

  51. 4.2 DECLARING AND DOCUMENTING LOCAL VARIABLES in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 23

  52. 5. STANDARDS FOR PARAMETERS (ARGUMENTS) TO METHODS in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 24

  53. 5.1 NAMING PARAMETERS in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 24

  54. 5.2 DOCUMENTING PARAMETERS in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 24

  55. 6. STANDARDS FOR CLASSES, INTERFACES, PACKAGES, AND COMPILATIONS UNITS in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 26

  56. 6.1 STANDARDS FOR CLASSES in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 26

  57. 6.1 STANDARDS FOR CLASSES 6.1.1 Naming Classes in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 26

  58. 6.1 STANDARDS FOR CLASSES 6.1.2 Documenting a Class in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 26

  59. 6.1 STANDARDS FOR CLASSES 6.1.3 Class Declarations in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 27

  60. 6.1 STANDARDS FOR CLASSES 6.1.4 Minimize the Public and Protected Interface in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 28

  61. 6.2 STANDARDS FOR INTERFACES in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 28

  62. 6.2 STANDARDS FOR INTERFACES 6.2.1 Naming Interfaces in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 28

  63. 6.2 STANDARDS FOR INTERFACES 6.2.2 Documenting Interfaces in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 29

  64. 6.3 STANDARDS FOR PACKAGES in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 29

  65. 6.3 STANDARDS FOR PACKAGES 6.3.1 Naming Packages in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 29

  66. 6.3 STANDARDS FOR PACKAGES 6.3.2 Documenting a Package in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 30

  67. 6.4 STANDARDS FOR COMPILATION UNITS in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 30

  68. 6.4 STANDARDS FOR COMPILATION UNITS 6.4.1 Naming a Compilation Unit in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 30

  69. 6.4 STANDARDS FOR COMPILATION UNITS 6.4.2 Documenting a Compilation Unit in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 30

  70. 7. MISCELLANEOUS STANDARDS in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 32

  71. 7.1 REUSE in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 32

  72. 7.2 IMPORTING CLASSES in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 32

  73. 8. THE SECRETS OF SUCCESS in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 33

  74. 8. THE SECRETS OF SUCCESS 8.1 USING THESE STANDARDS EFFECTIVELY in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 33

  75. 8. THE SECRETS OF SUCCESS 8.2 OTHER FACTORS THAT LEAD TO SUCCESSFUL CODE in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 33

  76. 9. PROPOSED JAVADOC TAGS FOR METHODS in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, p. 35

  77. Java naming conventions in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  78. Java documentation conventions in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  79. Java coding conventions in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  80. the prime directive:
    When you go against a standard, document it. All standards, except for this one, can be broken. If you do so, you must document why you broke the standard, the potential implications of breaking the standard, and any conditions that may/must occur before the standard can be applied to this situation. in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  81. Java Naming Conventions
    With a few exceptions discussed below, you should always use full English descriptors when naming things. Furthermore, you should use lower case letters in general, but capitalize the first letter of class names and interface names, as well as the first letter of any non-initial word.
    General Concepts: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  82. Naming convention: Arguments/ parameters
    Use a full English description of value/object being passed, possibly prefixing the name with 'a' or 'an.' The important thing is to choose one approach and stick to it.
    example: customer, account,
    - or -
    aCustomer, anAccount
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  83. Naming convention: Attributes/ fields/ properties
    Use a full English description of the attribute, with the first letter in lower case and the first letter of any non-initial word in uppercase.
    example: firstName, lastName, warpSpeed
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  84. Naming convention: Boolean getter methods
    All boolean getters must be prefixed with the word 'is.' If you follow the naming standard for boolean attributes described above then you simply give it the name of the attribute.
    example: isPersistent(), isString(), isCharacter()
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  85. Naming convention: Classes
    Use a full English description, with the first letters of all words capitalized.
    example: Customer, SavingsAccount
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  86. Naming convention: Compilation unit files
    Use the name of the class or interface, or if there is more than one class in the file than the primary class, prefixed with '.java' to indicate it is a source code file.
    example: Customer.java, SavingsAccount.java, Singleton.java
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  87. Naming convention: Components/ widgets
    Use a full English description which describes what the component is used for with the type of the component concatenated onto the end.
    example: okButton, customerList, fileMenu
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  88. Naming convention: Constructors
    Use the name of the class.
    example: Customer(), SavingsAccount()
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  89. Naming convention: Destructors
    Java does not have destructors, but instead will invoke the finalize() method before an object is garbage collected.
    example: finalize()
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  90. Naming convention: Exceptions
    It is generally accepted to use the letter 'e' to represent exceptions.
    example: e
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  91. Naming convention: Final static attributes (constants)
    Use all uppercase letters with the words separated by underscores. A better approach is to use final static getter methods because it greatly increases flexibility.
    example: MIN_BALANCE, DEFAULT_DATE
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  92. Naming convention: Getter methods
    Prefix the name of the attribute being accessed with 'get.'
    example: getFirstName(), getLastName(), getWarpSpeeed()
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  93. Naming convention: Interfaces
    Use a full English description describing the concept that the interface encapsulates, with the first letters of all words capitalized. It is customary to postfix the name with either 'able,' 'ible,' or 'er' but this is not required.
    example: Runnable, Contactable, Prompter, Singleton
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  94. Naming convention: Local variables
    Use full English descriptions with the first letter in lower case but do not hide existing attributes/fields. For example, if you have an attribute named 'firstName' don't have a local variable called 'firstName.'
    example: grandTotal, customer, newAccount
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  95. Naming convention: Loop counters
    It is generally accepted to use the letters i, j, or k, or the name 'counter.'
    example: i, j, k, counter
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  96. Naming convention: Packages
    Use full English descriptions, using mixed case with the first letter of each word in uppercase, everything else in lower case. For global packages, reverse the name of your Internet domain, put the first identifier completely in uppercase, and concatenate to this the package name.
    example: java.awt, COM.AmbySoft.www. persistence.mapping
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  97. Naming convention: Methods
    Use a full English description of what the method does, starting with an active verb whenever possible, with the first letter in lower case.
    example: openFile(), addAccount()
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  98. Naming convention: Setter methods
    Prefix the name of the attribute being accessed with 'set'. setFirstName(),
    example: setLastName(), setWarpSpeed()
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  99. Naming convention: Although I (Scott W. Ambler) don't agree with the following conventions, Sun suggests that for local variables of the given types you can give them short names. A much better convention is to use a full English descriptor – Don't be lazy.
    Variable TypeSuggested Naming Convention
    offsetoff
    lengthlen
    byteb
    charc
    doubled
    floatf
    longl
    Objecto
    Strings
    Arbitrary valuev
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  100. Java Documentation Conventions
    A really good rule of thumb to follow regarding documentation is to ask yourself if you've never seen the code before, what information would you need to effectively understand the code in a reasonable amount of time.
    General Concepts: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  101. Java Comment Types
    (The following table) describes the three types of Java comments and suggested uses for them.
    Comment Type Usage Example
    Documentation Use documentation comments immediately before declarations of interfaces, classes, methods, and attributes to document them. Documentation comments are processed by javadoc, see below, to create external documentation for a class.
    /**
Customer – A customer is any
person or organization that we
sell services and products to.
@author S.W. Ambler
*/
    C style Use C-style comments to document out lines of code that are no longer applicable, but that you want to keep just in case you users change their minds, or because you want to temporarily turn it off while debugging. 
    /*
This code was commented out
by J.T. Kirk on Dec 9, 1997
because it was replaced by the
preceding code. Delete it after two
years if it is still not applicable.
. . . (the source code )
*/
    This isn't actually a standard, it's more of a guideline. The important thing is that your organization should set a standard as to how C-style comments and single-line comments are to be used, and then to follow that standard consistently.
    Single line Use single line comments internally within methods to document business logic, sections of code, and declarations of temporary variables. 
    // Apply a 5% discount to all invoices
// over $1000 as defined by the Sarek
// generosity campaign started in
// Feb. of 1995.
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  102. What to document for Arguments/ parameters
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  103. What to document for Attributes/ fields/properties
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  104. What to document for Classes
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  105. What to document for Compilation units
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  106. What to document for Getter method
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  107. What to document for Interfaces
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  108. What to document for Local variables
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  109. What to document for Methods – Documentation
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  110. What to document for Methods – Internal comments
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  111. What to document for Package
    in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary. in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  112. Java Coding Conventions
    There are many conventions and standards which are critical to the maintainability and enhanceability of your Java code. 99.9% of the time it is more important to program for people, your fellow developers, than it is to program for the machine. Making your code understandable to others is of utmost importance. in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  113. Coding conventions for Accessor methods in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  114. Coding conventions for Attributes in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  115. Coding conventions for Classes in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  116. Coding conventions for Local variables in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  117. Coding conventions for Methods in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  118. What to document for Arguments/ parameters

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  119. What to document for Arguments/ parameters

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  120. What to document for Arguments/ parameters

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  121. What to document for Arguments/ parameters

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  122. What to document for Attributes/ fields/properties

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  123. What to document for Attributes/ fields/properties

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  124. What to document for Attributes/ fields/properties

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  125. What to document for Attributes/ fields/properties

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  126. What to document for Attributes/ fields/properties

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  127. What to document for Attributes/ fields/properties

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  128. What to document for Classes

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  129. What to document for Classes

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  130. What to document for Classes

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  131. What to document for Classes

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  132. What to document for Classes

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  133. What to document for Compilation units

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  134. What to document for Compilation units

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  135. What to document for Compilation units

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  136. What to document for Interfaces

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  137. What to document for Interfaces

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  138. What to document for Methods – Documentation

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  139. What to document for Methods – Documentation

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  140. What to document for Methods – Documentation

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  141. What to document for Methods – Documentation

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  142. What to document for Methods – Documentation

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  143. What to document for Methods – Documentation

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  144. What to document for Methods – Documentation

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  145. What to document for Methods – Documentation

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  146. What to document for Methods – Documentation

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  147. What to document for Methods – Documentation

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  148. What to document for Methods – Documentation

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  149. What to document for Methods – Internal comments

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  150. What to document for Methods – Internal comments

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  151. What to document for Methods – Internal comments

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  152. What to document for Methods – Internal comments

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  153. What to document for Methods – Internal comments

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  154. What to document for Package

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  155. What to document for Package

    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  156. Java Coding Conventions
    There are many conventions and standards which are critical to the maintainability and enhanceability of your Java code. 99.9% of the time it is more important to program for people, your fellow developers, than it is to program for the machine. Making your code understandable to others is of utmost importance. in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  157. Coding conventions for Accessor methods
    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  158. Coding conventions for Accessor methods
    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  159. Coding conventions for Accessor methods
    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  160. Coding conventions for Accessor methods
    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  161. Coding conventions for Accessor methods
    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  162. Coding conventions for Attributes
    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  163. Coding conventions for Attributes
    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  164. Coding conventions for Attributes
    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by Scott W. Ambler, v. July 10, 1997, Summary.

  165. Coding conventions for Attributes
    One of the items proposed by Scott W. Ambler is: in AmbySoft Inc. Java Coding Standards by