Feb 112012
communication LRCGCO, deduplication NMEC91, format M31XFI, info(information), post (publishing) LXYYH2, repetition|repeating|duplication NMEBTS, rule N0BY8E, writing LGYLMM Add comments
- NLZCUW title history in reverse start-order:
- 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
”
- NLZDGF –as this is much more accurate & clearer plus now includes the links to subtopics.
- NLZCXF at 1st publish, “repetition: absolutely-minimize it else make it automated else blatant http://1.JotHere.com/LXZ8S7”
- NLZCYR now “
- NLZD02 URL(s)
-
NLZDPV Why? Overall a notable win!
- LXZ92F This rule is fundamental to
- LXZ948 good communication, including good posting, indeed why I created this post.
- LXZ93K good IT design, indeed one of its most fundamental rules
- NLZDQ8 Pros thru cons:
- LXZ7N2 NOT doing it (so repeating & un-obviously & un-automatically) overall costs big; cons thru pros:
- LXZ9KE HUGE CON: vastly increases errors & inconsistencies (with multiple unsynced sources, there will be multiple un-synced answers)
- 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)
- LXZ7PZ BIG CON: makes it difficult or impossible not to give credit where credit is due (including plagiarism).
- 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.
- LXZ7SU NOTABLE CON: ups computing costs (more to needlessly transmit & store).
- 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.
- NLZE7V Net CON: (long term con but short-term pro): History maintenance
- NLZETO MED-BIG & REAL PRO: repeating/repetition aids to good human aesthetics
- 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)
- 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
- 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.
- LXZ7N2 NOT doing it (so repeating & un-obviously & un-automatically) overall costs big; cons thru pros:
- LXZ92F This rule is fundamental to
-
NLZFGY How? For content which is repeated, in rough order done:
- NLZFVE Spend the time up front to do this & do it right, as “short term-pain gives long term gain” as “Why” details.
- NM01U8 really minimize repeat/repetition
- 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
- 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”.
- NLZG4S perhaps most notably, do “OTPT&OTPT: ONE THREAD PER TOPIC and ONE TOPIC PER THREAD” (as on Meetup)
- LXZ1DW Place text & other content where it can be readily & ideally universally referred to without ideally ever having to be copied.
- 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.
- 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.
- LXZ8AT Establish a single source home for every piece of info.
- 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.
- NLZH8X NLZH8X: Move & prefer content in structures which most minimize repetition
- NMEF81 prefer a better structure to the degree the content can be fit into & well-organized by it and the storage location supports it
- NLZHAQ NLZHAQ: for text structuring format, prefer from most to least:
- NLZHC0 table
- NMEFC5 generally the most universal structure for capturing info but also readily painful in many cases where display automation is lacking.
- NMEFE0 notable example: leading prose platform WordPress is actually tables on the back end but with
- NLZHHS also rendering tables as diagrams and charts where useful & worth the work
- NLZHMA especially useful here is spreadsheets, HTML tables, and SQL.
- NMEFC5 generally the most universal structure for capturing info but also readily painful in many cases where display automation is lacking.
- NMECQK screenplay aka script (so via screenwriting aka scriptwriting)
- NMECR9 adds good proven structure specifically for this job
- NLZGWY outline
- NLZYYO outline directive (right-column) has a few more details: it’s recommended for most all writings.
- NLZGY5 as every point in an outline implicitly refers to is parent points especially its immediate parents without having to repeat them, so this
- NLZHXT especially discussion/conversation thread, especially nested
- NMEE38 best formatting of it…
- NMEE4L in HTML
- NMEET0 in BBCode
- NMEETC best one so far is my NC87S6 which is built from template “[*][color=beige]N9H001=[/color][list=1][/list=1]”
- NMEE3X in plaintext’
- NMEELA Destiny style (simple clean plaintext outlines)
- NMEEM3 the best plaintext format I currently know
- MXNN5A each point is on its own line and is prefixed with 1 “*” bullet for each nesting level (as “***” before a level-3 point)…
- NMEEN2 except points which are helpfully numbered, where instead of that level’s additional “*” a “([n])” is used as “(3)” for the 3rd point.
- NMEELA Destiny style (simple clean plaintext outlines)
- NLZHC0 prose
- NMEDVN is the most common form, probably because it is the easiest to understand each immediate point being said.
- NMEDVX is typically worst as far as repetition & disorder & seeing the big picture & writing involving multi-people & regular maintenance.
- NMECNH is seemingly the best form for
- NMECOW a speech
- NMECP3 writing intended to read smoothly notably with little jumping around
- NMECT4 for example , a novel & story
- NMED3J such as most fiction writing
- 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)
- NMEDCU so is typically worst form as far as finding one’s context for any given point and finding a point.
- 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
- NMEDCU so is typically worst form as far as finding one’s context for any given point and finding a point.
- NLZHC0 table
- 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
- NLZZCC this underlying, viewed mathematically, is essentially factoring out common expressions
- NLZZI0 this is seemingly the most fundamental way of minimizing/removing repetition
- NLZZI3 indeed this is emphasized on every page of this site in the right-column here
- LXYIWO a hyperlink-else-closest-link
- NLZY58 is a hyperlink else other type of link
- NLZY70 includes a pointer
- NLZYA0 directing exact as possible to the source location,
- NLZYBW as by (in general order of preface)
- NLZYCK giving the location an exact permanent ID,
- 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.
- NLZYE1 quoting a few unique & ideally-permanent words from the location ideally its start;
- NLZYCK giving the location an exact permanent ID,
- NLZYBW as by (in general order of preface)
- NLZYB5 so the reader can find its location easily
- 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)
- NLZYA0 directing exact as possible to the source location,
- 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
- 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
- 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)
- NM046R an example: a reference to an article/section is display text “section “[its title]””
- 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
- NM005T keep what is repeated generally small, as no bigger than tweet size
- NM033F which now is typically possible by doing the above
- 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
- NM01L9 make what is repeated/sourced obvious especially as to “what copied/converted from & to where & how”
- NM0064 make it obvious who all it is being sent to
- NM0086 Examples from best to worst:
- NM008O excellent: the CC & To field address list in an email showing all recipients
- 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
- NM00CN bad: appearing the message/info is being written & sent to one person when it’s actually going to multiple.
- NM0086 Examples from best to worst:
- LXYIT2 proper quoting: pretty much always, “quote your sources”:
- LXZ23A Meaning specifically:
- 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]”)
- 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.
- LXZ26G even if you are quoting yourself,
- NM03OY in other words, follow ideally everywhere the requirements for quoting and paraphrasing content of JotHere. standards of JotHere terms-of-service
- LXZ25R An example where this was NOT done is (TBA)
- LXZ23A Meaning specifically:
- NM00F7 make it repetition automated –but without failing to follow the other repetition rules of this article
- NM017R Pros thru cons:
- NM01AK dramatically helps & enables compute updates (so not copies which go out of date)
- NM01EO insures copies & conversions are complete
- NM01HI causes the at the least designers and ideally & easily everyone to get very clear as to the repeating vs. uniqueness for each case
- NM01FE con: automation is readily does repetition not following these other goals, including deliberately, making problems dramatically worse
- NM00HV examples from best first:
- NM01BB excellent: repetition of a spreadsheet produced by it recomputing its formulas
- 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
- NM0145 likely very good: tweet & Facebook status updates at least if who all the message goes to is visible to readers
- NM014P good: email distribution lists
- NM017R Pros thru cons:
- NM0064 make it obvious who all it is being sent to
-
NM03YT applying this
- NLZZMS applying this to messages, especially emails & paper letters
- NLZZND if done, could cut ~95% of the spam content we see in everyday life
- NLYF3T use links in place of content repeat includes means repeat minimal content between messages
- 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
- 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
- NLZZMS applying this to messages, especially emails & paper letters
- NMFYZH (section content) categories, in their container structure:
-
NLZC6F section additional history, in start-time order:
- NLZCCD seemingly originally section /754#LXZ9DA, including per LXZ948
- NLZC6W earlier history to be found
- NLZC99 “Version 0.9 (usable but with areas to improve)” published seemingly-1st “Feb 11, 2012 @ 23:57”
- NLZCDI updating it foremost for reference at NLZBHY, including
- NLZCHW update this structure to that style
- 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!).
- NM07A3 100% rewrite of everything here including many significant improvements.
- NM0GXK spellcheck; apply N14GIY plus ~3 manual fixes; publish again 2015.03.30Mon0017.
- NMGN70 NLZH8X lines: 12 to +24; spellcheck; apply N14GIY latest mod; publish again 2015.04.07Tue1655pst.
[…] VERY IMPORTANT: repetition: absolutely-minimize it else make it automated else blatant -click for full […]