<?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: Paying my Taxes</title>
	<atom:link href="http://stuffthathappens.com/blog/2007/09/25/paying-my-taxes/feed/" rel="self" type="application/rss+xml" />
	<link>http://stuffthathappens.com/blog/2007/09/25/paying-my-taxes/</link>
	<description>Technology and Geek Stuff by Eric Burke</description>
	<lastBuildDate>Thu, 04 Nov 2010 22:37:00 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Emmanuel Pirsch</title>
		<link>http://stuffthathappens.com/blog/2007/09/25/paying-my-taxes/comment-page-1/#comment-87</link>
		<dc:creator>Emmanuel Pirsch</dc:creator>
		<pubDate>Thu, 27 Sep 2007 18:38:50 +0000</pubDate>
		<guid isPermaLink="false">http://stuffthathappens.com/blog/2007/09/25/paying-my-taxes/#comment-87</guid>
		<description>Thanks for the shit : http://epirsch.blogspot.com/2007/09/more-on-continuous-tax-cedric-post-on.html</description>
		<content:encoded><![CDATA[<p>Thanks for the shit : <a href="http://epirsch.blogspot.com/2007/09/more-on-continuous-tax-cedric-post-on.html" rel="nofollow">http://epirsch.blogspot.com/2007/09/more-on-continuous-tax-cedric-post-on.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Weiqi Gao</title>
		<link>http://stuffthathappens.com/blog/2007/09/25/paying-my-taxes/comment-page-1/#comment-80</link>
		<dc:creator>Weiqi Gao</dc:creator>
		<pubDate>Wed, 26 Sep 2007 12:19:02 +0000</pubDate>
		<guid isPermaLink="false">http://stuffthathappens.com/blog/2007/09/25/paying-my-taxes/#comment-80</guid>
		<description>Had you made a similar return-type-altering change in Java, the compiler would have caught it as an error.  In that regard, the static typing works just like unit tests---it prevents you from breaking your code.</description>
		<content:encoded><![CDATA[<p>Had you made a similar return-type-altering change in Java, the compiler would have caught it as an error.  In that regard, the static typing works just like unit tests&#8212;it prevents you from breaking your code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Burke</title>
		<link>http://stuffthathappens.com/blog/2007/09/25/paying-my-taxes/comment-page-1/#comment-79</link>
		<dc:creator>Eric Burke</dc:creator>
		<pubDate>Wed, 26 Sep 2007 12:16:55 +0000</pubDate>
		<guid isPermaLink="false">http://stuffthathappens.com/blog/2007/09/25/paying-my-taxes/#comment-79</guid>
		<description>This particular method does not have good test coverage. Many other parts of this very small set of hooks do have good coverage. I just don&#039;t like invisible magic. I think it sucks for maintenance because there is no visible text telling you what is actually returned.</description>
		<content:encoded><![CDATA[<p>This particular method does not have good test coverage. Many other parts of this very small set of hooks do have good coverage. I just don&#8217;t like invisible magic. I think it sucks for maintenance because there is no visible text telling you what is actually returned.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Lewis</title>
		<link>http://stuffthathappens.com/blog/2007/09/25/paying-my-taxes/comment-page-1/#comment-77</link>
		<dc:creator>Dan Lewis</dc:creator>
		<pubDate>Wed, 26 Sep 2007 11:49:35 +0000</pubDate>
		<guid isPermaLink="false">http://stuffthathappens.com/blog/2007/09/25/paying-my-taxes/#comment-77</guid>
		<description>Good test coverage and language familiarity don&#039;t fix bad documentation.  Static typing doesn&#039;t fix it either.  However, &quot;static typing&quot; highlights the contradiction between docs and implementation.</description>
		<content:encoded><![CDATA[<p>Good test coverage and language familiarity don&#8217;t fix bad documentation.  Static typing doesn&#8217;t fix it either.  However, &#8220;static typing&#8221; highlights the contradiction between docs and implementation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mario Aquino</title>
		<link>http://stuffthathappens.com/blog/2007/09/25/paying-my-taxes/comment-page-1/#comment-76</link>
		<dc:creator>Mario Aquino</dc:creator>
		<pubDate>Wed, 26 Sep 2007 10:37:32 +0000</pubDate>
		<guid isPermaLink="false">http://stuffthathappens.com/blog/2007/09/25/paying-my-taxes/#comment-76</guid>
		<description>You have a good point about the need for up-to-date documentation for methods in dynamic languages.  There&#039;s just &quot;no way&quot; to fix this &quot;problem&quot;.  ;-)

Out of curiosity, did whatever code that had the mismatched method comments/return value have test coverage for that method? 

On returning the last evaluated statement in a method, I feel like that should be chalked up to learning the way the language works.  In my own reading of Ruby code, it is more common for methods to be written without a return statement.  As you become more familiar with the language and common idioms, you just get used to that.</description>
		<content:encoded><![CDATA[<p>You have a good point about the need for up-to-date documentation for methods in dynamic languages.  There&#8217;s just &#8220;no way&#8221; to fix this &#8220;problem&#8221;.  <img src='http://stuffthathappens.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>Out of curiosity, did whatever code that had the mismatched method comments/return value have test coverage for that method? </p>
<p>On returning the last evaluated statement in a method, I feel like that should be chalked up to learning the way the language works.  In my own reading of Ruby code, it is more common for methods to be written without a return statement.  As you become more familiar with the language and common idioms, you just get used to that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glen</title>
		<link>http://stuffthathappens.com/blog/2007/09/25/paying-my-taxes/comment-page-1/#comment-74</link>
		<dc:creator>Glen</dc:creator>
		<pubDate>Wed, 26 Sep 2007 03:51:51 +0000</pubDate>
		<guid isPermaLink="false">http://stuffthathappens.com/blog/2007/09/25/paying-my-taxes/#comment-74</guid>
		<description>I&#039;m not exactly sure what a continuous tax is supposed to be honest.  Clearly there are trade-off&#039;s in both directions when you choose between static and dynamically typed languages.  It will most likely be one of those areas where developers will be arguing about for many years to come.

I&#039;m personally happy developing with either sort of language.  My main issues with Java don&#039;t have much to do with the fact it&#039;s statically typed.  There are bigger issues that could be argued over.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not exactly sure what a continuous tax is supposed to be honest.  Clearly there are trade-off&#8217;s in both directions when you choose between static and dynamically typed languages.  It will most likely be one of those areas where developers will be arguing about for many years to come.</p>
<p>I&#8217;m personally happy developing with either sort of language.  My main issues with Java don&#8217;t have much to do with the fact it&#8217;s statically typed.  There are bigger issues that could be argued over.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.280 seconds -->

