Adhere to commonly used coding standards as set by Oracle, Eclipse, or Google. All major IDEs can format code according to the standards. Use "speaking" (i.e. self explanatory) names (variables, classes, and methods). Use constants (static final variables) instead of "Magic numbers". Whenever a number has a special meaning other than a simple counter, create a constant that explains the meaning of the number and use only the constant. Use comments to explain why something was coded in a certain way, not to explain how something was coded, or what the code does. Use JavaDoc to document your code. More on reddit.com

Use a database deployment tool like Liquibase or Flyway. Invaluable (and not Unvaluable :/). More on reddit.com

Calling .equals on a string This isn't a "best practise", it is "how to write code that actually does what you want it to do". Best practise implies it is still valid not to do it. Using entrySet to iterate over a hash map If you are only using the map for iterating across and never for key lookups, you shouldn't be using a map. That aside, Map#forEach exists for this purpose. Using enum as a singleton is threadsafe So is using a private static final field though... using an enum makes it less clear that you purely want a single singleton and not an enumeration. It is a hack. Using .wait/.notify APIs You almost never want to use these rather than the elements in java.util.concurrent, unless you are writing your own primitives, as they are higher level APIs, implement fairness, and don't cause problems with virtual threads under current JDKs. CloneNotSupportedException The best practise is just not to use cloning. Use copy constructors. Using iterators to iterate over a list in case it is a linked list Or just use an enhanced for loop or stream, which are the modern ways of dealing with cases like this. If you are wanting to iterate across a list and nothing else, then you shouldn't be using linked lists anyway, you should use array lists. LinkedLists are generally only beneficial for queues/stacks. Everything else will be slower than just using an ArrayList. If someone uses a LinkedList in code, I question whether it is micro-optimisation and whether it has benchmarks to prove it is needed. Here is the right way to close file streams No, it isn't. You should be using a try-with-resources block, not try-finally with nested try expressions within them. More on reddit.com

Research suggests the ideal individual code review session lasts about 60 minutes . Around this threshold, reviewers become drained, less focused, and unable to maintain peak accuracy. who tf reviews code for 60 minutes at a time? if my code reviews took that long I would spend 99% of my time reviewing code and doing literally nothing else. More on reddit.com