Use int, long (primitives), instead of their objects (Integer, Long)
primitives are the atomic, basic, data types, unless you know what you are doing, stick to those.
They (primitives) are passed by value. Long and Integer are the object form of the primitives, to be avoided unless you need to pass by reference, or pass and make the code infer the type.
sample of using inline filters:
somelist.stream().anyMatch(s -> s.getId() == COMPARE_ID)
where s is a particular member of somelist, with getId() as a method, and we are just picking the one where id match COMPARE_ID in this case
Spring / autowire
- when you see it on a class, it pretty much means “you are going to need one of these, and I am going to wire it for you”. Example:
public class SomeClass {
...
private ChallengeManager challengeManager;
@Autowired
public void setChallengeManager(@Qualifier(SpringConstants.COMPONENT_CHALLENGE_MANAGER) ChallengeManager challengeManager) {
this.challengeManager = challengeManager;
}so when SomeClass gets spawned, it will automagically include the class marked by @Autowired
the @Qualifier(SOMECONSTANT) is to ensure it is the class you want to autowire
in complex systems, there may be more than one ChallengeManager, so that qualifier and constant will make sure we are auto wiring the right one
Throwing and catching
if an interface is marked as “throws”, there should be a try catch that deal with the specified throwable exception in there
but if you want to make the parent calls of the class / method to deal with it instead, you can just add “throws ExceptionName” in the signature