<?xml version="1.0" encoding="latin1"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Jones @ NCSU CS Graduation</title>
	<atom:link href="http://ibiblio.org/pjones/blog/jones-ncsu-cs-graduation/feed/" rel="self" type="application/rss+xml" />
	<link>http://ibiblio.org/pjones/blog/jones-ncsu-cs-graduation/</link>
	<description>Accept no substitutes</description>
	<lastBuildDate>Mon, 13 May 2013 23:06:32 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jason Young</title>
		<link>http://ibiblio.org/pjones/blog/jones-ncsu-cs-graduation/comment-page-1/#comment-218000</link>
		<dc:creator>Jason Young</dc:creator>
		<pubDate>Sun, 11 Nov 2007 19:25:11 +0000</pubDate>
		<guid isPermaLink="false">http://ibiblio.org/pjones/wordpress/?p=2344#comment-218000</guid>
		<description>That &quot;code is law.&quot;  They will be writing rules and instructions (or picking the rules and instructions from others in IT or program manager roles) that collect, store, route, and display information.   They will be asked to design and integrate software that &lt;em&gt;will&lt;/em&gt; decide access, that &lt;em&gt;will&lt;/em&gt; define roles, that &lt;em&gt;will&lt;/em&gt;shape opinions.     They have an incredible power to influence issues beyond the right algorithm, they have the power to make it easy or hard to protect the rights of content users as well as creators, to protect the privacy of the users of their software, to expose information.  They are designing Frankenstein, and have the responsibility to think beyond the task to the impact the choices they make will have on those that use their tools.</description>
		<content:encoded><![CDATA[<p>That &#8220;code is law.&#8221;  They will be writing rules and instructions (or picking the rules and instructions from others in IT or program manager roles) that collect, store, route, and display information.   They will be asked to design and integrate software that <em>will</em> decide access, that <em>will</em> define roles, that <em>will</em>shape opinions.     They have an incredible power to influence issues beyond the right algorithm, they have the power to make it easy or hard to protect the rights of content users as well as creators, to protect the privacy of the users of their software, to expose information.  They are designing Frankenstein, and have the responsibility to think beyond the task to the impact the choices they make will have on those that use their tools.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
