essence of clean code

Functions

F1: Too Many Arguments
Functions should have a small number of arguments. No argument is best, followed by
one, two, and three. More than three is very questionable and should be avoided with prejudice.
(See “Function Arguments” on page 40.)

F2: Output Arguments
Output arguments are counterintuitive. Readers expect arguments to be inputs, not outputs.
If your function must change the state of something, have it change the state of the
object it is called on. (See “Output Arguments” on page 45.)

 

F3: Flag Arguments
Boolean arguments loudly declare that the function does more than one thing. They are
confusing and should be eliminated. (See “Flag Arguments” on page 41.)

 

F4: Dead Function
Methods that are never called should be discarded. Keeping dead code around is wasteful.
Don’t be afraid to delete the function. Remember, your source code control system still
remembers it.

 

my note: in my opinion, flag isn't that beautiful, should not be used. especially those flag as function arguments.

 

Java
J1: Avoid Long Import Lists by Using Wildcards

 

J2: Don’t Inherit Constants

This is a hideous practice! The constants are hidden at the top of the inheritance hierarchy.
Ick! Don’t use inheritance as a way to cheat the scoping rules of the language. Use a static
import instead.

 

J3: Constants versus Enums