|
|
| Line 1: |
Line 1: |
| {{Draft}}
| | Created by Barry Johnson of [http://www.polaritypartnerships.com/ Polarity Partnerships], Polarity Maps are ways to map out tensions. |
|
| |
|
| Co-founder of Blue Oxen Associates. Hacker-philosopher. Socialtext, TiddlyWeb.
| | {|width="50%" cellpadding="20" |
| | ! !! Left Pole !! Right Pole !! |
| | |- |
| | |align="right"|'''Upsides''' ||align="center" bgcolor="lightgreen"|Left Pole Upsides ||align="center" bgcolor="lightgreen"|Right Pole Upsides || |
| | |- |
| | |align="right"|'''Downsides''' ||align="center" bgcolor="red"|Left Pole Downsides ||align="center" bgcolor="red"|Right Pole Downsides |
| | |} |
|
| |
|
| Put practice to ideas. That, in turn, helped refine the ideas.
| |
|
| |
|
| = How I Met Chris =
| | Guidelines for creating a map: |
|
| |
|
| unrev-ii mailing list. Created a tool called [https://www.burningchrome.com/~cdent/index.cgi?word=1 Warp].
| | # Define the challenge |
| | | # Identify a key polarity |
| Shared architectural principles and aesthetic. System administrator and programmer at IU focused on a knowledge base project. [http://arts.sourceforge.net/ Arts]. Worked with a lot of hackers who became part of my tribe.
| | # Name the poles in a value-neutral way |
| | | # Brainstorm content for each quadrant |
| Was at the School of Library Information Sciences at Indiana University. Wanted to do an [https://www.burningchrome.com/~cdent/slis/#596 internship] for one of his classes and reached out to me. Was starting up Blue Oxen Associates at that point, so he joined as an intern.
| | # Agree on higher purpose or deeper fear |
| | |
| Chris's [https://www.burningchrome.com/~cdent/mt/archives/000121.html manifesto].
| |
| | |
| Purple numbers. PurpleWiki.
| |
| | |
| [http://eekim.com/2003/07/why-am-i-blogging/ Convinced me to start blogging.] Blogged a lot in those early days. Lots are in response to stuff that Chris said. It was a conversation out-loud. So generative.
| |
| | |
| = Lessons Learned
| |
| | |
| [http://eekim.com/2007/02/the-blue-oxen-way/ blog post on the Blue Oxen Way].
| |
| | |
| 1. Shared understanding / shared language. [[Squirm Test]]. Wikis all about shared language.
| |
| | |
| 2. Be less dumb.
| |
| | |
| 3. Bootstrapping. (Name, Blue Oxen Associates, an homage to [[Doug Engelbart]]). Architectures that supported this.
| |
| | |
| "we clearly shared the idea that good tools combined with good use of those tools was an important aspect of being good collaborators." Supporting augmentation — reuse, sourcing.
| |
| | |
| If it's not captured, it didn't happen. Tremendous discipline plus similar orientation around digital infrastructure needed to do this well. E.g. fine-grained addressability.
| |
| | |
| Work rhythms. Asynchronous back-and-forth.
| |
| | |
| Think out loud.
| |
| | |
| [http://eekim.com/2006/08/good-personal-information-hygiene/ Information hygiene].
| |
| | |
| Synthesis is part of the work.
| |
| | |
| "stigmergy"
| |
| | |
| Just do it. [http://eekim.com/2004/02/transclusions-pathbased-addressing-and-version-control/ Transclusions].
| |
| | |
| | |
| [[Category:People]]
| |
