###Code Smells
Code Smells
###Naming Conventions
Naming Conventions
###Repetitive Code Patterns
Repetitive Code Patterns
Exception Handling
###Resource Leaks
Resource Leaks
Objects and other Variables are nouns. Methods and other functions are verbs. Name them accordingly. Do not use acronyms or abbreviations, but do not use sentences for your names either. There is no need for joining words such as 'The', or 'With'. Most importantly, one should also always strive to maintain consistent naming convention, whatever style you choose. This is more in reference to @Shree's use of executeWithPreparedStatement.
Re-using names that you are deriving from is OK when you are recreating a function that does the same thing in a different way. It is not OK when you arehave extended the functionality of the code you are deriving from. Pick a new name that better describes why your method is different than the original.
Objects and other Variables are nouns. Methods and other functions are verbs. Name them accordingly. Do not use acronyms or abbreviations, but do not use sentences for your names either. There is no need for joining words such as 'The', 'With'. Most importantly, one should also always strive to maintain consistent naming convention, whatever style you choose. This is more in reference to @Shree's use of executeWithPreparedStatement.
Re-using names that you are deriving from is OK when you are recreating a function that does the same thing in a different way. It is not OK when you are extended the functionality of the code you are deriving from. Pick a new name that better describes why your method is different than the original.
Objects and other Variables are nouns. Methods and other functions are verbs. Name them accordingly. Do not use acronyms or abbreviations, but do not use sentences for your names either. There is no need for joining words such as 'The' or 'With'. Most importantly, one should also always strive to maintain consistent naming convention, whatever style you choose. This is more in reference to @Shree's use of executeWithPreparedStatement.
Re-using names that you are deriving from is OK when you are recreating a function that does the same thing in a different way. It is not OK when you have extended the functionality of the code you are deriving from. Pick a new name that better describes why your method is different than the original.