Thursday, January 25, 2007

Corporate Code Smells

Mostly venting here, how many of these have you seen?

Corporate Code smells:
  1. WSAD - There is a reason it isn’t called WHAPPY
  2. Only javadoc is the eclipse message telling you how to change your default javadoc templates
  3. No interfaces at all or an interface for every class
  4. junit.jar exists in the lib directory but no tests to be found
    • I got this unit test that calls the production database
  5. optimized imports? code formatting? we don’t have time in the project plan for that
  6. Sure we use Spring, but we wrap it with our own classes so we can switch it out later
    • We’ve cached the bean instance returned by Spring to speed things up
  7. We added hibernate because we knew we were going to hit the database
  8. Synchronization? Threads? the container takes care of that
  9. Guys, look at this framework I cranked out last night!
  10. With annotations I was able to expose all my classes as web services, you know, for reuse!

No comments: