This is review of the 2nd chapter from the book-”Clean Code: A Handbook of Agile Software Craftsmanship” by Robert C. Martin

What’s in a name- eh?

Well consider this- 90% of the code we write is nothing but a collection of names that we have written- be it names of classes, variables,functions etc.

Rest 10% are the keywords of the underlying programming language that you are using along with expressions and operatives.

Good selection of names= Good readability and clear intent.

In this Chapter- Robert goes through a series of rules of defining good names- all very practical advices.

Use Intention revealing names

Avoid dis-information

Make meaningful distinctions

Use pronounceable names

Use searchable names

Avoid encodings

Avoid mental mapping (no matter how smart you are !!!)

Don’t pun

Pick one word per concept

For other chapters- please see this post.

   
© 2011 Technology Cafe Suffusion theme by Sayontan Sinha