Reading Josh Robb's post on Naming Things jogged my memory about some things I was thinking the other day in regards to naming objects and design patterns. One thing that design patterns give us, is a common language used to describe abstract concepts. The easier it is to put a name and definition to something, the easier it is to conceptualize. I believe most of us use design pattern names in our object names, but like Josh, I sometimes struggle to come up with a good name for an object. When I do come up with a name that I'm satisfied with, I wonder if it will be meaningful to someone else. The fact that I struggled with the name in the first place may be a sign that it won't. I hate it when you know you need a little object to do something and it takes longer to come up with the name than to write the object. With TDD, you can end up with a lot of classes, so you need a lot of names. I can't help thinking that this is a problem about standardization. When I struggle with a name, I always think that there should be a standard for this which would make it a no-brainer. Is there a good book out there that defines a set of micro patterns related to TDD that would be a good reference for names? Maybe it's just me and my limited East Texas vocabulary?
Technorati Tags:
TDD,
Design Patterns