>>>Hi everybody,
>>>
>>>I am wondering what principles do you use when naming classes (and their methods / properties)? Do you know a good article on this topic?
>>>
>>>Say, right now I am thinking of how to name a class. My colleague suggested to use 'CurrentCallObject' for the class name, but I am not sure I like it. On the other hand, I don't have a better idea.
>>>
>>>This class is going to be instantiated on each invoke call (this call comes from C++ application) and will hold attributes related to the call.
>>>
>>>Thanks in advance.
>>
>>Watch this - you'll never wonder again because you'll know
>>
>>Clean Code: Writing Code for Humans
>>
http://pluralsight.com/training/courses/TableOfContents?courseName=writing-clean-code-humans&highlight=cory-house_writing-clean-code-humans-m3-naming*1!cory-house_writing-clean-code-humans-m8-demo*7#writing-clean-code-humans-m3-naming>>
>>It's a 3 hr course - have only watched 30 min or so. I then started changing some names of methods/variables, etc. I bet you willl as well
>>I
>
>I saw Cory's presentation on this at Heartland Developer's Conference live and it was easily the best of the entire conference. Good dude, good presenter, good topic. Follow him on twitter if you're not: @housecor.
Thanks, still have 2:30 hours to watch
Gregory