Resume for Steven E. Newton


Readings for Code Janitors


Steven E. Newton
Crater Moon Development
© 2003-2023

Coding Pet Peeves

3 Jun 2015 515 words. (3 min)

Eight little things I like to nitpick about in code. Mostly applicable to Java, but some are language-neutral.

  • Don’t return null, return the Null Object. Checking for null in a returned value requires code that has nothing to do with the problem domain, and rarely does an API document what it means when a null is returned. My biggest beef is with methods that return a collection type return null. Just return the empty collection, and if it matters to the caller, check the size(). Often it’s completely reasonable for code that does something with each element in a collection to do it zero times if the collection is empty.

  • Only use Java interfaces to define types, not as namespaces for globals. I’ve seen it suggested many times in questionable guides to create an interface as a dumping ground for public static values. Just Don’t Do It. If the values have any meaning in the code, then they can be associated with the class that most closely operates with them. If the “class” is application configuration, then for Pete’s sake create a configuration class with the ability to do things like pick up options from a configuration file, environment variables, or command-line arguments.

  • Override toString for all value types. It’s simple enough to generate a readable representation of the properties of an object, and it’s tremendously useful in monitoring, logging, and debugging. Far better than the default of the class name and a meaningless VM address.

  • Sort import statements, starting with java., then javax., then other 3rd party, then com.mydomain.*. Within a group, alphabetize.

  • Import down to the class name, unless you have more than 3 imports in a package, then you may import .*. Both this and the previous one are made much simpler by tools like Eclipse that automatically organize imports. Both are just the sort of neatness that any skilled professional should expect.

  • Vwls r mprtnt. Can’t make heads or tails of that? Try this: “Vowels are important”. Code with class, method, and variable names that abbreviate out all the vowels in identifiers quickly becomes and indecipherable mess. I see this most frequently in code that is closely associated with a relational database schema, because DBAs seem to love dropping all the vowels. Avoid the temptation to aggressively abbreviate as well – an example being a proposal to abbreviate every word longer than 6 letters to 4 or less.

  • Never name a class Manager, Handler, or Data. Don’t use the nouns “Object”, “Manager”, “Handler”, or “Data” in class names. These words say nothing about the responsibility of the class, leading maintenance programmers to lump all kinds of irrelevant code into the class. Think instead about what the class is actually supposed to do and name it after that.

  • Abbreviations used mixed case in identifiers except where an overriding convention exists. e.g UmlIpParser is much more readable then UMLIPParser. For most of my recent employers, things like the company’s initials, the project’s code name, or the like, are examples of overriding convention. That’s OK because generally all the developers involved know the convention.

<-Unit Tests Manage Complexity Defect Reporting ->