Clean Code Craftsmanship

Undergoing a recent change in paradigm as to what coding means to me. I have the first prompt to undergo a session with the book “Clean Code” by Author Robert C. Martin. I would be putting out important one liners as I go through this Agile Software Craftsmanship grail.

Below are some of the points I picked;

If names must be different, then they should also mean something different

…smaller classes and shorter functions so that people can usually see the point of declaration of each variable they’re using

One difference between a smart programmer and a professional programmer is that the professional understands that clarity is king

A class name should not be a verb

Methods should have verb or verb phrase names

Choose clarity over entertainment value

Say what you mean. Mean what you say.

Pick one word for one abstract concept and stick with it

Don’t Pun… Avoid using the same word for two purposes

Remember that the people who read your code will be programmers. So go ahead and use computer science (CS) terms, algorithm names, pattern names, math terms, and so forth

Separating solution and problem domain concepts is part of the job of a good programmer and designer. The code that has more to do with problem domain concepts should have names drawn from the problem domain

you need to place names in context for your reader by enclosing them in well-named classes, functions, namespaces, or prefixing the name may be necessary as a last resort

The hardest thing about choosing good names is that it requires good descriptive skills and a shared cultural background

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.