Single Purpose Principle

This is one of the most important principles in clean programming.

It applies to:
  • Interfaces
  • Classes
  • Methods
  • Whole Modules
The piece of code should be named to precisely reflect the functionality in contains and it should be developed,  and subsequently extended, to preform ONLY the functionality intended.

If there is a need to add different functionality, a new piece of code should be refactored out.







by Uki D. Lucas on Tuesday, July 29, 2008
find similar posts: ,
As an Amazon Associate I earn from qualifying purchases.

My favorite quotations..


“A man should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects.”  by Robert A. Heinlein

"We are but habits and memories we chose to carry along." ~ Uki D. Lucas

Popular Recent Articles