# Laws, Rules, Principles, Patterns, and Practices

I speak and write a lot about principles, patterns, and practices.  There has been a lot of hullabaloo lately about blind, rigid adherence to principles and how, apparently, this will result in some sort of catastrophe. Frankly, if we, as a profession, ever got the point where we were too rigidly following things like the SOLID principles, I think we’d be doing pretty good and that it would generally be a good problem to have (like having too much money or one extra piece of cake – a problem no doubt, but a good problem and one easily solved).

Amidst all the chest pounding and spitting, there appears to be some sort of confusion among the various words and definition. In a laughably futile attempt to try to inject some sort of rationalism and logic into the debate, I’d like to take a stab at defining what the following words mean, in the context of the practice of software design:  Laws, Rules, Principles, Patterns, and Practices.

## Law

Think more of the scientific definition of “law” than the governmental/legal definition.  For example, the Merriam-Webster dictionary defines it as:

6a: a statement of an order or relation of phenomena that so far as is known is invariable under the given conditions.

That’s a pretty good definition. To me, that means: Given X, if you do Y, the outcome will always be Z.  That’s a bold statement, thus the gravity of the use of the word “Law” in the context of design (something that has a lot of subjectivity). It’s not entirely subjective, however, and so laws CAN apply.

These are pretty rare in software design due the fact that it is still quite young and there is very little science involved (in order to prove anything).  Thus we must fall back to what little experience, observation, and empiricism we have available to us.  So far only one of these comes to mind (sorry, I’m drawing a big blank): Law of Demeter.

## Rule

I think I’ll referencing good ol’ M-W on this one again:

1 a: a prescribed guide for conduct or action, … c: an accepted procedure, custom, or habit

So we’re talking about something quite different from a law. A law is an observation of behavior of some phenomena whereas a rule is something we, as professionals, impose upon ourselves.  You can break a law and you will feel the pain and consequences for it. Breaking a rule is quite different. There may not be any consequences unless your colleagues hold you to it.  Rules, in my experience, are best prescribed by the individual team members for themselves and their own conduct. They should hold themselves accountable to each other and share the consequences in their violation (if any).

Rules are a way of enforcing consistency within a team, project, or set of projects. They do not enforce quality (unless your rules are designed to do that), they enforce consistency.  You can have a set of rules that produce consistently poor quality software just as easily as high quality software.

Some good examples of rules I might suggest you, together with your team members, place upon yourself are things like:

• Personal hygiene: Learn it, live it, love it.
• Follow CI and all the other minimal practices and requirements for good software
• Don’t commit into a broken build
• Don’t commit spike code into the trunk
• Don’t use the words “stored procedure” around Jeremy

## Principle

M-W defines this one as so:

1 a: a comprehensive and fundamental law, doctrine, or assumption

I have to admit, I was a little thrown back by that one. To me, “Principle” was never quite that strong. M-W suggests that it’s actually stronger than a law.  For now, I’ll defer to what the apparent popular usage of this word is within the development community versus what the dictionary actually says.

Principles are very important to me when I design software. People say things like “rigid adherence to principles” as though it’s a bad thing. In my practice, it seems to usually be a good thing and I can’t recall it ever being a bad thing. The key here is, though, that you must know and understand the principle well to ensure you’re actually following it and not some misguided misinterpretation.

To me, principle means something closer, but more loose, to Law rather than a Rule.  Principle means this to me: Given X, if you do Y, the outcome will likely be Z. Note the addition of the word ‘likely’.   Conversely, given X, if you do not do Y, the outcome will likely be A (or at least not Z).

Principles help guide me in the right direction and serve as a canary-in-the-mineshaft to tell me when I’m going in the wrong direction.  I say “guide” not “steer” because sometimes I knowingly violate those principles to serve some end. I do so with understanding of the consequences and that’s OK.

There are many principles – too numerous to list here unfortunately. The SOLID principles linked above are a good place to start, though.

## Pattern

Pattern is merely an implementation detail: A standard, known-good way of solving a particular problem. I use patterns within the context of design laws, principles, and our self-imposed rules. Patterns help me work within a given design to implement it. Patterns themselves are not ends, only the means to a greater end.  Unfortunately, patterns are severely abused and consequently end up getting a bad rap because they are the most visible elements of a failed design.

A good set of examples of patterns come from the  book “Design Patterns: Elements of Reusable Object-Oriented Software.” NOTE: If you have this book already, or are planning on getting it, PLEASE read the first chapters – especially the parts about “composition versus inheritance” as these are crucially important.  Many people (myself included) skipped right over these chapters and dove right into the meat of the patterns – to our great folly.

## Practice

A practice is more like a rule than a law of principle.  A good way to look at a practice is a means by which a rule, principle, or law is adhered to.  Adopt practices to help follow the rules, principles, and laws you find important.  Establishing practices and good habits will increase your success rate of appropriate adherence to the rules, principles, and laws your team has chosen to follow.

Practices also serve as a means by which you can detect when you’ve fallen away from your adherence. This may be deliberate and conscious, or it may be accidental. Either way, you’re aware of it and can take appropriate action (continue down this path, knowingly, or correct it).

Examples of practices include: Continuous Integration, Check-in Dance, Test-Driven Development, and daily stand-up meeting.

#### Related Articles:

Post Footer automatically generated by Add Post Footer Plugin for wordpress.

Chad Myers is the Director of Development for Dovetail Software, in Austin, TX, where he leads a premiere software team building complex enterprise software products. Chad is a .NET software developer specializing in enterprise software designs and architectures. He has over 12 years of software development experience and a proven track record of Agile, test-driven project leadership using both Microsoft and open source tools. He is a community leader who speaks at the Austin .NET User's Group, the ADNUG Code Camp, and participates in various development communities and open source projects.