<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (caseygollan)</title>
    <link>https://pinboard.in/u:caseygollan/public/</link>
    <description>recent bookmarks from caseygollan</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://joedocs.com/"/>
	<rdf:li rdf:resource="http://chaosmanagement.com/images/stories/pdfs/Group%20Relations%20Glosary%20of%20terms2-08.pdf"/>
	<rdf:li rdf:resource="http://stet.editorially.com/articles/making-remote-teams-work/"/>
	<rdf:li rdf:resource="http://www.full-stop.net/2014/01/21/features/the-editors/tldr-choire-sicha/"/>
	<rdf:li rdf:resource="http://jofreeman.com/joreen/tyranny.htm"/>
	<rdf:li rdf:resource="https://github.com/github/gollum#readme "/>
	<rdf:li rdf:resource="http://ofps.oreilly.com/ "/>
	<rdf:li rdf:resource="http://techcrunch.com/2011/03/17/whom-to-hire-at-a-startup-attitude-over-aptitude/ "/>
	<rdf:li rdf:resource="http://clementvalla.com/index.php?/printed/sol-lewitt--mechanical-turk/ "/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://joedocs.com/">
    <title>JoeDocs | Better Collaborative Documents</title>
    <dc:date>2020-07-21T20:45:25+00:00</dc:date>
    <link>https://joedocs.com/</link>
    <dc:creator>caseygollan</dc:creator><dc:subject>collaboration tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:caseygollan/b:edf38a8f2dd5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://chaosmanagement.com/images/stories/pdfs/Group%20Relations%20Glosary%20of%20terms2-08.pdf">
    <title>GROUP RELATIONS GLOSSARY OF TERMS</title>
    <dc:date>2020-05-29T21:52:40+00:00</dc:date>
    <link>http://chaosmanagement.com/images/stories/pdfs/Group%20Relations%20Glosary%20of%20terms2-08.pdf</link>
    <dc:creator>caseygollan</dc:creator><dc:subject>power collaboration</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:caseygollan/b:79b7951f76e9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:power"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:collaboration"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://stet.editorially.com/articles/making-remote-teams-work/">
    <title>STET | Making remote teams work</title>
    <dc:date>2014-01-30T19:08:42+00:00</dc:date>
    <link>http://stet.editorially.com/articles/making-remote-teams-work/</link>
    <dc:creator>caseygollan</dc:creator><description><![CDATA[> Perhaps the most persistent bit of advice I gathered — and in some ways the most counterintuitive — is the need for remote teams to overcommunicate. That runs against the prevailing theme of efficiency that marks many discussions about workplace best practices]]></description>
<dc:subject>Reading.am ranch remote collaboration</dc:subject>
<dc:identifier>https://pinboard.in/u:caseygollan/b:2732028191cc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:Reading.am"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:ranch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:remote"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:collaboration"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.full-stop.net/2014/01/21/features/the-editors/tldr-choire-sicha/">
    <title>TL;DR: Choire Sicha</title>
    <dc:date>2014-01-23T14:42:45+00:00</dc:date>
    <link>http://www.full-stop.net/2014/01/21/features/the-editors/tldr-choire-sicha/</link>
    <dc:creator>caseygollan</dc:creator><description><![CDATA["I would say the most fascinating and challenging writing is happening on GroupMe, Hipchat, IRC, Campfire, maybe Snapchat and Whisper, and then on the more conversational corners of Tumblr and maybe sometimes Twitter, but not that often, because Twitter is for the olds, and it calcifies really fast"]]></description>
