<?xml version="1.0" encoding="utf-8"?><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: Must Programmers be Depressed Asocial Geeks?</title>
	<atom:link href="http://grandtextauto.org/2004/05/03/must-programmers-be-depressed-asocial-geeks/feed/" rel="self" type="application/rss+xml" />
	<link>http://grandtextauto.org/2004/05/03/must-programmers-be-depressed-asocial-geeks/</link>
	<description>A group blog about computer narrative, games, poetry, and art.</description>
	<lastBuildDate>Wed, 19 May 2010 01:52:58 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: nick</title>
		<link>http://grandtextauto.org/2004/05/03/must-programmers-be-depressed-asocial-geeks/comment-page-1/#comment-1255</link>
		<dc:creator>nick</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=318#comment-1255</guid>
		<description>Just when you thought the stereotypes of programmers couldn&#039;t get &lt;a href=&quot;http://www.salon.com/tech/feature/2002/08/28/0wnz0red/&quot;&gt;any worse...&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Just when you thought the stereotypes of programmers couldn&#8217;t get <a href="http://www.salon.com/tech/feature/2002/08/28/0wnz0red/">any worse&#8230;</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt K.</title>
		<link>http://grandtextauto.org/2004/05/03/must-programmers-be-depressed-asocial-geeks/comment-page-1/#comment-1256</link>
		<dc:creator>Matt K.</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=318#comment-1256</guid>
		<description>I share those same reservations about the book. It&#039;s a flawed novel--no question--and the skewed portrayal of the programmers (odd since Ullman is herself a long-time programmer) is only one issue. The narrative structure and point of view doesn&#039;t make much sense either, though it&#039;s perhaps obliquely accounted for by the trope of the memory leak. My students had mixed reactions to the book, largely because there were really no sympathetic or likeable characters (Ute, the German sysadmin is about the closest we get to that). Moreover, as Mark Bernstein and others have suggested, Ethan&#039;s  behavior bears a strong resemblance to Asperberger&#039;s Syndrome, and if that&#039;s the case then Ullman&#039;s treatment of him borders on the perverse. 



That said, the novel provoked its share of lively discussions, especially in my grad class which is composed entirely of humanities students--some of whom have very deep experiential knowledge of tech culture, and some of whom don&#039;t. The two cultures divide that gets played out through Berta and Ethan opened up a way for us to talk about code literarcy (the divide between those who can and can&#039;t code) in what may have been the most useful and intensive session of the semester. I don&#039;t believe a theoretical or historical reading would have provoked the same response. 



Finally, as Michael notes, the book is unusually eloquent on the minute particulars of coding. Despite the cloying, crushing unhappiness of the characters&#039; lives, Ullman captures the appeal of programming as world building. When I asked my grad students who wanted to go out and learn to code, I think every hand in the room went up. And I know at least one of them has followed through. Maybe some folks from ENGL 668 or 467, if they&#039;re reading, can chime in.</description>
		<content:encoded><![CDATA[<p>I share those same reservations about the book. It&#8217;s a flawed novel&#8211;no question&#8211;and the skewed portrayal of the programmers (odd since Ullman is herself a long-time programmer) is only one issue. The narrative structure and point of view doesn&#8217;t make much sense either, though it&#8217;s perhaps obliquely accounted for by the trope of the memory leak. My students had mixed reactions to the book, largely because there were really no sympathetic or likeable characters (Ute, the German sysadmin is about the closest we get to that). Moreover, as Mark Bernstein and others have suggested, Ethan&#8217;s  behavior bears a strong resemblance to Asperberger&#8217;s Syndrome, and if that&#8217;s the case then Ullman&#8217;s treatment of him borders on the perverse. </p>
<p>That said, the novel provoked its share of lively discussions, especially in my grad class which is composed entirely of humanities students&#8211;some of whom have very deep experiential knowledge of tech culture, and some of whom don&#8217;t. The two cultures divide that gets played out through Berta and Ethan opened up a way for us to talk about code literarcy (the divide between those who can and can&#8217;t code) in what may have been the most useful and intensive session of the semester. I don&#8217;t believe a theoretical or historical reading would have provoked the same response. </p>
<p>Finally, as Michael notes, the book is unusually eloquent on the minute particulars of coding. Despite the cloying, crushing unhappiness of the characters&#8217; lives, Ullman captures the appeal of programming as world building. When I asked my grad students who wanted to go out and learn to code, I think every hand in the room went up. And I know at least one of them has followed through. Maybe some folks from ENGL 668 or 467, if they&#8217;re reading, can chime in.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: michael</title>
		<link>http://grandtextauto.org/2004/05/03/must-programmers-be-depressed-asocial-geeks/comment-page-1/#comment-1257</link>
		<dc:creator>michael</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=318#comment-1257</guid>
		<description>I&#039;m glad to hear that the book did provoke intense discussion. The appeal of world building, and crossing the two culture divide are two topics I&#039;ve tried to engage in class discussion before using historical and theoretical readings - sounds like &lt;i&gt;The Bug&lt;/i&gt; successfully sparked that discussion. If I wasn&#039;t also trying to teach programming at the same time, I would definitely try it. But in the context of my class, I still need to think about it...</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad to hear that the book did provoke intense discussion. The appeal of world building, and crossing the two culture divide are two topics I&#8217;ve tried to engage in class discussion before using historical and theoretical readings &#8211; sounds like <i>The Bug</i> successfully sparked that discussion. If I wasn&#8217;t also trying to teach programming at the same time, I would definitely try it. But in the context of my class, I still need to think about it&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rita r</title>
		<link>http://grandtextauto.org/2004/05/03/must-programmers-be-depressed-asocial-geeks/comment-page-1/#comment-1258</link>
		<dc:creator>rita r</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=318#comment-1258</guid>
		<description>[my first comment on gta]: i just finished reading the novel yesterday - just by chance - so i thought i would chime in. i agree with michael and matt&#039;s comments about characterization and would add that the formal structure of the novel is often that of an instruction manual. her descriptions of conway, compilation et al are exceptionally lucid but the mode is very much that of _the pattern on the stone_. if you&#039;ll pardon the old-fashioned critical judgment, the prose in _close to the machine_ is much more elegant. still, the insider look at a 1980s software company alone is worth the price of admission. 
</description>
		<content:encoded><![CDATA[<p>[my first comment on gta]: i just finished reading the novel yesterday &#8211; just by chance &#8211; so i thought i would chime in. i agree with michael and matt&#8217;s comments about characterization and would add that the formal structure of the novel is often that of an instruction manual. her descriptions of conway, compilation et al are exceptionally lucid but the mode is very much that of _the pattern on the stone_. if you&#8217;ll pardon the old-fashioned critical judgment, the prose in _close to the machine_ is much more elegant. still, the insider look at a 1980s software company alone is worth the price of admission.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
