repetition/repeating: as much as practical, really minimize it and make it obvious (what copied/converted from & to where & how) and automate it

^NLZCVU

1. ^NLZCUW  title history in reverse start-order:
   1. ^NLZCYR   now “
      

      repetition/repeating: as much as practical, really minimize it and make it obvious (what copied/converted from & to where & how) and automate it

      ”

      1. ^NLZDGF  –as this is much more accurate & clearer plus now includes the links to subtopics.
   2. ^NLZCXF   at 1st publish, “repetition: absolutely-minimize it else make it automated else blatant http://1.JotHere.com/LXZ8S7”
2. ^NLZD02   URL(s)
   1. ^LXZ8S7   http://1.JotHere.com/LXZ8S7
   2. ^NLZDLP   http://1.JotHere.com/755#NLZCVU

3. ^NLZDPV   Why? Overall a notable win!

   1. ^LXZ92F  This rule is fundamental to
      1.  ^LXZ948  good communication, including good posting, indeed why I created this post.
      2.  ^LXZ93K  good IT design, indeed one of its most fundamental rules
   2. ^NLZDQ8   Pros thru cons:
      1. ^LXZ7N2  NOT doing it (so repeating & un-obviously & un-automatically) overall costs big; cons thru pros:
         1. ^LXZ9KE  HUGE CON: vastly increases errors & inconsistencies (with multiple unsynced sources, there will be multiple un-synced answers)
         2. ^NLZE5E HUGE-BIG CON: vastly increases cost to maintain the content (multiple repeats must be updated, and if they’ve since been moved/distributed elsewhere, this can be very hard or impossible)
         3. ^LXZ7PZ   BIG CON: makes it difficult or impossible not to give credit where credit is due (including plagiarism).
         4. ^LXZ7PI  LARGE CON: slows things down in all but the short run with more for every reader (not just 1 author) to now have to read & dedup & merge.
         5. ^LXZ7SU  NOTABLE CON: ups computing costs (more to needlessly transmit & store).
            1. ^LXZ9T9  indeed, in the usual case where the repetition & content generation is done automatically and with no facilities to also recognize & undo, there is no limit to the wasted computing costs.
         6. ^NLZE7V Net CON: (long term con but short-term pro): History maintenance
            1. ^NLZEIZ  as its simpler to keep the history by just making a copy and indeed if repeating so copies are minimized, history is readily lost, but with good versioning including differencing (as say done by Git), history is better maintained including telling exactly what was changed & why.
         7. ^NLZETO MED-BIG & REAL PRO: repeating/repetition aids to good human aesthetics
            1. ^NLZEVV   as in music (including a repeated verse), wall & floor patterns (including tile & wallpaper), and poetry
            2. ^NLZEXL   fortunately specifying what is repeated can & should be done where possible (as in written music, specifying the “refrain”).
         8. ^NLZE1N   MED-BIG PRO but NOT good excuse: often much easier to quickly compose something that looks good (if one doesn’t bother tracking & include-telling what was copied from where)
         9. ^NLZE49   BIG & PRACTICALLY ESENTIAL PRO:  Reader doesn’t have to do anything special nor be interrupted to see what is being referred to, especially the frequent small items, because their details are repeated
            1. ^NLZEM9   this is indeed practically essential  but it is handled with automation (as hyperlinks and & iframes & more, which also typically require permalinks) but unfortunately this automation isn’t always available but it increasingly is.

