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?
In fact, Wikipedia refers to all of them as principles:
In software engineering, Don't Repeat Yourself (DRY) or Duplication is Evil (DIE) is a principle of software development
KISS is an acronym for the design principle "Keep it simple, Stupid!".
The principles when applied together intends to make it more likely that a programmer will create a system that is easy to maintain and extend over time
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.
protected by gnat Sep 22 '16 at 5:54
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?