|
|
| Line 1: |
Line 1: |
| {{Draft}} | | {{Venue |
| | |Address=721 Broadway, New York, NY 10003 |
| | |URL=http://tisch.nyu.edu/about/contact-us |
| | }} |
| | They expect meetings to be nonprofit/tech focused, and like tech + art projects. |
|
| |
|
| Co-founder of Blue Oxen Associates. Hacker-philosopher. Socialtext, TiddlyWeb.
| | Referred by Lane Rasberry. |
| | |
| Put practice to ideas. That, in turn, helped refine the ideas.
| |
| | |
| = How I Met Chris =
| |
| | |
| unrev-ii mailing list. Created a tool called [https://www.burningchrome.com/~cdent/index.cgi?word=1 Warp].
| |
| | |
| 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.
| |
| | |
| 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.
| |
| | |
| 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]]
| |
