Simple Is not Simplistic

From WikiContent

(Difference between revisions)
Jump to: navigation, search
Line 15: Line 15:
# The time necessary to implement it (when do the users ''really'' need it?)
# The time necessary to implement it (when do the users ''really'' need it?)
-
Unfortunately, many developers skim through point (1), and assume that the users actually know what they need, then think about point (2) forgetting the "cleanly" bit, skip point (3) altogether, and try to cut the time at point (4) as much as possible, and equate this to a "simple" solution, when in fact, it is a simplistic one.
+
Unfortunately, many developers skim through point (1), and assume that the users actually know what they need, then think about point (2) forgetting the "cleanly" bit, skip point (3) altogether, and try to cut the time at point (4) as much as possible, and equate this to a "simple" solution, when, in fact, it is a simplistic one.
[this is still work in progress]
[this is still work in progress]

Revision as of 13:46, 8 May 2009

"Very often, people confuse simple with simplistic. The nuance is lost on most." Clement Mok.
"Simplicity before understanding is simplistic; simplicity after understanding is simple." Edward de Bono.

First of all a couple of definitions (from the "New Oxford Dictionary Of English"):

  • simple easily understood or done; presenting no difficulty
  • simplistic treating complex issues and problems as if they were much simpler than they really are

I'm sure that most developers know that simple software is more maintainable, has fewer bugs, has a longer lifetime, etc., and that they always try to implement the simplest solutions they can possibly think of. We also know that many of those developers often end-up with unmaintainable code very quickly.

In my experience, the most common reason for that is due to lack of understanding of the problem being solved. In fact, when implementing a new piece of functionality, the real problem being solved has several aspects:

  1. The users' requirements (is what the users are asking for, what they really need?)
  2. How to fit the functionality into the system cleanly (what parts of the current system need to change, if any, to accommodate it nicely?)
  3. What and how to test (How can I prove that the functionality is implemented correctly? How can I make the tests simple to write and simple to run?)
  4. The time necessary to implement it (when do the users really need it?)

Unfortunately, many developers skim through point (1), and assume that the users actually know what they need, then think about point (2) forgetting the "cleanly" bit, skip point (3) altogether, and try to cut the time at point (4) as much as possible, and equate this to a "simple" solution, when, in fact, it is a simplistic one.

[this is still work in progress]


By Giovanni Asproni


This work is licensed under a Creative Commons Attribution 3

Back to 97 Things Every Programmer Should Know home page

Personal tools