Hi guys, it’s been a while that I haven’t posted anything. I was thinking writing all those technical things sometimes is not enough for the reader to visualize the concept. So I came up with a screencast this time. I’ll try to create these screencasts once a week and will cover different topics. This series will contain Making Code More Testable talks only. For other topics, I’ll create different series. Anyways, let’s get back to the overview :)
Maximizing Reuse Minimizes Use
A nice modularity tip that should be considered when you’re designing a modular system:
Naming the Java Implementation Classes
Today I was reading an answer to a question (http://bit.ly/FkgKB) about naming the implementation classes. People in these days are using Impl suffix to their implementation classes which implements a certain interface. For instance, if your interface name is Item, your implementation class name would be ItemImpl. Honestly I hate this bullshit naming convention. And I’ll forever blame the guy who invented such a crappy naming. Actually I first saw this naming convention in the IBM Developerworks articles. I guess it is some sort of IBM crap (I never got along with any of IBM related thing so far though). Anyways, let me tell you why it’s crappy:
