<?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 (rybesh)</title>
    <link>https://pinboard.in/u:rybesh/public/</link>
    <description>recent bookmarks from rybesh</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://github.com/copier-org/copier/"/>
	<rdf:li rdf:resource="https://blog.prototypr.io/guide-for-effective-projects-teams-management-bc6852738dcb"/>
	<rdf:li rdf:resource="https://github.com/recipy/recipy"/>
	<rdf:li rdf:resource="https://dmp.cdlib.org/"/>
	<rdf:li rdf:resource="http://blog.factual.com/introducing-drake-a-kind-of-make-for-data"/>
	<rdf:li rdf:resource="http://www.librarything.com/review/86646140"/>
	<rdf:li rdf:resource="http://www.librarything.com/work/10582957/reviews/73669750"/>
	<rdf:li rdf:resource="https://github.com/nodejitsu/haibu"/>
	<rdf:li rdf:resource="http://www.lib.unc.edu/datamanagement/index.html"/>
	<rdf:li rdf:resource="http://docs.lib.purdue.edu/cgi/viewcontent.cgi?article=1092&amp;context=lib_research"/>
	<rdf:li rdf:resource="http://www.joelonsoftware.com/items/2007/10/26.html"/>
	<rdf:li rdf:resource="http://clemesha.org/blog/2009/jul/05/modern-python-hacker-tools-virtualenv-fabric-pip/"/>
	<rdf:li rdf:resource="http://supervisord.org/"/>
	<rdf:li rdf:resource="http://feeds.feedburner.com/~r/FoundHistory/~3/409568111/"/>
	<rdf:li rdf:resource="http://roundup.sourceforge.net/"/>
	<rdf:li rdf:resource="http://feeds.feedburner.com/~r/FoundHistory/~3/308124637/"/>
	<rdf:li rdf:resource="http://www.economist.com/opinion/displaystory.cfm?story_id=9725272"/>
	<rdf:li rdf:resource="http://ipydis.org/eloka/"/>
	<rdf:li rdf:resource="http://www.eol.ucar.edu/projects/aon-cadis/"/>
	<rdf:li rdf:resource="http://www.useplus.com/home.asp"/>
	<rdf:li rdf:resource="http://maczealots.com/tutorials/drupal/"/>
	<rdf:li rdf:resource="http://www.granicus.com/solutions/streaming.html"/>
	<rdf:li rdf:resource="http://www.glscube.org/index.html"/>
	<rdf:li rdf:resource="http://www.mariascharf.com/"/>
	<rdf:li rdf:resource="http://www.cultos.org/"/>
	<rdf:li rdf:resource="http://slashdot.org/comments.pl?sid=164858&amp;cid=13758721"/>
	<rdf:li rdf:resource="http://psi.berkeley.edu/"/>
	<rdf:li rdf:resource="http://www.research.ibm.com/UIMA/"/>
	<rdf:li rdf:resource="http://www.timclark.net/tsurumi/Tsurumi_2005.pdf"/>
	<rdf:li rdf:resource="http://www.amazon.com/exec/obidos/ASIN/0932633439/webservices-20?dev-t=D151B5UYK93CM2%26camp=2025%26link_code=xm2"/>
	<rdf:li rdf:resource="http://www.amazon.com/exec/obidos/ASIN/0671671642/webservices-20?dev-t=D151B5UYK93CM2%26camp=2025%26link_code=xm2"/>
	<rdf:li rdf:resource="http://www.amazon.com/exec/obidos/ASIN/0316178314/webservices-20?dev-t=D151B5UYK93CM2%26camp=2025%26link_code=xm2"/>
	<rdf:li rdf:resource="http://www.amazon.com/exec/obidos/ASIN/0195126165/webservices-20?dev-t=D151B5UYK93CM2%26camp=2025%26link_code=xm2"/>
	<rdf:li rdf:resource="http://www.amazon.com/exec/obidos/ASIN/B00008JYQ8/webservices-20?dev-t=D151B5UYK93CM2%26camp=2025%26link_code=xm2"/>
	<rdf:li rdf:resource="http://www.amazon.com/exec/obidos/ASIN/0385512058/webservices-20?dev-t=D151B5UYK93CM2%26camp=2025%26link_code=xm2"/>
	<rdf:li rdf:resource="http://features.slashdot.org/article.pl?sid=05/04/18/164213&amp;tid=95&amp;tid=149&amp;tid=9"/>
	<rdf:li rdf:resource="http://www.mantisbt.org/"/>
	<rdf:li rdf:resource="http://37signals.com/svn/archives2/some_notes_on_the_building_of_codezoo.php"/>
	<rdf:li rdf:resource="http://www.xml.com/pub/a/2004/10/27/extend.html?page=1"/>
	<rdf:li rdf:resource="http://projects.edgewall.com/qunittest/"/>
	<rdf:li rdf:resource="http://www.edgewall.com/trac/"/>
	<rdf:li rdf:resource="http://www.animemusicvideos.org/phpBB/viewtopic.php?t=41184"/>
	<rdf:li rdf:resource="http://scrum.minty.org/"/>
	<rdf:li rdf:resource="http://urlgreyhot.com/personal/node/2161"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://github.com/copier-org/copier/">
    <title>copier-org/copier: Library and command-line utility for rendering projects templates.</title>
    <dc:date>2023-01-12T15:15:02+00:00</dc:date>
    <link>https://github.com/copier-org/copier/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Library and command-line utility for rendering projects templates.]]></description>
<dc:subject>project management development code</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:723a84514053/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:project"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:code"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.prototypr.io/guide-for-effective-projects-teams-management-bc6852738dcb">
    <title>Guide for Effective Projects &amp; Teams Management - Prototypr</title>
    <dc:date>2019-12-10T14:11:21+00:00</dc:date>
    <link>https://blog.prototypr.io/guide-for-effective-projects-teams-management-bc6852738dcb</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The ability to manage projects and teams is a valuable asset in the industry today, as organisations are continuingly faced with complex problems that require collaboration between professionals to solve it (Wheelan, 2016). The collaboration often is complex, because it involves a multidisciplinary team with various nature way of working, different perspective and skill background, personal preferences and management structures (Nancarrow et al., 2013). It is important to understand that dealing with teams means dealing with people, and therefore understanding people management comes rst before everything else (George, 2012). This guide will discuss culture in working place and provide the essential steps and tools to manage projects and teams. Although the effectiveness of the guide relies on the team dynamics, it will provide a practical overview of managing projects and teams.]]></description>
<dc:subject>teaching collaboration management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f72297b8211b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:teaching"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/recipy/recipy">
    <title>recipy/recipy</title>
    <dc:date>2015-08-27T23:24:20+00:00</dc:date>
    <link>https://github.com/recipy/recipy</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[With the addition of a single line of code to the top of your Python files, ReciPy will log each run of your code to a database, keeping track of the input files, output files and the version of your code.]]></description>
<dc:subject>python provenance research metadata management tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8b4c39660da2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:provenance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://dmp.cdlib.org/">
    <title>Data Management Plan Tool | Home</title>
    <dc:date>2013-04-29T23:53:01+00:00</dc:date>
    <link>https://dmp.cdlib.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Several universities and organizations are developing the DMPTool to help researchers meet these new requirements. In specific, the DMPTool will help researchers:

Create ready-to-use data management plans for specific funding agencies
Meet requirements for data management plans
Get step-by-step instructions and guidance for data management plan
Learn about resources and services available at your institution to fulfill the data management requirements of their grants]]></description>
<dc:subject>research data curation tools management grants</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cbef0bcf3910/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:curation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:grants"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.factual.com/introducing-drake-a-kind-of-make-for-data">
    <title>Introducing Drake, a kind of ‘make for data’ - Factual Blog</title>
    <dc:date>2013-04-28T23:56:16+00:00</dc:date>
    <link>http://blog.factual.com/introducing-drake-a-kind-of-make-for-data</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Drake is a text-based command line data workflow tool that organizes command execution around data and its dependencies. Data processing steps are defined along with their inputs and outputs.  It automatically resolves dependencies and provides a rich set of options for controlling the workflow. It supports multiple inputs and outputs and has HDFS support built-in.

We use Drake at Factual on various internal projects. It serves as a primary way to define, run, and manage data workflow. Some core benefits we’ve seen:
Non-programmers can run Drake and fully manage a workflow
Encourages repeatability of the overall data building process
Encourages consistent organization (e.g., where supporting scripts live, and how they’re run)
Precise control over steps (for more effective testing, debugging, etc.)
Unifies different tools in a single workflow (shell commands, Ruby, Python, Clojure, pushing data to production, etc.)]]></description>
<dc:subject>data fbp analytics management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5e810562cb8f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:fbp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:analytics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.librarything.com/review/86646140">
    <title>Paper Machines: About Cards &amp; Catalogs, 1548-1929 (History and Foundations of Information Science) by Markus Krajewski | LibraryThing</title>
    <dc:date>2012-09-22T04:32:57+00:00</dc:date>
    <link>http://www.librarything.com/review/86646140</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Timothy Burke's review of Krajewski, Markus. Paper Machines?: About Cards & Catalogs, 1548-1929. MIT Press,, 2011. Print. History and Foundations of Information Science.

Intellectual, material and technological history of the "file card" and its incorporation into the structure and conception of digital file storage and access. Central object of focus is the card catalog. 

Starts with the question: why was there a moment where the designers of card catalogs promised they would be in some sense "universal information devices" capable of almost anything?]]></description>
<dc:subject>information management history inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ff2eb3d95a48/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:information"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.librarything.com/work/10582957/reviews/73669750">
    <title>Too Much to Know: Managing Scholarly Information before the Modern Age by Ann M. Blair | LibraryThing</title>
    <dc:date>2012-09-19T13:08:11+00:00</dc:date>
    <link>http://www.librarything.com/work/10582957/reviews/73669750</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Timothy Burke's review of Ann Blair's Too Much to Know.]]></description>
<dc:subject>history information management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e92bc07668dc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:information"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/nodejitsu/haibu">
    <title>nodejitsu/haibu</title>
    <dc:date>2012-05-25T12:12:30+00:00</dc:date>
    <link>https://github.com/nodejitsu/haibu</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[haibu is the open-source node.js project used at Nodejitsu's for spawning and managing several node.js applications on a single server.]]></description>
<dc:subject>nodejs cloud management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:612620c054c4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nodejs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cloud"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.lib.unc.edu/datamanagement/index.html">
    <title>Research Data Toolkit</title>
    <dc:date>2012-03-26T21:30:12+00:00</dc:date>
    <link>http://www.lib.unc.edu/datamanagement/index.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Library's Data Management Committee has compiled this toolkit to help researchers understand the issues involved in data management and provide resources for formulating data management plans.]]></description>
<dc:subject>research data management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5d2ee5514f3b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://docs.lib.purdue.edu/cgi/viewcontent.cgi?article=1092&amp;context=lib_research">
    <title>Conducting a Data Interview</title>
    <dc:date>2011-09-08T03:24:57+00:00</dc:date>
    <link>http://docs.lib.purdue.edu/cgi/viewcontent.cgi?article=1092&amp;context=lib_research</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In this poster, we share a set of ten questions that a librarian can use as a starting point for such a “data interview”. It is not a comprehensive strategy but instead a practical tool to draw out information that needs to be considered in order to evaluate the suitability of a dataset for the collection and the requirements for the infrastructure and services that will be needed for data curation.]]></description>
<dc:subject>preservation data management curation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:69c5078ae413/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:preservation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:curation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.joelonsoftware.com/items/2007/10/26.html">
    <title>Evidence Based Scheduling - Joel on Software</title>
    <dc:date>2009-07-20T17:23:25+00:00</dc:date>
    <link>http://www.joelonsoftware.com/items/2007/10/26.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[You gather evidence, mostly from historical timesheet data, that you feed back into your schedules. What you get is not just one ship date: you get a confidence distribution curve, showing the probability that you will ship on any given date.
]]></description>
<dc:subject>statistics business planning development software management</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:7e9eaf8d1e8e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:statistics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:planning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://clemesha.org/blog/2009/jul/05/modern-python-hacker-tools-virtualenv-fabric-pip/">
    <title>Tools of the Modern Python Hacker: Virtualenv, Fabric and Pip</title>
    <dc:date>2009-07-09T18:49:59+00:00</dc:date>
    <link>http://clemesha.org/blog/2009/jul/05/modern-python-hacker-tools-virtualenv-fabric-pip/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[For the modern Python programmer, some of the most important tools to aid in reduced complexity and repetition are virtualenv, Fabric, and pip.
]]></description>
<dc:subject>python code development management howto</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:3d8d85e8a0ac/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://supervisord.org/">
    <title>Supervisor</title>
    <dc:date>2009-06-07T18:33:05+00:00</dc:date>
    <link>http://supervisord.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Supervisor is a client/server system that allows its users to monitor and control a number of processes on UNIX-like operating systems.
]]></description>
<dc:subject>unix distributed management tools python</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:b76f65982d64/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:unix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://feeds.feedburner.com/~r/FoundHistory/~3/409568111/">
    <title>Making It Count: Toward a Third Way</title>
    <dc:date>2008-10-02T17:51:58+00:00</dc:date>
    <link>http://feeds.feedburner.com/~r/FoundHistory/~3/409568111/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[
Over the summer there was much discussion among my colleagues about making digital humanities work “count” in academic careers. This included two fantastic threads on Mills Kelly’s Edwired blog, a great post by Kathy Davidson, and an informal chat on our own Digital Campus podcast. As usual the topic of tenure also undergirded discussions at the various digital humanities workshops and conferences I attended during June, July, and August. The cooler weather and tempers of autumn having arrived, I’d like to take a quick look back and commit to writing some of the thoughts I offered on our podcast and at these meetings.

Let me use Mills’ “Making Digital Scholarship Count” series as a starting point. For those of you who weren’t following his posts, Mills argues that if scholars want digital scholarship to count in traditional promotion and tenure decisions, then they have to make sure it conforms to the characteristics and standards of traditional scholarship (though Mills points out that some of those standards, such as peer review, will have to be modified slightly to accommodate the differences inherent in digital scholarship.)  At the same time Mills suggests that we have to accept that digital work that does not fit the standards of traditional scholarship, no matter how useful or well done, will not count in traditional promotion and tenure decisions. Essentially Mills makes a distinction between digital “scholarship” and other kinds of digital “work,” the first which bears the characteristics of traditional scholarship and the second which does not.  The first should count as “scholarship” in promotion and tenure decisions. The second should not. Rather it should count as “service” or something similar.

I more or less agree this, and I’m fine with Mills’ distinction. Communities have the right to set their own standards and decide what counts as this or that. But this situation does raise questions for those of us engaged primarily in the second kind of activity, in digital humanities “work.” What happens to the increasing numbers of people employed inside university departments doing “work” not “scholarship?” In universities that have committed to digital humanities, shouldn’t the work of creating and maintaining digital collections, building software, experimenting with new user interface designs, mounting online exhibitions, providing digital resources for students and teachers, and managing the institutional teams upon which all digital humanities depend count for more than service does under traditional P&T rubrics? Personally I’m not willing to admit that this other kind of digital work is any less important for digital humanities than digital scholarship, which frankly would not be possible without it. All digital humanities is collaborative, and it’s not OK if the only people whose careers benefit from our collaborations are the “scholars” among us. We need the necessary “work” of digital humanities to count for those people whose jobs are to do it.

Now I’m not arguing we bestow tenure in the history department for web design or project management, even if it’s done by people with PhD’s. What I am saying is if we’re going to do digital humanities in our departments, then we need something new. It can’t be tenure-track or nothing. With the emergence of the new digital humanities, we need some new employment models.

I myself do relatively little work that would fit traditional definitions of scholarship. Practically none of my digital work would. Because of that I am more than willing to accept that tenure just isn’t in the picture for me. With my digital bent I am asking for a change in the nature of academic work, and therefore I have to be willing to accept a change in the nature and terms of my academic employment. 

That said, I am not willing to accept the second-class status of, for instance, an adjunct faculty member. My work—whether it is “scholarship” or not—wins awards, attracts hundreds of thousands of dollars in grant funding, turns up periodically on CNN and in the New York Times, enables the work of hundreds of other academics, and is used every day by thousands of people, scholars and non-scholars alike. That may not make it tenureable, but it’s certainly not second class. My work requires a “third way.”

 Fortunately I’m at an institution committed to digital humanities and willing to experiment with new models of academic employment. Technically I have two titles, “Managing Director of the Center for History & New Media” and “Research Assistant Professor.” That puts me somewhere between an untenured administrative faculty member and an untenured research faculty member. It is a position which would frighten some of my tenure-track colleagues terribly, and I can, indeed, be fired from my job. Sometimes that worries me too. Then I remember that probably 99% of the rest of working Americans can also be fired from their jobs. I also remember that just like that other 99%, if I do what’s expected of me, it probably won’t happen. If I continue to win grants and awards from panels of my peers and continue to produce quality, well-received, well-used digital humanities products, I’ll probably continue to have a job. If I exceed expectations, I’ll probably advance.

Just as important to note are the benefits my job has over more traditional scholarly career paths, some of which are pretty serious. I’m not terrorized by the formalized expectations that accompany traditional P&T decisions. I won’t perish if I don’t publish. I also don’t have fixed teaching obligations. I can focus full-time on my research, and I have greater freedom and flexibility to explore new directions than most of my tenure-track colleagues. I get to work on lots of things at once. Some of these experiments are likely to fail, but as long as most succeed, that’s expected and OK. I manage my own travel budgets and research schedule rather than being held hostage to department committees. I get to work every day with a close-knit team of like-minded academics rather than alone in a library. I have considerably greater freedom to negotiate my pay and benefits. And to the extent that it advances the mission and interests of the Center for History & New Media, this blog “counts.”

Mine is not a tenure-track position, and based on the work I do, I don’t expect it to be. Nor do I care. There are some downsides and some upsides to my position, but it’s a reasonably happy third way. More importantly, I believe it is a necessary third way for the digital humanities, which in Mills’ terms require not only digital “scholarship” but also digital “work.” I’m lucky to be at an institution and to have colleagues that make this third way possible. Other institutions looking to build digital humanities capacity should follow suit. If digital humanities are going to flourish in the academy, we need both to accept and advocate for new models of academic employment.

[Image credit: Dave Morris]

Late Update (10/2/08): I very absentmindedly neglected to list my friend Margie McLellan among the important voices in this discussion. Along with Mills and Kathy Davidson, Margie’s three posts, On Defining Scholarship, Scholarship Update, and Is a Blog Scholarship?, are required reading on these matters.


     
]]></description>
<dc:subject>Digital_Humanities Management</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:e6d3429ac256/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:Digital_Humanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:Management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://roundup.sourceforge.net/">
    <title>Roundup Issue Tracker</title>
    <dc:date>2008-10-02T15:47:31+00:00</dc:date>
    <link>http://roundup.sourceforge.net/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Roundup is a simple-to-use and -install issue-tracking system with command-line, web and e-mail interfaces.
]]></description>
<dc:subject>python code management tools bugtracking</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:15e5357c7282/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:bugtracking"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://feeds.feedburner.com/~r/FoundHistory/~3/308124637/">
    <title>Six Tips for Hiring Good Programmers</title>
    <dc:date>2008-06-09T16:16:01+00:00</dc:date>
    <link>http://feeds.feedburner.com/~r/FoundHistory/~3/308124637/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[
 There has been a useful discussion on Twitter (of all places!) among some of the THATCamp participants about how to write a good help wanted ad for programmers for digital humanities projects.  Here are a few of the suggestions, mostly from the programmers in the bunch:


“All depends on what you’re looking for: a real programmer or just a code secretary? Good coders show up for fun real problems … code secretary = comes to meetings, takes orders, transcribes them into code without creative insight.”
“Regardless of the title, make clear if people will have the authority to use their own creativity and do things in new ways.”
“One suggestion is to get tied in to local user-group communities—especially ones that attract freelancers and learners.”
“But good programmers also get paid a bit better, and thrive on a community of other programmers (which means other area employers).”
“Another thing to tout is the ability to choose the technical stack, & freedom to explore new languages/frameworks, if true.”
“Also, is there any chance you could offer a referral bonus to univ employees?  No better applicants than that.”

Good tips. Good use of Twitter.

[Thanks to Karin Dalziel, Adam Solove, and Ben Brumfield for allowing me to republish this conversation! Image credit: Matt Wetzler.]

ShareThis
]]></description>
<dc:subject>Digital_Humanities Management Twitter</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:73f3156f7ebc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:Digital_Humanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:Management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:Twitter"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.economist.com/opinion/displaystory.cfm?story_id=9725272">
    <title>Who's afraid of Google? | Economist.com</title>
    <dc:date>2007-09-01T03:16:16+00:00</dc:date>
    <link>http://www.economist.com/opinion/displaystory.cfm?story_id=9725272</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Google is a capitalist tool—and a useful one. Better, surely, to face the coming storm on that foundation, than on a trite slogan that could be your undoing.
]]></description>
<dc:subject>google opinion privacy capitalism strategy perception management</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:fbb71ad03452/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:opinion"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:capitalism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:strategy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:perception"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ipydis.org/eloka/">
    <title>ELOKA</title>
    <dc:date>2007-08-13T15:42:08+00:00</dc:date>
    <link>http://ipydis.org/eloka/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[ELOKA will provide a data management and networking service for community-based research that keeps control of data in the hands of community data providers, while still allowing for broad searches and sharing of information.
]]></description>
<dc:subject>arctic community research data management delivery collaboration tools</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:f287fd5b2a9c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:arctic"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:community"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:delivery"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.eol.ucar.edu/projects/aon-cadis/">
    <title>AON-CADIS: Arctic Observing Network Cooperative Arctic Data and Information Service</title>
    <dc:date>2007-08-13T15:40:17+00:00</dc:date>
    <link>http://www.eol.ucar.edu/projects/aon-cadis/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[CADIS supports the Arctic Observing Network (AON). It will be a portal for data discovery, and provide near-real-time data delivery, a repository for data storage, and tools to manipulate data.
]]></description>
<dc:subject>arctic research data storage management delivery tools</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:5852d09ef4b2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:arctic"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:storage"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:delivery"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.useplus.com/home.asp">
    <title>:: PLUS ::</title>
    <dc:date>2007-03-21T05:07:26+00:00</dc:date>
    <link>http://www.useplus.com/home.asp</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A worldwide Coalition of leading companies, respected associations, and industry experts have joined this unprecedented non-profit mandate to clearly define and standardize the core aspects of image licensing and its management. Now we can all agree.
]]></description>
<dc:subject>image IP management standards copyright policy</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:4664f8a97c15/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:image"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:IP"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:copyright"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:policy"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://maczealots.com/tutorials/drupal/">
    <title>Installing Drupal on Tiger</title>
    <dc:date>2006-09-22T03:32:45+00:00</dc:date>
    <link>http://maczealots.com/tutorials/drupal/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[How to install Drupal on OSX.
]]></description>
<dc:subject>osx content management tools howto drupal</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:cc9d1708d66b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:osx"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:content"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:drupal"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.granicus.com/solutions/streaming.html">
    <title>Granicus MediaManager</title>
    <dc:date>2006-09-22T01:46:26+00:00</dc:date>
    <link>http://www.granicus.com/solutions/streaming.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Granicus opens the door for local government municipalities to webcast and deliver rich media to all their constituents. Indexing by keyword, with video linked to meeting minutes.
]]></description>
<dc:subject>web video management tools public government timetags</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:1e26cccc60d4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:video"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:public"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:government"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:timetags"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.glscube.org/index.html">
    <title>GLScube.org</title>
    <dc:date>2006-07-22T20:25:59+00:00</dc:date>
    <link>http://www.glscube.org/index.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Tagging the desktop.
]]></description>
<dc:subject>metadata documents search database management unix tools opensource storage</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:54604bca8689/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documents"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:search"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:unix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:storage"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.mariascharf.com/">
    <title>Maria Christina Binz-Scharf</title>
    <dc:date>2006-03-26T06:34:19+00:00</dc:date>
    <link>http://www.mariascharf.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Research interests are information technology and organizational behavior, social networks, and organizational theory.
]]></description>
<dc:subject>information technology organization theory social networking academia people economics management nyc</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:ad7a88b5e3c0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:information"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:technology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:organization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:theory"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:social"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:networking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:academia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:people"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:economics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nyc"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.cultos.org/">
    <title>CULTOS - Multimedia Knowledge Management Tools for Culture and Arts</title>
    <dc:date>2005-11-13T05:25:04+00:00</dc:date>
    <link>http://www.cultos.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[It includes a knowledge model of intertextual studies, a standardised hypermedia document model and a prototype multimedia authoring tool for use in the publishing life-cycle.
]]></description>
<dc:subject>multimedia research management tools culture art hypermedia authoring kr metadata</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:9c7ee9dc1ffe/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:multimedia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:art"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hypermedia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authoring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:kr"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://slashdot.org/comments.pl?sid=164858&amp;cid=13758721">
    <title>Yahoo Launches New Podcasting Service</title>
    <dc:date>2005-10-11T03:02:32+00:00</dc:date>
    <link>http://slashdot.org/comments.pl?sid=164858&amp;cid=13758721</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[I like knowing which shows I've heard, and which I still need to have a listen, and being able to pick up where I left off when I get interupted. iTunes, presents this information in a very intuitive way.
]]></description>
<dc:subject>media management interface design mp3 audio blog yahoo timetags</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:e7cedc58d94c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:media"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:mp3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:audio"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:blog"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:yahoo"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:timetags"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://psi.berkeley.edu/">
    <title>Petabyte Storage Infrastructure Project</title>
    <dc:date>2005-08-31T23:12:50+00:00</dc:date>
    <link>http://psi.berkeley.edu/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Aims to provide low-cost, petabyte-scale, generic storage via the use of replicated commodity components, disk-to-disk backup, and a high level of administrative automation.
]]></description>
<dc:subject>storage research p2p management</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:3745b6dbffb1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:storage"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:p2p"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.research.ibm.com/UIMA/">
    <title>UIMA: Unstructured Information Analysis Architecture</title>
    <dc:date>2005-08-09T15:46:47+00:00</dc:date>
    <link>http://www.research.ibm.com/UIMA/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[It is an open, industrial-strength, scaleable and extensible platform for creating, integrating and deploying unstructured information management solutions from combinations of semantic analysis and search components.
]]></description>
<dc:subject>ai architecture community knowledge management nlp opensource research search semantics semweb standards</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:9501509db066/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:community"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:knowledge"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nlp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:search"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semantics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.timclark.net/tsurumi/Tsurumi_2005.pdf">
    <title>Dysfunctional Management Education and Damaged Capitalism in America</title>
    <dc:date>2005-06-27T02:44:45+00:00</dc:date>
    <link>http://www.timclark.net/tsurumi/Tsurumi_2005.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Dysfunctional business and political leaders cause the social, political and economic malaise afflicting America. It produces an MBA mindset that embraces the robber baron culture and Social Darwinism of market and Christian fundamentalism.
]]></description>
<dc:subject>usa business culture economics policy social japan management capitalism</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:e5407509915b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:usa"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:economics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:policy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:social"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:japan"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:capitalism"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.amazon.com/exec/obidos/ASIN/0932633439/webservices-20?dev-t=D151B5UYK93CM2%26camp=2025%26link_code=xm2">
    <title>Timothy Lister, Tom Demarco: Peopleware</title>
    <dc:date>2005-06-23T21:46:08+00:00</dc:date>
    <link>http://www.amazon.com/exec/obidos/ASIN/0932633439/webservices-20?dev-t=D151B5UYK93CM2%26camp=2025%26link_code=xm2</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Lister and Demarco capture in this text the essence of why so many projects and initiatives fail across corporate landscapes - communication, planning, structure, and leadership...
]]></description>
<dc:subject>books 1999 urn:asin:0932633439 wishlist business humanresources management</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:04f9e2a73a91/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:1999"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:urn:asin:0932633439"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wishlist"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:humanresources"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.amazon.com/exec/obidos/ASIN/0671671642/webservices-20?dev-t=D151B5UYK93CM2%26camp=2025%26link_code=xm2">
    <title>Paul Hawken: GROWING A BUSINESS</title>
    <dc:date>2005-06-23T21:45:51+00:00</dc:date>
    <link>http://www.amazon.com/exec/obidos/ASIN/0671671642/webservices-20?dev-t=D151B5UYK93CM2%26camp=2025%26link_code=xm2</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[I just sold my company and, looking back over the ten years it took to build, this book was the BEST resource and touchston I had...
]]></description>
<dc:subject>books 1988 urn:asin:0671671642 wishlist business management self smallbusiness</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:89021913d013/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:1988"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:urn:asin:0671671642"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wishlist"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:self"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:smallbusiness"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.amazon.com/exec/obidos/ASIN/0316178314/webservices-20?dev-t=D151B5UYK93CM2%26camp=2025%26link_code=xm2">
    <title>Edward De Bono: Six Thinking Hats</title>
    <dc:date>2005-06-23T21:27:26+00:00</dc:date>
    <link>http://www.amazon.com/exec/obidos/ASIN/0316178314/webservices-20?dev-t=D151B5UYK93CM2%26camp=2025%26link_code=xm2</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[I don't know that much about the author, but this book is nothing but the usual obvious bromides...
]]></description>
<dc:subject>books 1999 urn:asin:0316178314 wishlist business creativity management</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:eadd561527af/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:1999"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:urn:asin:0316178314"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wishlist"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:creativity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.amazon.com/exec/obidos/ASIN/0195126165/webservices-20?dev-t=D151B5UYK93CM2%26camp=2025%26link_code=xm2">
    <title>Ikujiro Nonaka, Kazuo Ichijo, Georg Von Krogh: Enabling Knowledge Creation</title>
    <dc:date>2005-06-23T19:41:43+00:00</dc:date>
    <link>http://www.amazon.com/exec/obidos/ASIN/0195126165/webservices-20?dev-t=D151B5UYK93CM2%26camp=2025%26link_code=xm2</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This book made me discover knowledge management...
]]></description>
<dc:subject>books 2000 urn:asin:0195126165 wishlist business management motivational</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:95e01def4737/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:2000"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:urn:asin:0195126165"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wishlist"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:motivational"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.amazon.com/exec/obidos/ASIN/B00008JYQ8/webservices-20?dev-t=D151B5UYK93CM2%26camp=2025%26link_code=xm2">
    <title>Robert I. Sutton: Weird Ideas That Work</title>
    <dc:date>2005-06-23T19:13:46+00:00</dc:date>
    <link>http://www.amazon.com/exec/obidos/ASIN/B00008JYQ8/webservices-20?dev-t=D151B5UYK93CM2%26camp=2025%26link_code=xm2</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Choose your favourite weird (or not so weird) idea...
]]></description>
<dc:subject>books 2001 urn:asin:B00008JYQ8 wishlist bargain business consulting decisionmaking management creative</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:7a4b92f9aaa6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:2001"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:urn:asin:B00008JYQ8"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wishlist"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:bargain"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:consulting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:decisionmaking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:creative"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.amazon.com/exec/obidos/ASIN/0385512058/webservices-20?dev-t=D151B5UYK93CM2%26camp=2025%26link_code=xm2">
    <title>Keith Ferrazzi, Tahl Raz: Never Eat Alone</title>
    <dc:date>2005-06-23T19:10:05+00:00</dc:date>
    <link>http://www.amazon.com/exec/obidos/ASIN/0385512058/webservices-20?dev-t=D151B5UYK93CM2%26camp=2025%26link_code=xm2</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[As much as many (competent, but charming challenged) people like to believe it's what you know that counts, it really does turn out that it is who you know that's more important...
]]></description>
<dc:subject>books 2005 urn:asin:0385512058 wishlist business careers generosity management motivational personalgrowth publicrelations</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:a8760d93985f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:2005"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:urn:asin:0385512058"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wishlist"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:careers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:generosity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:motivational"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:personalgrowth"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publicrelations"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://features.slashdot.org/article.pl?sid=05/04/18/164213&amp;tid=95&amp;tid=149&amp;tid=9">
    <title>The Early History of Nupedia and Wikipedia: A Memoir</title>
    <dc:date>2005-04-19T18:28:37+00:00</dc:date>
    <link>http://features.slashdot.org/article.pl?sid=05/04/18/164213&amp;tid=95&amp;tid=149&amp;tid=9</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A lengthy, informative account of the early history of Nupedia and Wikipedia, including some cogent observations on project management, online legitimacy, dealing with trolls, and other hazards of running a large, collaborative project over the Internet.
]]></description>
<dc:subject>wiki commons social media management collaboration</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:eda835b7dccc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wiki"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:commons"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:social"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:media"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:collaboration"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.mantisbt.org/">
    <title>Mantis Bug Tracker</title>
    <dc:date>2005-04-19T06:09:48+00:00</dc:date>
    <link>http://www.mantisbt.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Mantis is a php/MySQL/web based bugtracking system.
]]></description>
<dc:subject>code management opensource php tools</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:ecbac484015f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:php"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://37signals.com/svn/archives2/some_notes_on_the_building_of_codezoo.php">
    <title>Small teams rule.</title>
    <dc:date>2005-04-19T04:35:19+00:00</dc:date>
    <link>http://37signals.com/svn/archives2/some_notes_on_the_building_of_codezoo.php</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The efficiency of the team is approximately the inverse of the square of the number of members in the team. I'm beginning to think three people is optimal for a 1.0 product release.
]]></description>
<dc:subject>code management process howto</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:4574d207cdff/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:process"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.xml.com/pub/a/2004/10/27/extend.html?page=1">
    <title>XML.com: Extensibility, XML Vocabularies, and XML Schema</title>
    <dc:date>2005-02-22T03:19:37+00:00</dc:date>
    <link>http://www.xml.com/pub/a/2004/10/27/extend.html?page=1</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This article describes techniques to achieve more effective loose coupling between systems by providing a means for backwards- and forwards-compatible changes to occur when systems evolve.
]]></description>
<dc:subject>xml management standards howto</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:7b4c2b853e2c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:xml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://projects.edgewall.com/qunittest/">
    <title>Edgewall Software: QUnitTest</title>
    <dc:date>2005-02-13T00:18:05+00:00</dc:date>
    <link>http://projects.edgewall.com/qunittest/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[an easy-to-use GUI framework and application for use with the Python unit testing framework.
]]></description>
<dc:subject>python code management tools interface opensource</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:abb6df234327/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:opensource"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.edgewall.com/trac/">
    <title>Edgewall Software: Trac</title>
    <dc:date>2005-02-13T00:13:01+00:00</dc:date>
    <link>http://www.edgewall.com/trac/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Trac is an enhanced wiki and issue tracking system for software development projects.
]]></description>
<dc:subject>opensource code management tools wiki msmdx</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:acd8f2870460/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wiki"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:msmdx"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.animemusicvideos.org/phpBB/viewtopic.php?t=41184">
    <title>advice for project coordinators: tips for running multi-editor projects</title>
    <dc:date>2005-02-04T05:48:02+00:00</dc:date>
    <link>http://www.animemusicvideos.org/phpBB/viewtopic.php?t=41184</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Are there any suprising things the you wish to god someone had told you before you started your project?
]]></description>
<dc:subject>management anime editing social msmdx</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:e547fe942adc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:anime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:social"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:msmdx"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://scrum.minty.org/">
    <title>ScrumWiki</title>
    <dc:date>2005-01-18T17:37:20+00:00</dc:date>
    <link>http://scrum.minty.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A Wiki for Scrum. It has all the regular Wiki features, plus it adds the functionality to make managing Tasks, Teams, Sprints and Product Backlogs easier.
]]></description>
<dc:subject>management tools wiki perl</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:34bbb8c0a04f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wiki"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:perl"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://urlgreyhot.com/personal/node/2161">
    <title>Using a Wiki for Documentation and Collaborative Authoring</title>
    <dc:date>2004-12-14T17:15:43+00:00</dc:date>
    <link>http://urlgreyhot.com/personal/node/2161</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Capturing internal process, procedure and project information on a wiki.
]]></description>
<dc:subject>authoring howto management wiki msmdx collaboration</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:1bbcf0f72a89/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authoring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wiki"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:msmdx"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:collaboration"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>