<?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"
	>
<channel>
	<title>Comments on: Polymorphism in C#/.NET Makes Code Incomprehensible</title>
	<atom:link href="http://aabs.wordpress.com/2006/12/06/polymorphism-in-cnet-makes-code-incomprehensible/feed/" rel="self" type="application/rss+xml" />
	<link>http://aabs.wordpress.com/2006/12/06/polymorphism-in-cnet-makes-code-incomprehensible/</link>
	<description>Closed weekends and holidays.</description>
	<pubDate>Sat, 05 Jul 2008 04:21:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
		<item>
		<title>By: Dan Winslow</title>
		<link>http://aabs.wordpress.com/2006/12/06/polymorphism-in-cnet-makes-code-incomprehensible/#comment-883</link>
		<dc:creator>Dan Winslow</dc:creator>
		<pubDate>Thu, 14 Dec 2006 15:15:01 +0000</pubDate>
		<guid isPermaLink="false">http://aabs.wordpress.com/2006/12/06/polymorphism-in-cnet-makes-code-incomprehensible/#comment-883</guid>
		<description>Modern coding seems to be all about abstraction, at th expense of all else. Rigor and proveability used to be emphasized, but have been abandoned in favor of refelection and what amounts to run-time modification of code.
All this has led to a proliferation of 'side-effects' and hidden mechnisms that render whats actually in the osurce code only a part of the story, and sometimes not even the major part. It really makes it hard to work with.

I don't like looking at stack traces that are 300-400 frames deep. I don't like trying to trace threads of control that wander all over the place between layers.</description>
		<content:encoded><![CDATA[<p>Modern coding seems to be all about abstraction, at th expense of all else. Rigor and proveability used to be emphasized, but have been abandoned in favor of refelection and what amounts to run-time modification of code.<br />
All this has led to a proliferation of &#8217;side-effects&#8217; and hidden mechnisms that render whats actually in the osurce code only a part of the story, and sometimes not even the major part. It really makes it hard to work with.</p>
<p>I don&#8217;t like looking at stack traces that are 300-400 frames deep. I don&#8217;t like trying to trace threads of control that wander all over the place between layers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
