<?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: The Verbosity Difference</title>
	<atom:link href="http://naml.us/blog/2009/08/verbosity-difference/feed" rel="self" type="application/rss+xml" />
	<link>http://naml.us/blog/2009/08/verbosity-difference</link>
	<description>Geoffrey Irving</description>
	<pubDate>Sun, 05 Sep 2010 05:19:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Geoffrey Irving</title>
		<link>http://naml.us/blog/2009/08/verbosity-difference#comment-147</link>
		<dc:creator>Geoffrey Irving</dc:creator>
		<pubDate>Thu, 20 Aug 2009 21:12:35 +0000</pubDate>
		<guid isPermaLink="false">http://naml.us/blog/?p=301#comment-147</guid>
		<description>&lt;p&gt;Yes, the coder is trading off code maintainability and learnability for time-to-market, but that's no excuse for a language which turns around and makes the coder stupider in response.  The problem is that once you've merged conceptually unrelated ideas into one, you really do start to think about those ideas as if they are the same, and that really does make you stupider (this happens to me all the time, so substitute "you" for "we" if you like).  That doesn't mean you were stupid to make that choice in the first place, which is exactly why I'm blaming it on the language rather than the programmer.&lt;/p&gt;

&lt;p&gt;Also, it's interesting that you left out &lt;em&gt;quality&lt;/em&gt; in your list of trade-offs.  It doesn't help to get code out the door really fast if the code is bad, and having the language trick you into picking the wrong abstractions will definitely lower quality.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Yes, the coder is trading off code maintainability and learnability for time-to-market, but that&#8217;s no excuse for a language which turns around and makes the coder stupider in response.  The problem is that once you&#8217;ve merged conceptually unrelated ideas into one, you really do start to think about those ideas as if they are the same, and that really does make you stupider (this happens to me all the time, so substitute &#8220;you&#8221; for &#8220;we&#8221; if you like).  That doesn&#8217;t mean you were stupid to make that choice in the first place, which is exactly why I&#8217;m blaming it on the language rather than the programmer.</p>

<p>Also, it&#8217;s interesting that you left out <em>quality</em> in your list of trade-offs.  It doesn&#8217;t help to get code out the door really fast if the code is bad, and having the language trick you into picking the wrong abstractions will definitely lower quality.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: bustos</title>
		<link>http://naml.us/blog/2009/08/verbosity-difference#comment-145</link>
		<dc:creator>bustos</dc:creator>
		<pubDate>Thu, 20 Aug 2009 03:29:58 +0000</pubDate>
		<guid isPermaLink="false">http://naml.us/blog/?p=301#comment-145</guid>
		<description>&lt;p&gt;Stupid is such a harsh term.  Do you think it would be more precise to say that the coder is trading off code maintainability and learnability for time-to-market?&lt;/p&gt;

&lt;p&gt;I think I make such tradeoffs in my coding, and it makes me uneasy because I know I don't have tools which allow me to easily go back and undo them later.  Maybe I should make a point of incorporating to-do lists into file comments.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Stupid is such a harsh term.  Do you think it would be more precise to say that the coder is trading off code maintainability and learnability for time-to-market?</p>

<p>I think I make such tradeoffs in my coding, and it makes me uneasy because I know I don&#8217;t have tools which allow me to easily go back and undo them later.  Maybe I should make a point of incorporating to-do lists into file comments.</p>]]></content:encoded>
	</item>
</channel>
</rss>
