As we've looked at before, simplicity is a funny word. Sometimes hard to understand. Always hard to accomplish.
As Software Architects, one of our greatest responsibilities is to vacuum up the chaos and distill it into a rational and valuable (even pleasant) reality. One of the keys to success on this dimension is simplicity, which I tend to think of in the following ways:
"Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." (Antoine de Saint-Exupery)Finally, as I'm defining it, the goal of simplicity is nicely summed up in the following quote from Paul Preiss, President of IASA, in a recent webcast, "A Guide to the Architecture Profession":
"Simplicity--the art of maximizing the amount of work not done--is essential." (Agile Manifesto)
"Treat every problem as if it can be solved with ridiculous simplicity. The time you save on the 98% of problems for which this is true will give you ridiculous resources to apply to the other 2%." (Dr. Paul MacCready)
"80% of the results come from 20% of the effort." (Pareto Principle or 80/20 rule)
"Our responsibility is to build as little software as possible to add shareholder value."Let's get out there and build less software! Oh, and lets simply do it with less effort!