This blog post is part of a series of blog posts concerning a Clean Code study circle that we developers at Admeta are persuing during 2009. Here you can find an introduction concerning the question why we are doing this and here you can find an overview of all chapters as well as some study circle recommendations.

Questions: Chapter 2 Meaningful Names

1. What do you think is the characteristics of a good name?
2. Do you take IDE Code Completion into consideration when labeling namespaces, class names and its members?
3. Have you reflected upon "noise words" in names before?
   
4. If you have a class property of type int named Age, but you discover that you would actually want an Age property of type string as well. How would you handle this?
5. Are you or have you been using Hungarian Casing? Why? Do you agree with the books statement that it should not be used in modern languages?
6. Having a prefixed I for interface is an established Microsoft convention. Do you agree with this? Why?
   • Extra (Design considerations): Interface vs Base classes [1], [2], [3], and [4].
7. Do you think "Duck Typing" is something good and do you see Duck Typing as possible in a typed language as C# v3?
   • How far should we utilise the support for Duck Typing in CS 3?
8. Would you consider complexity of code as a beautiful thing or do you agree with the books ways of seeing such practices to write complex code deliberately as a personal quest to show off mental capabilities?
9. Is there any benefit of using constructor (or a static factory method that produces the object) as a way to inject dependencies compared to properties/mehtods?
10. Design: So you find the concept of Value Object as a useful pattern?
11. What is your opinion on PascalCasing and camelCasing?
    • Do you have a deviating opinion from Microsofts recommendations of when to use which?
12. Are there any rules in Chapter 17 that you think originates from this chapter?
    • Is there any rule that you are missing from what you have read in this chapter?

The context of our study sessions is restricted to .NET and C#, thus the nature of the questions above.