Is something like DRY a design pattern, a methodology, or something in between? They do not have specific implementations that could neccessarily be demonstrated(even if you can easily demonstrate a case NOT using something like KISS... see The Daily WTF for a plethora of examples), nor do they fully explain a development process like a methodology generally would. Where does that leave these types of "rule of thumb"'s?
- Anybody can ask a question
- Anybody can answer
- The best answers are voted up and rise to the top
In fact, Wikipedia refers to all of them as principles:
I'd say that they're basic engineering principles.
A methodology can have n principles.
And they're definitely not design patterns :)
These are the guidelines for your everyday work, crossing the boundaries of layers, problem domains and technologies.
They also form what you would call a philosophy defining your professional practice.