AboveAndBelowTheDoubleLine - Notes

Above and Below the Double Line - Dr. M.C. Morgan

-"writing on wiki proceeds from ThreadMode to DocumentMode by way of Refactoring."
-explain to students….wiki writing collaborative - changes not just what write, but how we write
-so, change way we talke about process.
-ThreadMode is discussion.
-like prewriting to generate topics and positions and arguements.
-DocumentMode is exposition
-like drafting essay by pulling together the threads of ThreadMode.
-Refactoring - kinda like revising - kinda like reorganizing - kinda like clearing away the (tea?!?!) table for another course.
-comes from computer programming.

-wordsmash - wikiWords - signal links to new topics open for elaboration - follow link

-return to topic to see what is developing.

-authors enter page to work w/ text in diff ways - refactor-(still not clear on what it means)
-go to another page to add to thread
-add WikiWord to another
-point out link to topic on another
-reader sees something needed, adds wikiWord and declares new topic - sets out ideas, a summary, direction for page
-wikiWord now topic - topic does appear in Recent Changes and Index.

-people visit topic, read, leave
-or begin develop it in Threadmode (signed) or DocumentMode(unsigned above doublelines…whatever that means)…..
-ThreadMode - diaglogue, discussion, dialectic
-open, collective, dynamic, informal
-develop as page or on a page.
-no predictive structure
-writing in thread is spontaneous, improvisational, but not sermonic - not preachy
-these shut down threadmode
-public thinking -
-designed, considered, polite
-presents position, way of understanding, clear/persuasive, not soapbox but sandbox.
-tentative rather than absolute.
-opinionated but not seeking closure
-exploring - create understanding instead winning ground from opponents.
-oh boy….grounded in specifics to make sense of abstractions
-end - allow others to understand and create - not to win
-is an attitude.
-don't follow chronology like blog - place contributions near passage are responding to - - additions tend to be concise and pointed.
-thread mode can start as reply to a document mode beginning.
-start page in document mode, others may choose reply to document
-starts threads
-they continue
-maybe someone willing or able to refactor page, deleting original comments
-page refactored into document mode - process begins again.

-DocumentMode -expository
-discursive(???WHICH DISCURSIVE????longwinded and rambling or logically proceeding??)
-monologue
-still open
-written in 3rd person.
-active voice
-synthesis of collective thinking.
-pages and sections of pages become collective understanding on the wiki.
-usually unsigned
-recent changes takes care of crediting.
-cuz are collective, are still active.
-document mode - ideas and not authors are focus and center.
-written in analyzing prose - transparent style.
-doesn't call attention to the writing.