<dc:subject>Reading.am remote collaboration ranch</dc:subject>
<dc:source>https://twitter.com/</dc:source>
<dc:identifier>https://pinboard.in/u:caseygollan/b:0c67f898b2f3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:Reading.am"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:remote"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:ranch"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://jofreeman.com/joreen/tyranny.htm">
    <title>The Tyranny of Stuctureless</title>
    <dc:date>2013-12-24T21:40:07+00:00</dc:date>
    <link>http://jofreeman.com/joreen/tyranny.htm</link>
    <dc:creator>caseygollan</dc:creator><description><![CDATA[<blockquote>While working in this kind of group is a very heady experience, it is also rare and very hard to replicate. There are almost inevitably four conditions found in such a group;

 1) It is task oriented. Its function is very narrow and very specific, like putting on a conference or putting out a newspaper. It is the task that basically structures the group. The task determines what needs to be done and when it needs to be done. It provides a guide by which people can judge their actions and make plans for future activity.
2) It is relatively small and homogeneous. Homogeneity is necessary to insure that participants have a "common language" for interaction. People from widely different backgrounds may provide richness to a consciousness-raising group where each can learn from the others' experience, but too great a diversity among members of a task-oriented group means only that they continually misunderstand each other. Such diverse people interpret words and actions differently. They have different expectations about each other's behavior and judge the results according to different criteria. If everyone knows everyone else well enough to understand the nuances, these can be accommodated. Usually, they only lead to confusion and endless hours spent straightening out conflicts no one ever thought would arise.
3) There is a high degree of communication. Information must be passed on to everyone, opinions checked, work divided up, and participation assured in the relevant decisions. This is only possible if the group is small and people practically live together for the most crucial phases of the task. Needless to say, the number of interactions necessary to involve everybody increases geometrically with the number of participants. This inevitably limits group participants to about five, or excludes some from some of the decisions. Successful groups can be as large as 10 or 15, but only when they are in fact composed of several smaller subgroups which perform specific parts of the task, and whose members overlap with each other so that knowledge of what the different subgroups are doing can be passed around easily.
4) There is a low degree of skill specialization. Not everyone has to be able to do everything, but everything must be able to be done by more than one person. Thus no one is indispensable. To a certain extent, people become interchangeable parts.
</blockquote>]]></description>
<dc:subject>Reading.am ranch collaboration structure organization</dc:subject>
<dc:identifier>https://pinboard.in/u:caseygollan/b:7420d4977c97/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:Reading.am"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:ranch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:structure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:organization"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/github/gollum#readme%20">
    <title>github/gollum - GitHub</title>
    <dc:date>2011-07-08T22:11:12+00:00</dc:date>
    <link>https://github.com/github/gollum#readme%20</link>
    <dc:creator>caseygollan</dc:creator><dc:subject>wikis collaboration constellations coding git</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:caseygollan/b:63f4bfdb0124/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:wikis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:constellations"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:coding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:git"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ofps.oreilly.com/%20">
    <title>OFPS</title>
    <dc:date>2011-03-26T18:20:52+00:00</dc:date>
    <link>http://ofps.oreilly.com/%20</link>
    <dc:creator>caseygollan</dc:creator><description><![CDATA[The Open Feedback Publishing System (OFPS) is an O'Reilly experiment that tries to bridge the gap between private manuscripts and public blogs. Following on the let-them-comment-on-everything model established by the Django Book, Real World Haskell, and Mercurial: The Definitive Guide (among others), OFPS allows readers to read in-progress O'Reilly manuscripts, communicate suggestions with the authors, follow others' comments, and directly participate in the development of new books.

Manuscripts developed with OFPS sites allow the authors to publish the in-progress work as whenever they think it's ready for public comment and then update the site with new versions as the text is improved. Authors note sections of the text that they'd like comments on (potentially down to an individual paragraph) and that allows readers on the site to comment on that particular section.]]></description>
<dc:subject>publishing writing blogging books internet collaboration</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:caseygollan/b:2b7450b6da64/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:writing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:blogging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:collaboration"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://techcrunch.com/2011/03/17/whom-to-hire-at-a-startup-attitude-over-aptitude/%20">
    <title>Whom Should You Hire at a Startup? (Attitude over Aptitude)</title>
    <dc:date>2011-03-18T16:48:00+00:00</dc:date>
    <link>http://techcrunch.com/2011/03/17/whom-to-hire-at-a-startup-attitude-over-aptitude/%20</link>
    <dc:creator>caseygollan</dc:creator><dc:subject>startups hiring business collaboration</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:caseygollan/b:a9bee6bdc0f0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:startups"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:hiring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:collaboration"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://clementvalla.com/index.php?/printed/sol-lewitt--mechanical-turk/%20">
    <title>Sol Lewitt Mechanical Turk : clementvalla</title>
    <dc:date>2011-03-14T01:41:26+00:00</dc:date>
    <link>http://clementvalla.com/index.php?/printed/sol-lewitt--mechanical-turk/%20</link>
    <dc:creator>caseygollan</dc:creator><description><![CDATA[Custom software recreates various Sol LeWitt drawings. The software also posts instructions on Amazon.com’s Mechanical Turk. Human workers execute the drawings online based on the instructions from the program. The workers are paid 5¢ for each drawing. The software then assembles the drawings in a grid. The computer generated drawings, and the grids filled in by anonymous workers are displayed side by side.
]]></description>
<dc:subject>art systems collaboration outsourcing technology communication books conceptual boring</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:caseygollan/b:edfde3a7c08b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:art"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:systems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:outsourcing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:technology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:conceptual"/>
	<rdf:li rdf:resource="https://pinboard.in/u:caseygollan/t:boring"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>