Sök
Hjälp?
Behöver ni experthjälp med något programmeringsärende eller vill ni kanske fråga om råd inför en IT-investering? Kontakta mig så ska jag försöka hjälpa er!Nyckelord
Addon Apache Computer CSS Design Development Download Error Firefox Google HOWTO HTML Internet Internet Explorer iPhone JavaScript JeOS Linux Microsoft MSDN MySQL NoScript Open Source Opera Patent Perl php Programmering Recension Roligt rsync Safari Security SEO Server Slow Software SSH Ubuntu Virus Visual Basic VMWare Web Windows Wordpress
Nyheter från New SeedAnnons
Arkiv
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- October 2009
- September 2009
- June 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
Tag Archives: Project
Worse is Better
I recently found an article of an outdated development philosophy called Worse is Better. The term was coined by Richard P. Gabriel in an article about LISP and alludes to the “Less is more” slogan.
In Worse is Better-design simplicity is held above all other traits of development. Wikipedia summerizes the traits:
- Simplicity
- the design must be simple, both in implementation and interface. It is more important for the implementation to be simple than the interface. Simplicity is the most important consideration in a design.
- Correctness
- the design must be correct in all observable aspects. It is slightly better to be simple than correct.
- Consistency
- the design must not be overly inconsistent. Consistency can be sacrificed for simplicity in some cases, but it is better to drop those parts of the design that deal with less common circumstances than to introduce either implementational complexity or inconsistency.
- Completeness
- the design must cover as many important situations as is practical. All reasonably expected cases should be covered. Completeness can be sacrificed in favor of any other quality. In fact, completeness must be sacrificed whenever implementation simplicity is jeopardized. Consistency can be sacrificed to achieve completeness if simplicity is retained; especially worthless is consistency of interface.
There have been many development methods that have been hyped lately but I’ve never heard about this one before and yet I think that I’ve been involved in several projects where the values of this approach have been used. I dare say many website projects have had this overall strategy. Most of all I think this is a valuable approach while learning a new programming technique (such as a framework or programming language).
Posted in Programmering
Tagged Approach, Completeness, Consistency, Correctness, Development, Management, Philosophy, Project, Simplicity, Software
1 Comment