Java Common Mistakes and Best Practices

Question 1

Thinking about optimization even before implementation starts.

Best start with a simple solution, then optimize and refactor

Answer 1

Premature Optimization

Question 2

Spending too much time on debating or deciding trivial matters.

Be aware of the time spent on decision making and try to reduce it to acceptable bounds.

Answer 2

Bikeshedding

Question 3

Too much analysis leading to paralysis

Similar with Premature Optimization, start with a simple solution and adjust and refactor as necessary

Answer 3

Analysis Paralysis

Question 4

Classes with too many responsibilities and dependencies

Design your code to be more modular and keep DIP in mind

Answer 4

God Class

Question 5

Better to break large classes into smaller, more manageable ones

Answer 5

Fear of Adding Classes

Question 6

Re-implementing features that are already built in to the platform

Be knowledgeable of the features that your platform has. This takes time and mastery.

Answer 6

Inner-platform Effect

Question 7

Using unnamed Strings or Literals in your code that seem to come out of nowhere.

Better use constants or variables to avoid this anti-pattern. It results into more readable code and more flexible program.

Answer 7

Magic Numbers and Strings

Question 8

Reliance on “numbers” for deceision making

Can be observed in bigger companies and workplaces. 

“Numbers” should serve as a guide

Answer 8

Management by Numbers

Question 9

Restructure code to get rid of these.

Answer 9

Useless (Poltergeist) Classes