- Don't use the Lombok @EqualsAndHashCode annotation unless strictly necessary and consider why it is needed. - Use '==' instead of .equals() to compare enums to avoid potential compile errors. - Avoid generic method names like 'preSave' and 'postCreate' as developers must inspect the method body to understand what it does; clearly describe a method's purpose in its name instead. - For example, rather than a 'create' method calling 'preSave', have it perform validations and other requirements directly rather than obscure actions with generic names.

1. Coding Practice

2. lombok
● Don’t use @EqualsAndHashCode unless you really need it
● Consider why you need @EqualsAndHashCode if you really need it

3. Enum
● Use ‘==’ to compare, not equals.
‘==’ can introduce compile error when trying to compare inconsist enum
●

4. Method name
● Don’t use method such as ‘preSave’ ‘postCreate’
Developer must click into method to know what is doing
● Take care of abstraction level
Maintainer should be able to understand method’s responsibility without dig
into method implementation

5. Method name - example
● Bad
public MyModel create(MyModel model) {
preSave( model );
configService.persist( model );
}
● Good
public MyModel create(MyModel model) {
validate(model);
model.setDomainId( domainId ); // feature requirement in this example
configService.persist( model );
}