در طراحي و ساخت محصولات نرم‌افزاري، سادگي اصلي است بسيار مهم. سادگي راه حل و طراحي معيار مهمي در انتخاب گزينه‌هاي مختلف است. به همين دليل، پيدا كردن راهي براي بازتعريف سادگي با هدفِ اعمال آن در طراحي‌ها و راه‌حلهاي مبتني بر نرم‌افزار موضوع مهمي خواهد بود. John Maeda در كتاب The Laws of Simplicity ده اصل و سه كليد براي سادگي معرفي كرده است كه مطالعه‌ي آن مفيد است. اگر منبع ديگري مي‌شناسيد لطفاً معرفي نماييد. براي اطلاعات بيشتر به اين سايت نيز مي‌توانيد مراجعه نماييد.

The Laws of Simplicity
Reduce
The simplest way to achieve simplicity is through thoughtful reduction.
Organize
Organization makes a system of many appear fewer.
Time
Savings in time feel like simplicity.
Learn
Knowledge makes everything simpler.
Differences
Simplicity and complexity need each other.
Context
What lies in the periphery of simplicity is definitely not peripheral.
Emotion
More emotions are better than less.
Trust
In simplicity we trust.
Failure
Some things can never be made simple.
The one
Simplicity is about subtracting the obvious, and adding the meaningful.

Three Keys
Away
More appears like less by simply moving it far, far away.
Open
Openness simplifies complexity.
Power
Use less, gain more.

Quote:
Technology has made our lives more full, yet at the same time we’ve become uncomfortably “full”. John Maeda

برآمد باد صبح و بوی نوروز
به کام دوستان و بخت پیروز
مبارک بادت این سال و همه سال
همایون بادت این روز و همه روز

سال نو مبارک

منبع: از ميان نامه‌هاي نرگس

گزيده:

If a low price is more important to you than getting good value for your money, you’re not as prosperous as you think you are.
ref: J2ME development forum

تصویر زیر را یکی از دوستانم برایم ارسال کرده بود (محمدرضا). امیدوارم که این تصویر همان طور که باعث خندیدنم شد، شما را نیز بخنداند.

گزيده:

“Science is a differential equation. Religion is a boundary condition” – Alan Turing

[Evaluating Software Design Patterns — the “Gang of Four” patterns implemented in Java 6]

In this project, we perform an evaluation of the “Gang of Four” design patterns from a practical and experimental point of view using Java 6 as the implementation language. We investigate how Java 6 language features affect the application of the “Gang of Four” design patterns, individually and collectively. The investigation focuses on how the practical use of language features can affect the design pattern implementations, not how the features are constructed. To perform a reasonably structured and verifiable evaluation, we define a general evaluation approach on how to evaluate the “Gang of Four” patterns using a language as a catalyst. …
Using the defined approach, we implement the “Gang of Four” patterns in Java 6 and investigate use of core language features (types, generics, closures, etc.), reflection (class literals, dynamic proxies, annotations, etc.), and special language mechanisms (synchronisation, serialization, cloning, etc.).

>> To find complete thesis and “one of his great supporters” see here

Quote:
Data is not information. Information is not knowledge. Knowledge is not understanding. Understanding is not wisdom. Anonymous
ref: Booch weblog

به ياد ديار پدري: کرنا نوازان گيلاني مرثيه مي‌دمند

گزيده:
داشتن علم بهتر از داشتن ثروت است ولی نداشتن ثروت بدتر از نداشتن علم است.

«We are some people who have observed software engineering theory and practice of the past decades and have realized that it is now time to revitalize this discipline. We have been quietly planning a “revolution”.
Since then I have advanced gradually. First, I explored this idea by publishing a paper, entitled “In need of a theory in software engineering”, first in China (in Chinese) and then in Australia. Later on I joined forces with two colleagues of mine, Bertrand Meyer, the creator of Eiffel, and Richard Solely, the chairman of OMG. We have formed a community called SEMAT (Software Engineering Method and Theory). Its goal is to make software engineering a more systematic discipline than it has been in the past.
This effort started with a Call for Action a few weeks ago. To put it in a sharply simplified way, we state: 1) software engineering is not a mature discipline, and 2) this situation has to be changed fundamentally ”based on a solid theory, proven principles and best practices that include a kernel of widely-agreed elements,” etc.
The big challenge of this initiative is to achieve consensus among so many strong and driving forces. SEMAT differs from other initiatives in that we are not trying to unify the world around a method, but rather, focusing on the creation of a small kernel that contains elements that we always have when we develop software. We call these kernel elements universals. Furthermore, we insist that industry and research communities should be harmonized. Both of them have their strengths and have their unique roles to play, but they need to work together as a team resulting in a synergy for us to be successful.»
Reference: Ivar Jacobson’s Blog

گزيده:
تجربه نامي است كه همه ما بر اشتباهات خود مي‌گذاريم. اسكار وايلد
مرجع: كتاب نكته‌هاي ناب اثر مرتضي اسد‌خواه