Law of conservation of complexity (original) (raw)

About DBpedia

The law of conservation of complexity, also known as Tesler's Law, or Waterbed Theory, is an adage in human–computer interaction stating that every application has an inherent amount of complexity that cannot be removed or hidden. Instead, it must be dealt with, either in product development or in user interaction. This poses the question of who should be exposed to the complexity. For example, should a software developer add complexity to the software code to make the interaction simpler for the user or should the user deal with a complex interface so that the software code can be simple?

Property Value
dbo:abstract The law of conservation of complexity, also known as Tesler's Law, or Waterbed Theory, is an adage in human–computer interaction stating that every application has an inherent amount of complexity that cannot be removed or hidden. Instead, it must be dealt with, either in product development or in user interaction. This poses the question of who should be exposed to the complexity. For example, should a software developer add complexity to the software code to make the interaction simpler for the user or should the user deal with a complex interface so that the software code can be simple? (en)
dbo:wikiPageExternalLink http://www.nomodes.com/Larry_Tesler_Consulting/Home.html
dbo:wikiPageID 30699737 (xsd:integer)
dbo:wikiPageLength 3511 (xsd:nonNegativeInteger)
dbo:wikiPageRevisionID 1124196481 (xsd:integer)
dbo:wikiPageWikiLink dbr:Application_software dbr:Interaction_design dbc:Human–computer_interaction dbr:Programming_complexity dbc:Software_engineering_folklore dbr:Bruce_Tognazzini dbr:Adage dbr:PARC_(company) dbr:User_experience dbr:Larry_Tesler dbr:Human–computer_interaction
dbp:wikiPageUsesTemplate dbt:Reflist
dct:subject dbc:Human–computer_interaction dbc:Software_engineering_folklore
gold:hypernym dbr:Adage
rdfs:comment The law of conservation of complexity, also known as Tesler's Law, or Waterbed Theory, is an adage in human–computer interaction stating that every application has an inherent amount of complexity that cannot be removed or hidden. Instead, it must be dealt with, either in product development or in user interaction. This poses the question of who should be exposed to the complexity. For example, should a software developer add complexity to the software code to make the interaction simpler for the user or should the user deal with a complex interface so that the software code can be simple? (en)
rdfs:label Law of conservation of complexity (en)
owl:sameAs freebase:Law of conservation of complexity wikidata:Law of conservation of complexity https://global.dbpedia.org/id/4pq8W
prov:wasDerivedFrom wikipedia-en:Law_of_conservation_of_complexity?oldid=1124196481&ns=0
foaf:isPrimaryTopicOf wikipedia-en:Law_of_conservation_of_complexity
is dbo:wikiPageWikiLink of dbr:List_of_eponymous_laws dbr:Programming_complexity dbr:Larry_Tesler dbr:List_of_software_development_philosophies
is foaf:primaryTopic of wikipedia-en:Law_of_conservation_of_complexity