4. ^NLZFGY   How?  For content which is repeated, in rough order done:

   1. ^NLZFVE   Spend the time up front to do this & do it right, as “short term-pain gives long term gain” as “Why” details.
   2. ^NM01U8   really minimize repeat/repetition
      1. ^LXYJJF KEY: avoid repeat posting any topic, and including without a reference to the prior works, by having just before searched for it and only posted a new thread/content if not already there
         1. ^NM0J5B  Note even if the idea/situation/sentiment is already there, but the fact you have it, too, is not, you can & should post effectively “I concur” or “me, too”.
         2. ^NLZG4S   perhaps most notably, do “OTPT&OTPT: ONE THREAD PER TOPIC and ONE TOPIC PER THREAD” (as on Meetup)
      2. ^LXZ1DW Place text & other content where it can be readily & ideally universally referred to without ideally ever having to be copied.
         1. ^LXZ1LY  For example: as a JotHere article or comment or in a Google Drive item (file or folder), and where possible avoiding  private message (as email or SMS) or voice communication.
         2. ^NM0JG1 Note posting especially electronic especially where each post & ideally item within it as an anchor, well achieves this, in contrast to other communication methods.
      3. ^LXZ8AT  Establish a single source home for every piece of info.
         1. ^LXZ8DK  Common example: if an event has a RSVP page for it, such as http://meetup.com/OCAndroid/events/46109162 , then your present status on if or not you’re going and why goes there, never in (a message, as “I will only be there on Saturday”) or even a post somewhere else.
      4. ^NLZH8X   NLZH8X:  Move & prefer content in structures which most minimize repetition
         1.  ^NMEF81   prefer a better structure to the degree the content can be fit into & well-organized by it and the storage location supports it
         2. ^NLZHAQ  NLZHAQ: for text structuring format, prefer from most to least:
            1. ^NLZHC0   table
               1. ^NMEFC5   generally the most universal structure for capturing info but also readily painful in many cases where display automation is lacking.
                  1. ^NMEFE0   notable example: leading prose platform WordPress is actually tables on the back end but with
               2. ^NLZHHS   also rendering tables as diagrams and charts where useful & worth the work
               3. ^NLZHMA   especially useful here is spreadsheets, HTML tables, and SQL.
            2. ^NMECQK   screenplay aka script (so via screenwriting aka scriptwriting)
               1. ^NMECR9   adds good proven structure specifically for this job
            3. ^NLZGWY   outline
               1. ^NLZYYO  outline directive (right-column) has a few more details: it’s recommended for most all writings.
               2. ^NLZGY5   as every point in an outline implicitly refers to is parent points especially its immediate parents without having to repeat them, so this
                  1. ^NLZH34  cuts huge amounts of repetition (the repetition of the parent contexts)
                  2. ^NLZH4U  strongly encourages the grouping of related items, indeed putting the items of a common parent under it (and then also only having to say the parent once), so gets the content a lot more orderly
               3. ^NLZHXT   especially discussion/conversation thread, especially nested
               4. ^NMEE38   best formatting of it…
                  1. ^NMEE4L   in HTML
                     1. ^NMEE4Q   best ones I’m steadily developing
                     2. ^NMEE56   the format used in this document is one of the best and the one I most commonly use
                  2. ^NMEET0   in BBCode
                     1. ^NMEETC   best one so far is my NC87S6 which is built from template “[*][color=beige]N9H001=[/color][list=1][/list=1]”
                  3. ^NMEE3X   in plaintext’
                     1. ^NMEELA   Destiny style (simple clean plaintext outlines)
                        1. ^NMEEM3   the best plaintext format I currently know
                        2. ^MXNN5A  each point is on its own line and is prefixed with 1 “*” bullet for each nesting level (as “***” before a level-3 point)…
                           1. ^NMEEN2   except points which are helpfully numbered, where instead of that level’s additional “*” a “([n])” is used as “(3)” for the 3rd point.
            4. ^NLZHC0   prose
               1. ^NMEDVN   is the most common form, probably because it is the easiest to understand each immediate point being said.
               2. ^NMEDVX   is typically worst as far as repetition & disorder & seeing the big picture & writing involving multi-people & regular maintenance.
               3. ^NMECNH   is seemingly the best form for
                  1. ^NMECOW   a speech
                  2. ^NMECP3   writing intended to read smoothly notably with little jumping around
                     1. ^NMECT4   for example , a novel & story
                     2. ^NMED3J   such as most fiction writing
                     3. ^NMED5D   to achieve this, it notably smooths out, including adds transitions, between changes (in topic/talk/time/place) so the structuring becomes background & implicit, unlike the other forms (which are more structured and generally don’t bother with transitional polish & clutter but rather feature their structure)
                        1. ^NMEDCU   so is typically worst form as far as finding one’s context for any given point and finding a point.
                           1. ^NMED8L   due to this (its typical requirement that the content is always smoothed out including so context/structure is generally invisible easily a fault), is typically worst form for writing which is authored incrementally & needs to be updated significantly, readily proportionately worse to the number of authors involved
      5. ^NLZXW3  use links in place of content repeat: instead of repeating/copying text or other content, place there a hyperlink-else-closes-link to where it is
         1. ^NLZZCC   this underlying, viewed mathematically, is essentially factoring out common expressions
         2. ^NLZZI0  this is seemingly the most fundamental way of minimizing/removing repetition
            1. ^NLZZI3  indeed this is emphasized on every page of this site in the right-column here
         3. ^LXYIWO a hyperlink-else-closest-link
            1. ^NLZY58  is a hyperlink else other type of link
            2. ^NLZY70   includes a pointer
               1. ^NLZYA0   directing exact as possible to the source location,
                  1. ^NLZYBW   as by (in general order of preface)
                     1. ^NLZYCK   giving the location an exact permanent ID,
                        1. ^NLZYDU  for instance every point I make includes a unique 6-digit code, a KCGUID currently, which, wherever possible, also is an HTML anchor to the section else start of the section point.
                     2.  ^NLZYE1   quoting a few unique & ideally-permanent words from the location ideally its start;
               2. ^NLZYB5   so the reader can find its location easily
                  1. ^NLZYFX  which ideally can be located automatically by the content browser as web browser (as by clicking on the link else Ctrl-F search or web search)
            3. ^NLZYIF   ideally also includes, and then is often & perhaps ideally displayed as, a few descriptive words, in the language of the text, telling the reader what this location is in relation to the current context
               1. ^NLZYM6   aims to and ideally achieves so it will not need to be changed even if the source is changed else this update will be automatic
                  1. ^NLZYOC   typically achieved by a using references which will not go out of date and using software to update the reference (for instance to update the reference “3” if its a link to how it was computed, say “1+2” where then inputs changed)
               2. ^NM046R   an example: a reference to an article/section is display text “section “[its title]””
      6. ^NM005T   keep what is repeated generally small, as no bigger than tweet size
         1. ^NM033F   which  now is typically possible by doing the above
   3. ^NM01L9   make what is repeated/sourced obvious especially as to “what copied/converted from & to where & how”
      1. ^NM0064   make it obvious who all it is being sent to
         1. ^NM0086   Examples from best to worst:
            1. ^NM008O excellent: the CC & To field address list in an email showing all recipients
            2. ^NM009B   good: the name and/or description of the distribution list where at least the user and ideally the reader-software can tell how many people-else-addresses it is being sent to
            3. ^NM00CN   bad: appearing the message/info is being written & sent to one person when it’s actually going to multiple.
      2. ^LXYIT2  proper quoting: pretty much always, “quote your sources”:
         1. ^LXZ23A  Meaning specifically:
            1. ^LXZ1YA  Make clear what’s being repeated (what was copied) and how it was changed (as by putting it in quotes “” and using editing marks as “..” and “[custom]”)
            2. ^LXZ21G  always include a link to your source –otherwise, the unobvious repeat of info will just take longer for the reader to identify & merge and make mistakes doing so and just waste time.
            3. ^LXZ26G   even if you are quoting yourself,
               1. ^LXZ28I  as how can one collapse the complexity of other people’s complexity if you don’t do it for one’s own work
               2. ^LXZ2A3  The fact that (VCS, especially DVCS as Git, are thought to be good to use even if there is only one programmer) is a good popular example of the importance of this.
            4. ^NM03OY   in other words, follow ideally everywhere the requirements for quoting and paraphrasing content of JotHere. standards of JotHere terms-of-service
         2. ^LXZ25R  An example where this was NOT done is (TBA)
      1. ^NM00F7   make it repetition automated –but without failing to follow the other repetition rules of this article
         1. ^NM017R   Pros thru cons:
            1. ^NM01AK   dramatically helps & enables compute updates (so not copies which go out of date)
            2. ^NM01EO  insures copies & conversions are complete
            3. ^NM01HI   causes the at the least designers and ideally & easily everyone to get very clear as to the repeating vs. uniqueness for each case
               1. ^NM03DP   for instance, the typical (so common heavily reused) form, making clear what is constant & what is variable for each case.
            4. ^NM01FE   con: automation is readily does repetition not following these other goals, including deliberately, making problems dramatically worse
         2. ^NM00HV   examples from best first:
            1. ^NM01BB  excellent: repetition of a spreadsheet produced by it recomputing its formulas
            2. ^NM00I9   very good: repetition produced by makefiles as (some of the latest technology) Grunt & alternatives at least if this & relevant source code is provided in the result so it is “copied/converted from & to what & how” is clear
            3. ^NM0145    likely very good: tweet & Facebook status updates at least if who all the message goes to is visible to readers
            4. ^NM014P   good: email distribution lists

