Geeks With Blogs
Catherine Russell Architect, President of "Women In Information Technology" Group

Clean Code is divided into three parts.
The first part are the principles, patterns, and practices of writing clean code.
The second part consists of several case studies of increasing complexity.
Each case study is an exercise in cleaning up code—of transforming a code base
that has some problems into one that is sound and efficient.
The third part is the payoff: a single chapter containing a list of heuristics and “smells”
gathered while creating the case studies.
The result is a knowledge base that describes the way we think when we write, read, and clean code.

This book covers:
How to tell the difference between good and bad code
How to write good code and how to transform bad code into good code
How to create good names, good functions, good objects, and good classes
How to format code for maximum readability
How to implement complete error handling without obscuring code logic
How to unit test and practice test-driven development
This book is a must for any developer, software engineer, project manager, team lead,
or systems analyst with an interest in producing better code.

To read more go to:
Clean Code: A Handbook of Agile Software Craftsmanship
Robert C. Martin 

Posted on Sunday, December 13, 2009 8:09 PM Tutorials , Patterns | Back to top

Comments on this post: Writing a Clean Code.

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © CatherineRussell | Powered by: