AncientKnowledge - Latin and Greek Rennaisance ArchiveEverything - Don't lose any data - Compare ExploitableDataOnly AssumeGoodFaith - An etiquette pattern AutomaticDiffs AuxlangFallacy AvailabilityPropagation - An archival pattern - Data you use most often will be copied to new machines - It'll be put in easy to reach places - Therefore, it backs itself up - Compare WuWei AvoidExposingMechanics - If you're a builder, you care how it works - Users don't - Compare InYourFaceURIs BeautifulCode - The Whits list BecomingClint - A Javier pattern for MartyMcFlyBecomingClint - How we learn things BetterThanBeforeFallacy - An advertising fallacy BreakBrokenTraditions - NoSacredCows BugFreeProgramming - WriteMetacode ChangesetRevisionControl - Like Equid, Darcs, hg, etc. CodeAndConfigTransparency ContentRichDesign - The Topic on this CoolURIs - Compare HuffmaniseEverything - APIs can be cool too - And other non-URI identifiers - Example: telephone number reallocations - Example: WL's warehouse shop post - Names vs. locations CurrentPublicationSpaces - Is there a maximum number? DataRot - Data that isn't consumed rots - Ergo ExploitableDataOnly - Compare the term bitrot DesignPatterns - CamelCase is good beacause single words give WikiDictionaryFallacy - There are MetaDesignPatterns DevelopToUseCases - A workflow style - Don't program before you have a reason to - Example: EARL - Example: RDF DirectionalFallacy - Is the root up, or is it down? - Directions aren't universal DocumentByExamples - People LearnByExample - People learn best using examples, especially when task oriented - So document using examples DocumentDuring - You'll lose interest after the fact - Therefore, document as you go along DocumentMode - Opposite of ThreadMode DoTheRightThing - Cynically the same as DoWhatIMean DoWhatIMean - Cynically the same as DoTheRightThing EditingHypertext - Compare Amaya, Wiki Syntaxes, etc. EverExpandingScope - A fallacy - Clever people expand their scopes to think big - But this prevents specialisation - Which is bad, sometimes ExploitableDataOnly - Helps to prevent DataRot ExposeData - Though see ExploitableDataOnly - A conflicting aphorism? FilesystemOrganisation - How do I do it? - How do you do it? - What practices are universal? - Can anything be learned from this? - What patterns does this subsume? FirstClassData - First class data is data with a URI - Or an object with an interface - Some means of easily addressible availability FlexibleValidation - Schematron vs. RELAX NG - Not, exactly, DTDs/WXS vs. RELAX NG - Modular namespace stuff, etc. - Compare validation.n3 and loading new constraints - Getting schema data from instance data ForwardsCompatability - The opposite of Backwards Compatability - Compare HotComments - Compare ManAndOpt FutureEcho - A TV Tropes and Idioms pattern - Also used in books GiveMeMyData - If I store data somewhere, I should be able to access it - Or GimmeMyData? - Or GimmeMyDataBack? GlobalIdentifierSpaces - What kinds are there? - How easy is it to develop a new one? GoodCitizenship HomedirAsRoot - The homedir is important to me - The root is important to the computer - Therefore, show me my homedir primarily HomedirRevisionControl - Joey Hess and Mark Pilgrim do this HotComments - Compare ManAndOpt - ForwardsExtensibility is hard - Example: Trackback/Creative Commons - Example: PIs in XML - Example: Shebangs HuffmaniseEverything - Huffmanise URIs - Huffmanise your filesystem - Huffmanise regexp syntax - Huffmanise programming languages - Huffmanise natural languages ImportantInformationFirst - A documentation pattern InherentComplexity - The clutter is inherent to the organism - Complexity is sometimes irreducible - Compare MapsAndTerritories - Compare OversimplicationFallacy - Or ClutterIsInherent? InterpretationProperties - An RDF design pattern InventedWorlds InYourFaceURIs - Do they always suck? - Compare AvoidExposingMechanics - A Connolly Pattern JottableDates - A kind of Poor Man's Datatype - An (undocumented?) Connolly Pattern JustPublishIt - Don't worry, be crappy - A Connolly Pattern, renamed - A WuWei way of doing this is to work in a public directory - Compare ReleaseEarlyAndOften KeepAllData - Or ArchiveEverything? LanguageDesign LearnByExample - This is what people do - Therefore, DocumentByExamples LearningByFolklore - A Javier pattern LiterateProgramming LocationalTodoPlanning - The Principle of Most Annotation - (Or Least) MakeItWork - Then make it work better - A PPR pattern ManAndOpt - Compare ForwardsCompatibility - A TimBL pattern MapsAndTerritories - A WL pattern - The map is not the territory - But a map is also a territory! MedialWordNumbers - Like m12n, i18n, etc. - A Poor Man's Datatype, kinda? ModernistFallacy - What is called modern soon won't be - There is no fixed concept of modern - Things called modern are done so egotistically - This can be cultural egotism NeoHomesteading - What WL does OneBigDirectory - Against hierarchies - Hierarchies Are Evil! OneBigFile - Keeping it all in one file - Example: Whits - Example: Amaya for editing the XAG spec - Example: this very file is getting hard to edit OversimplificationFallacy - Compare MapsAndTerritories - Compare InherentComplexity PalimpsestSystem - Doesn't lose any information - PaperlessWorkspace PaperPrototyping PatternLanguage PatternNaming PatternReuse PoorMansDatatype PoorMansHypertext - A Connolly Pattern PrivacyVsAvailability - A Connolly Pattern PublishedSubjectIndicators - From John Cowan PurgeTheUserInterface - Kinda related to ExploitableDataOnly QualityOfEnvironment - A bigger factor than people think RDFPathEditing ReleaseEarlyAndOften - RERO - Hard to do - What ways are there of achieving it? - Compare JustPublishIt ResearchNotebook - A workflow pattern - A Connolly Pattern ReuseGreyAreas - A Semantic Web pattern - The #swig conversation RuiningNewPastures - Make an error on purpose - Then you can't be afraid of spoiling perfection - People yearn against this RuleOf128 - An espian pattern SayWhatYouMean - From TimBL via WL SchemaAnnotation SchemataVsInstances - Compare XML-infoset-in-RDF - Divide, but keep searching SelfDescription - Write self descripting code to WriteMetacode - Compare TestDrivenDevelopment SeriouslyKeepItSimple SpecificationFirst - Perl5 vs. Perl6 StructuredProcrastination StyleIsContent SyntaxAndSemantics - My old paper TaggingFallacies - Compare ExploitableDataOnly TemporalIngredient TestDrivenDevelopment - A workflow pattern ThemeAndDisambiguate - As in, the verbs - Example: inamidst.com borders and colours - Page texture is often very important TheRamshackleWay - Cody calls this the ghetto way - Others call it the bubble gum way - In other words, kludging - But kludging as a valid first class method TheUnixPhilosophy - Make things small - Make them work well - Chain them together ThreadMode - Opposite of DocumentMode TropesAndIdioms TweakExisting - From Javier UniversalCalendarFallacy - There are many calendar systems - People think of their own as universal, often - Calendars are often highly arbitrary UniversalFormalisms - RDF for Object Oriented Programmers - UML for RDF people - And so on - Larch seems another good example, and Topic Maps UnreusableWheels - Sometimes, the wheel isn't quite what you need - Compare ReuseGreyAreas - A Semantic Web topic, but probably succeptible to EverExapandingContext UnrevisabilityFallacy - If I miss Last Call, that's the specification's problem - Only, in practice, it's mine too UselessRedundancy - Example: language - Example: the entity hack in Pwyky - Sometimes the use is unforeseen! - Compare ForwardsCompatibility UseOpenFormats - Otherwise, DataRot - Compare GiveMeMyData VectorsNotResultants - An history pattern - Example: Elizojacobean playwrights - Example: escape characters WatchTinyRoads - A road safety pattern WebUniversality WikiDictionaryFallacy - Wikis don't make good dictionaries - Let dictionaries be dictionaries - Don't repeat boring data - Compare ExploitableDataOnly WriteMetacode - To help achieve BugFreeProgramming - Compare SelfDescription WuWei - Example: EARL post - Compare AvailabilityPropagation