5. ^NM03YT  applying this

   1. ^NLZZMS   applying this to messages, especially emails & paper letters
      1. ^NLZZND   if done, could cut ~95% of the spam content we see in everyday life
      2. ^NLYF3T   use links in place of content repeat includes means repeat minimal content between messages
         1. ^NLYF62   so avoid sending the same content multiple people, especially via copy-and-paste, except for the same links
            1. ^NM0033   this results in messages which are generally very small, even tweet size, as a message is 100%
         2. ^NLYFAP   instead put into post(s) all possible text which would repeat (including unchange between sends of the message) and have the message point to that
      3. ^NM04AI   doing proper quoting causes the same text sent to everyone be in quotes, and optionally including an ID, especially at the start, to ID the repeated text
      4. ^NM04FG   Real example: template (to be completed without removing its quotes) used a Meetup Greet to member applicants: “
         Sebastian, “MIX4YX: RE ur ”<date format=”YYYY.MM.DD”/>“ application:
         WELCOME2 http://MEETUP.COM/OCANDROID ,OC’s Largest & Oldest Android Community Group!
         *I now approve u BUT,on ur profile,pls ans BOTH of MFTRef’s 2Qs EXACT-as-possible”(as “(1)Destiny@SCaLE11x http://meetu.ps/rBfh4 booth 81 ..”)“.
         *Then read http://1.JotHere.com/MHMore then RSVP-with-Why to 3 of our events,with 2 YES-RSVPs (or equivalent: 2 MAYBEs=1 YES :-).
         *Next mtg ”TOMORROW!“ LkgFwd2 1st mtg u@our events!”
         ” –quoted from here
6. ^NMFYZH   (section content) categories, in their container structure:
   1. ^NMFZ5L   “structure NMEBJG” –not explicitly added because subs cover it fully
      1. ^NMFZ8H    “info|information M1EQW0” –now add
         1. ^NMFZ8T    “communication LRCGCO” –now add
            1. ^NMFZC9   “posting/messaging NMESUI”
               1.  ^NMFZHJ  “posting LXYYH2” –added
         2. ^NMFZX1  “media M4P7K7” -now add
            1. ^NMFZXH   “writing LGYLMM” -now add
      2.  ^NMGMTE  “pattern NMG2ND” –not here as to general
         1. ^NMGMTR    “redundancy NMEC54” -not here as too general
            1. ^NMG002   “repetition|repeating|duplication NMEBTS” –now add
               1. ^NMECFY   “deduplication NMEC91” –now add
         2. ^NMGMYN    “format M31XFI”  –now add, as due to NLZHAQ
      3.  intermediates
         1.  “affect N0BXNJ”
            1.  “control|regulate|govern N0BXPG”
               1. “ guide N0BXS4”
                  1. ^NMG0DJ  “rule N0BY8E” –now add especially due to

8. ---

   ^NLZC6F  section additional history, in start-time order:

   1. ^NLZCCD seemingly originally section /754#LXZ9DA, including per LXZ948
   2. ^NLZC6W   earlier history to be found
   3. ^NLZC99    “Version 0.9 (usable but with areas to improve)” published seemingly-1st “Feb 11, 2012 @ 23:57”
   4. ^NLZCDI   updating it foremost for reference at NLZBHY, including
      1. ^NLZCHW   update this structure to that style
      2. ^NLZFV1  “Don’t” repeat anything: Spend the time up-front to) Minimize repetition and, where impossible, make it automated else blatant (showing what exactly has been copied from where) ) with NLZFVF including since much of this is repeated title matter (which is also somewhat incorrect, so repeated errs!).
      3. ^NM07A3   100% rewrite of everything here including many significant improvements.
      4. ^NM0GXK   spellcheck; apply N14GIY plus ~3 manual fixes; publish again 2015.03.30Mon0017.
   5. ^NMGN70   NLZH8X lines: 12 to +24; spellcheck; apply N14GIY latest mod; publish again 2015.04.07Tue1655pst.