Every so often, you see code that someone else has written—or code
that you wrote—and smack your head in wonder, disbelief, and dismay.
My previous article, “Ten Java coding antipatterns to avoid: Worst
practices #10 through
#6,”
explores five of those antipatterns. I’ll conclude the discussion
here with the final five worst practices, plus a bonus.
I’ll reiterate what I wrote in the previous article’s introduction:
You should avoid these worst practices—and eliminate them when you
maintain or refactor existing code. And, of course, resolve them if
you see these issues during a code review.