<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/marks/link/299795">
<title>Public marks on http://charlespetzold.com/etc/DoesVisualStudioRotTheMind.html</title>
<description>Public marks on http://charlespetzold.com/etc/DoesVisualStudioRotTheMind.html</description>
<link>http://blogmarks.net/marks/link/299795</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/bcpbcp/mark/205842"/>
<rdf:li resource="http://blogmarks.net/api/user/nhoizey/mark/198896"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/bcpbcp/mark/205842">
<title>Does Visual Studio Rot the Mind?</title>
<link>http://charlespetzold.com/etc/DoesVisualStudioRotTheMind.html</link>
<description>Visual Studio can be one of the programmer's best friends, but over the years it has become increasingly pushy, domineering, and suffering from unsettling control issues. Should we just surrender to Visual Studio's insistence on writing our code for us? Or is Visual Studio sapping our programming intelligence rather than augmenting it? This talk dissects the code generated by Visual Studio</description>
<dc:date>2005-11-01T02:04:10Z</dc:date>
<dc:author>bcpbcp</dc:author>
<dc:subject>.net, 2005, writing, programming, c#, article, charlespetzold.com</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://charlespetzold.com/etc/DoesVisualStudioRotTheMind.html"><img border="0" src="http://www.blogmarks.net/screenshots/2005/10/28/da3818761afbf5e1439a0e55591d4477.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://charlespetzold.com/etc/DoesVisualStudioRotTheMind.html">Does Visual Studio Rot the Mind?</a></h4>
 
by <a href="http://blogmarks.net/user/bcpbcp">bcpbcp</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/299795">2 other(s)</a> 
<p class="description">Visual Studio can be one of the programmer's best friends, but over the years it has become increasingly pushy, domineering, and suffering from unsettling control issues. Should we just surrender to Visual Studio's insistence on writing our code for us? Or is Visual Studio sapping our programming intelligence rather than augmenting it? This talk dissects the code generated by Visual Studio</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/.net">.net</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/2005">2005</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/writing">writing</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/programming">programming</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/c%2523">c#</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/article">article</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/charlespetzold.com">charlespetzold.com</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=205842">Copy</a> | 
<a href="http://blogmarks.net/link/299795">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/nhoizey/mark/198896">
<title>Does Visual Studio Rot the Mind?</title>
<link>http://charlespetzold.com/etc/DoesVisualStudioRotTheMind.html</link>
<description>This talk dissects the code generated by Visual Studio; analyzes the appalling programming practices it perpetuates; rhapsodizes about the joys, frustrations, and satisfactions of unassisted coding; and speculates about the radical changes that Avalon will bring</description>
<dc:date>2005-10-28T09:29:38Z</dc:date>
<dc:author>nhoizey</dc:author>
<dc:subject>dev, .net, avalon, visual studio</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://charlespetzold.com/etc/DoesVisualStudioRotTheMind.html"><img border="0" src="http://www.blogmarks.net/screenshots/2005/10/28/da3818761afbf5e1439a0e55591d4477.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://charlespetzold.com/etc/DoesVisualStudioRotTheMind.html">Does Visual Studio Rot the Mind?</a></h4>
 
by <a href="http://blogmarks.net/user/nhoizey">nhoizey</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/299795">2 other(s)</a> 
<p class="description">This talk dissects the code generated by Visual Studio; analyzes the appalling programming practices it perpetuates; rhapsodizes about the joys, frustrations, and satisfactions of unassisted coding; and speculates about the radical changes that Avalon will bring</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dev">dev</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/.net">.net</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/avalon">avalon</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/visual%2Bstudio">visual studio</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=198896">Copy</a> | 
<a href="http://blogmarks.net/link/299795">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>