Reduced duplication, high expressiveness and early building of simple abstractions. That's what makes clean code for me.

Clean Code

<ul><li>﻿Use intention revealing names (elapsedTimeInDays vs d) </li><li>Class names should contain nouns and not verbs. Avoid Manager, Processor, Data, Info in class names. </li><li>Method names should have verbs. Accessory, mutators and predicates should be named for their values and prefixed with get, set, is</li><li>Use searchable names</li><li>Make meaningful distinctions</li></ul>

Ch2. Meaningful Names

Looks at the principles and clean code, includes case studies showcasing the practices of writing clean code, and contains a list of heuristics and "smells" accumulated from the process of writing clean code.

books

Books

Even bad code can function. But if code isn't clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn't have to be that way. Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship. Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code "on the fly" into a book that will instill within you the values of a software craftsman and make you a better programmer--but only if you work at it. What kind of work will you be doing? You'll be reading code--lots of code. And you will be challenged to think about what's right about that code, and what's wrong with it. More importantly, you will be challenged to reassess your professional values and your commitment to your craft. Clean Code is divided into three parts. The first describes 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. Readers will come away from this book understanding <ul> <li>How to tell the difference between good and bad code</li> <li>How to write good code and how to transform bad code into good code</li> <li>How to create good names, good functions, good objects, and good classes</li> <li>How to format code for maximum readability</li> <li>How to implement complete error handling without obscuring code logic</li> <li>How to unit test and practice test-driven development</li> </ul> This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.

Robert Cecil Martin, commonly called Uncle Bob, is a software engineer, advocate of Agile development methods, and President of Object Mentor Inc. Martin and his team of software consultants use Object-Oriented Design, Patterns, UML, Agile Methodologies, and eXtreme Programming with worldwide clients.He was Editor in Chief of the C++ Report from 1996 to 1999. He is a featured speaker at international conferences and trade shows.

hei you's Key Ideas from Clean Code
by Robert C. Martin

RON JEFFRIES

Ch2. Meaningful Names

hei you's ideas are part of this journey:

Related collections

Different Perspectives Curated by Others from Clean Code

Discover Key Ideas from Books on Similar Topics

hei you's Key Ideas from Clean Codeby Robert C. Martin

RON JEFFRIES

Ch2. Meaningful Names

hei you's ideas are part of this journey:

Related collections

Different Perspectives Curated by Others from Clean Code

Discover Key Ideas from Books on Similar Topics

hei you's Key Ideas from Clean Code
by Robert C. Martin