THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
All test classes should be in the exact same package hierarchy as the source java class
All test classes should begin with Test for instance TestCSVInternmediateFormat.java instead of CSVIntermediateFormatTest.
If you see code duplicated, please create a JIRA and let us all know, we can collectively do the cleanup.
Do not try to catch exceptions that you do not know how to handle, let it bubble up.
Try to use the IDE to clean-up unused imports
Try not to create code with warnings. Especially when the IDE is screaming at you and telling you how to fix them!
Goes without saying, do not have functions that run 100 lines long. break them down so it is easy to read and unit test
- Use Log.DEBUG / Log.INFO statements generously in code that is not easy to follow. It helps the person debugging your code!
- Use IDE for
hashCode
andequals
andtoString
code generation. Use IDE for refactoring cues. - Apache Kafka Coding Guide very beautifully documents some of the basic stuff of writing code. Kindly read it.
...