Data Salon 3 - Ghent
Download as PPTX, PDF1 like522 views
The document discusses complexity in computing and the brain. It notes that complexity is not solely defined by computational or mathematical concepts like P, NP, EXPTIME, and other time and space complexity classes. The brain can see simpler problems than formal definitions and may prioritize speed, understandability, and community over other factors. Standards, tools, and technologies related to digital preservation are also listed.
More Related Content
Similar to Data Salon 3 - Ghent (20)
Data Salon 3 - Ghent
- 3. COMPLEXITY
- 4. NOT
- 6. OR
- 7. MATHEMATICAL
- 10. NO
- 11. SIMPLER PROBLEMS
- 12. WHERE THE BRAIN SAYS
- 13. FWT
- 16. A1,A2,A3,A4
- 17. A1Enkelpublicaties die in de Science Citation Index, de Social Science Citation Index en de Arts & Humanities Citation Index in Web of Science het documenttype article, letter, note, review of proceedings paper krijgen, kunnenerkendwordenals A1 (z.o. definitie van A1 publicatie in vorigevraag).Anderedocumenttypes, zoals book review, biographical item, editorial material, ..., krijgengeen A1 status en wordendaarom door de reviewer geklasseerdals V. Indienuwpublicatietochgelijkstaataaneenvolwaardigartikel (bijv. in velegevallen van editorial material), dankuntu in samenspraak met de uitgever van het tijdschriftwaarinuwbijdrageverscheen, eenvraagindienenbij Thomson Reuter om het documenttypeomtezettennaar article of review.
- 18. ONLY 6 CLICKS TO FULL TEXT
- 20. FWT
- 21. STANDARDSTOOLBOX
- 24. WARNING: REAL CODEif (!$loginAccount or (($userRoleeq 'reviewer') and !$loginAccount->{departmentRights}) or ($userRoleeq 'localAdmin' and !$loginAccount->{isLocalAdmin}) or (($userRoleeq 'superAdmin') and !$loginAccount->{isSuperAdminAccount})) {…}
- 27. FWT
- 28. Law of conservation of trouble?
- 29. Origin in Trade-Off’s?Interpretable (conceptual distance): humans -> machinesProcessing (time, production): slow -> fastExtensible: namespaces -> bigger modelCommunity: my group -> your groupCost of production: $$ -> $$$$SecurityApplication Domain: generic (e.g. HTML) -> data modelsTradition: If it ain’t broke..LawFuture promises: If I do this then I will …Compatibility: forwards -> backwards
- 30. OR
- 32. TIME/CONTEXT?At this moment in time we had only access to (…)
- 34. Feature CreepFallacies of ArgumentationCommunity Pressure?Wrong Business ModelNot Invented hereBricolageFunding
- 35. LESS = MORE
- 36. WORSE = BETTER
- 37. Richard Gabriel - 1989On SimplicityThe design must be simple, both in implementation and interface.Better: simpler implementation than: simpler interface
- 38. Richard Gabriel - 1989On CorrectnessThe design must be correct in all observable aspects. It is slightly better to be simple than correct.Better:simpler designthan:correct design
- 39. Richard Gabriel - 1989On ConsistencyConsistency can be sacrificed for simplicityBetter: consistency sacrificed in some cases for simplicity than: design must be consistent in all aspects
- 40. Richard Gabriel - 1989On CompletenessCompleteness can be sacrificed in favor of any other qualityBetter: simplicity may overrule completenessthan: simplicity is not allowed to reduce completeness
- 41. SIMPLICITY produces successful softwareSIMPLICITY takes much less time and effort to produce and adaptSIMPLICITY spreads much rapidly, long before any complete, correct, constitent programs sees the market
- 42. THANKS :-)PATRICK HOCHSTENBACH – GHENT UNIVERSITY LIBRARYhttp://lib.ugent.beDATASALON-3 OCT 2009GENT