Minimize scope of local variables.
Local variables should be contained within the smallest scope possible.
The most optimal solution is therefore to create the local variable the same place as it is used. Thereby increasing the readability of the code and minimizing the chance of misusing the variable.
Assert method arguments validity
Whenever an object is given in as a method argument, it should be asserted in terms of validity as the first thing.
This can be done with something as Objects.requireNonNull(arg), which will throw an exception if the argument is null.
Additionally, if you want to determine which arguments, should be allowed to be nullable, the @Nullable annotation can be used.
42. Prefer Lambdas To Anonymous Classes
When using event listeners, comparators, or simple interfaces, which promises one method implementation, it is valuable to use lambdas, since there is no need to use multiple lines of boilerplate code to call the only method available.
Use enums instead of integer constants
Before the introduction of enums, it was common practice to use integer constant values to indicate different variations of domain constants.
26. Don’t Use Raw Types
Since Java 5, generics were introduced. However, before that Collections (e.g. List) where still part of the language.
With generics it became possible to declare, inside the diamond declaration (), which type a List would be working with. Without a diamond declaration, it would be classified as a raw type.
Because of backwards compatibility these raw types where not removed after java 5’s release. However, regardless of them being part of the language, they should never be used.
Raw types enable the possibility to add unintended objects to the List, which will throw an exception at runtime.
Your Code as a Crime Scene (Affliate Link) is essentially a book about utilization of version control systems (VCS) to analyze and determine hotspots in the codebase.
15. Limit Accessibility To Classes And Members
Generally, any class or member of a class should have the lowest possible access level, which still allows for its functionality to work.
API Example:
Take the case of an externally exposed API, where the interface represents all public accessible methods. Any implementation of this interface should only have public access level on the implemented methods.
The additional members of the implementing class should never be made public. Ideally private or package-private if required for unit testing.
In the case of the exposed API, any publicly available member of the implementation will have to be supported forever, if they have once been published. If members are degraded to a lower access level, it will ruin the API’s backwards compatibility.
The composite design pattern is intended for structuring data classes with a relationship to each other. It categorizes the data as either a composite- or and leaf class, which determines whether other classes can be stored within the class. For this reason, it should come as no shock that it is a structural design pattern.
The Facade Pattern is based on the concept of simplifying activities. It allows us to wrap complex procedures in a facade class and afterwards utilize these procedures by one simple method call. For this reason it is categorized as a structural design pattern. ​
The Adapter Pattern is a simple, yet convenient, utility, which you will most certainly find good use of.
The pattern uses and interface and its implementation to create a layer around another object, which then allows the behavior of the object to be converted into a desired form.Â
INTEGU uses cookies to personalize your experience and provide traceability for affiliate links. By using the website, you agree to these terms and conditions. To learn more see the privacy policy page.
