design - Reasons not to overdesign a solution to a current problem -

G'day,

I started thinking about thinking about this question here.

What can you provide to those people who insist on blowing out designs because "they want to use it somewhere else in the future"?

Similarly, what do you do when people take the requirements and then come back with many extra "bells and whistles" with bloated design, which you have not asked?

When you know that this makes sense, then I can understand the detail of a design for requirements or possible uses which are present either in the near future and I only need a list of requirements Accepting and advocating to apply it clearly, what you think you can remember.

I am saying that when people insist on adding or external functionality, so that "we can use it somewhere else in the future?"

There are many good reasons for Wikipedia.

• The time spent is taken from adding, testing, or improving the required functionality.
• New features should be debug, documented, and supported.
• Any new feature can be done in the future, obstacles have been put on it, hence, an unnecessary feature can now prevent an essential feature from being applied later on.
• Unless this feature is really necessary, it is difficult to completely define what it should do and test it. If the new feature is not properly defined and tested, it will not do the right thing, even if it is needed eventually.
• This code leads to Bloat; The software becomes bigger and more complex.
• As long as the specification and some modification controls do not take place, this feature may not be known to the programmer who could use it.
• The new feature may suggest other new features if these new features are also applied, then the result may be snowball effect towards the porousness.

See also: