Rule 12:Adhere to generally accepted naming conventions
naming conventions fall into two categories: typographical and grammatical.
There are only a handful of typographical naming conventions, covering packages, classes, interfaces, methods, fields, and type variables.
The remainder of a package name should consist of one or more components describing the package. Components should be short, generally eight or fewer characters. Meaningful abbreviations are encouraged, for example, util rather than utilities. Acronyms are acceptable, for example, awt. Components should generally consist of a single word or abbreviation
Type parameter names usually consist of a single letter. Most commonly it is one of these five: T for an arbitrary type, E for the element type of a collection, K and V for the key and value types of a map, and X for an exception. The return type of a function is usually R. A sequence of arbitrary types can be T, U, V or T1, T2, T3.
Grammatical naming conventions:
these conventions are more flexible and more controversial than typographical conventions. There are no grammatical naming conventions to speak of for packages.
Instantiable classes, including enum types, are generally named with a singular noun or noun phrase, such as Thread, PriorityQueue, or ChessPiece. Non-instantiable utility classes (Item 4) are often named with a plural noun, such as Collectors or Collections.
Interfaces are named like classes, for example, Collection or Comparator, or with an adjective ending in able or ible, for example, Runnable, Iterable, or Accessible.
Methods that perform some action are generally named with a verb or verb phrase (including object), for example, append or drawImage.
Methods that return a boolean value usually have names that begin with the word is or, less commonly, has, followed by a noun, noun phrase, or any word or phrase that functions as an adjective, for example, isDigit, isProbablePrime, isEmpty, isEnabled, or hasSiblings.
A few method names deserve special mention. Instance methods that convert the type of an object, returning an independent object of a different type, are often called toType, for example, toString or toArray. Methods that return a view (Item 6) whose type differs from that of the receiving object are often called asType, for example, asList.
Methods that return a primitive with the same value as the object on which they’re invoked are often called typeValue, for example, intValue.
Common names for static factories include from, of, valueOf, instance, getInstance, newInstance, getType, and newType
Techglot 