-BY WAY OF REFACTORING -
-threadmode - wiki pages develop opportunistically as returned to - then read, edit, add, reoganize
-REFACTORING - less opportunistic -
-conscientious technique for developing a page - move toward document mode.
-lotsa posting - mess- initial point or purpose gets lost.
-authors don't read entire page, but skim and start adding comments wherever - create redundancies.
-ideas that would help coalesce lost.
-gettin' NOISY
-"Thread mess" - page developing by drama of discussion and not exploration.
-gotta synthesize threads to document mode.
-refactoring is a kind of revision - BUT compostion and rhetoric types tend to see revision changing and developing meaning
-REFACTORING DIFF cuz attempts to preserve meaning -
-find and make clear an organized patter in the ideas of ThreadMode. (WHO THE HELL BESIDES A WRITER WOULD DO THIS? THESE WIKIS ARE FOR WRITERS AND WRITER WANNA BE'S - FINE - THEN EVERYONE WITH ARMS AND LEGS AND THE ABILITY TO WALK, GET THE HELL OUT ON THE FOOTBALL FIELD AND GET READY TO PARTICIPATE.)
-refactoring is synthesis.
-programing - reworking program code for processing elegance w/out changing function of code.
-might take long-ass procedure and refactor into 1 - 2 lines of code.

-daily refactoring - mnemonics, redo grocery list to map onto physical store,

wikipedia - 'refactoring' - doesn't add new functionality - designed to improve understandability of code - make easier for human maintenance.

-attempt to distill valuable info from earlier, less focused discussions.
-four moves:
-add comment
-edit older comments
-split conversations to new pages
-capture converging comments in single paragraph.

-replace thread mode w/ monolog says same thing
-change 1st person singular to 1st or 3rd person plural
-remove inline attributions and put at end w/ contributors.

-attempt to find or create structure for threads of discussion that allows them to be synthesized into document.
-refact document encompasses what threads replaced argued.
-says exlicitly what was implicit in threads.
(AND IS ANY OF THIS ABOUT ANYTHING THAT IS OF ANY INTEREST AT ALL??? SEEMS LIKE A WHOLE LOT OF WORK JUST TO DO DUMBASS BUSY WORK).

refactor - stabilize meaning for a moment so build on

FINALLY -QUOTE THIS….
Re-working a passage to make it easier to understand (change the signal to noise, bring out structures in ideas, make it mean more than it meant before) means changing its meaning. We know that. And we know that refactoring favors some stylistic moves over others. We know that RefactoringIsProblematic. But we refactor anyway. Because we need to move on.

-keep close to ideas in thread
-concern about getting refactor wrong -
-"wiki self-healing.'

TECHNIQUES -
-accuracy
-difficult
-time and repeated sessions
-people still adding threads
-staying close to ideas
-as enjoyable as thick slice of hell.

1-USE DOUBLE LINES
2-USE PAGE PATTERNS

-DoubleLines - distinguish document from thread
-some use separate DocumentMode, OpeningStatement, Thesis, or pattern at top and threadMode below.
-top part is payload - short article on page's title subject
-bibliographic info
-bottom is meta-data about page, discussion, suggested changes, categorization, stories, indirectly related links.

-quote this…..
Pages on this wiki tend to have the DocumentMode section at the top of the page, followed by ThreadMode contributions. Use DoubleLines (two lines of four dashes) to separate DocumentMode from ThreadMode on the same page. This convention is not absolute, however, and we find that writers add comments and questions to DocumentMode sections. This is a Good Thing, and writers can refactor the page to address the embedded comment. But as a thread gets long, move it below the DoubleLines. [16]

-PAGE PATTERNS-
refactoring gives explicit structure.
-threads develop, direction, arguements and evidence suggest patter for organizing.
-make pattern explicit
-heuristic

-ThereforeBut
-ThesisAntithesisSynthesis
-TenativeSummary

-state the context and forces in a paragraph or several, then put a bold ‘Therefore,’ on a line

-workhouse sentence structure/patterns to get outta chaos….quote this;;
#########################################
structure for breaking an explanation down into several parts

To , he/she , which , , .

A structure for organized opposing, followed by a gloss

Rather than , , , a should , , : .
#######################################
PATTERNS -RESOURCE

* A pattern for listing alternatives
o HowDoWeDoX
o ByThisMeans
o OrByThisMeans
o OrByThisMeans
o  … 
* A pattern for stating and considering dependencies
o ItDependsOnThis
o AndOnThis
o AndOnThis
o WhichDependsOn
o  … 
* A pattern for stating if-then, with an option
o IfThenOtherwise or IfThenElse
* A pattern for breaking an explanation into several parts, with qualifications
o IfThisAndThisAndThis … ThenThis
o ButIfYouConsiderThis … ThenThis
* A pattern for articulating parallel points or reasons in a series
o ThisAndThisAndThis … LeadToThis
* A pattern for organized composing with a gloss
o OnOneHandThese … ButOnTheOtherHandThese … AndSoThis

-CHALKBOARD ANALOGY
Online Chalkboard

When we write threads we scribble ideas as if we were writing with chalk.

They need no order

If the chalk keeps moving the brain keeps working

Chalk comes in many colors

You can make pictures with chalk

A chalkboard can be taped over and posted to

It’s easier to read a chalkboard from a distance
-eventually board is filled and look at what's written -
-TheEditor in all can erase unimportant and summarize and refactor info.
-now more space - now scribble again.