<?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 for So Jake Says:</title>
	<atom:link href="http://www.jakevoytko.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jakevoytko.com/blog</link>
	<description>Ye Olde Computer Science Blogge</description>
	<pubDate>Sat, 17 May 2008 10:10:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>Comment on Somewhere Between Vim and Emacs There is a Great Text Editor by Naan Yaar</title>
		<link>http://www.jakevoytko.com/blog/2008/04/13/somewhere-between-vim-and-emacs-there-is-a-great-text-editor/#comment-6193</link>
		<dc:creator>Naan Yaar</dc:creator>
		<pubDate>Sat, 17 May 2008 04:46:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.jakevoytko.com/blog/?p=70#comment-6193</guid>
		<description>Hi,

I have been using Viper in XEmacs with the "expert" level set to 5. It has worked wonderfully, allowing me to use the best of both editors. I completely agree regarding the need to have "kitchen sink" capability and modal editing.

In Viper, I tend to use XEmacs keystrokes when I am in insert mode and use vi keystrokes for mostly everything else. The save and undo key combinations in XEmacs come in handy and I tend to use them a lot. Also, dabbrev-complete is unbelievably useful for any editing; I cannot live without this.

Why do you believe Viper is not the way to go?</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I have been using Viper in XEmacs with the &#8220;expert&#8221; level set to 5. It has worked wonderfully, allowing me to use the best of both editors. I completely agree regarding the need to have &#8220;kitchen sink&#8221; capability and modal editing.</p>
<p>In Viper, I tend to use XEmacs keystrokes when I am in insert mode and use vi keystrokes for mostly everything else. The save and undo key combinations in XEmacs come in handy and I tend to use them a lot. Also, dabbrev-complete is unbelievably useful for any editing; I cannot live without this.</p>
<p>Why do you believe Viper is not the way to go?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How Reddit Will (Maybe) Save Software Development by Bryce</title>
		<link>http://www.jakevoytko.com/blog/2008/05/12/how-reddit-will-maybe-save-software-development/#comment-5975</link>
		<dc:creator>Bryce</dc:creator>
		<pubDate>Tue, 13 May 2008 01:16:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.jakevoytko.com/blog/?p=78#comment-5975</guid>
		<description>Ooooh there are flames in these here comments!!! Lol that's sadly one of the best compliments the internet can give! 

Seriously thought provoking article though. Sadly I'm too fried to pop off a quality comment but an enjoyable read none the less.</description>
		<content:encoded><![CDATA[<p>Ooooh there are flames in these here comments!!! Lol that&#8217;s sadly one of the best compliments the internet can give! </p>
<p>Seriously thought provoking article though. Sadly I&#8217;m too fried to pop off a quality comment but an enjoyable read none the less.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How Reddit Will (Maybe) Save Software Development by William Bland</title>
		<link>http://www.jakevoytko.com/blog/2008/05/12/how-reddit-will-maybe-save-software-development/#comment-5955</link>
		<dc:creator>William Bland</dc:creator>
		<pubDate>Mon, 12 May 2008 15:45:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.jakevoytko.com/blog/?p=78#comment-5955</guid>
		<description>"Theorems that have withstood the test of time are falling, one by one; just ask Fermat and Poincaré."

You mean "conjectures", or "open problems" rather than "theorems".  Theorems are the end-product of mathematics.  Fermat's Last Theorem wasn't actually *known* to be a theorem until a proof was found - until then it was a conjecture.</description>
		<content:encoded><![CDATA[<p>&#8220;Theorems that have withstood the test of time are falling, one by one; just ask Fermat and Poincaré.&#8221;</p>
<p>You mean &#8220;conjectures&#8221;, or &#8220;open problems&#8221; rather than &#8220;theorems&#8221;.  Theorems are the end-product of mathematics.  Fermat&#8217;s Last Theorem wasn&#8217;t actually *known* to be a theorem until a proof was found - until then it was a conjecture.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How Reddit Will (Maybe) Save Software Development by Daniel Schumacher</title>
		<link>http://www.jakevoytko.com/blog/2008/05/12/how-reddit-will-maybe-save-software-development/#comment-5952</link>
		<dc:creator>Daniel Schumacher</dc:creator>
		<pubDate>Mon, 12 May 2008 15:00:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.jakevoytko.com/blog/?p=78#comment-5952</guid>
		<description>I agree with much of the setup, not the conclusion.  I agree that a social methodology of *design* is needed.  The software industry is immature... similar to when the auto industry made the model-T Ford (it could be argued we are earlier than that... after all the Model-T was reliable, cheap, and produced efficiently.)  My solution is to create a social requirements engineering system (this would also supersede bug dbs... since a bug is merely an anti-requirement.)  I would integrate this requirement system directly with the testing system (could be unit tests or other types.)  I'd call this "requirement verification".  This would make the "big triangle" of design-implement-test an actual triangle!  Today, at software companies I've worked at the triangle's sides are only vaguely related/connected.  I bought the domain "OpenRequirements.org" hoping to advance this idea... if anybody wants to work on it with me please get in touch.  I do a lot of CAD design (I create CAD software... IntelliCAD.)  Note that blueprint-style design is actually a thousands of years old practice.  The software industry has no analogous design methodology.  We are at the phase where we construct a wooden Indian from toothpicks, glue and chisels (and we stop when we have a wooden Indian or we run out of time.)  It should not be surprising that our end-products are of such low-quality, given this methodology.  The keys to improving our design capacity are:

 - Design captures requirements adequately.  Social "marketplace of ideas" methods ensure this.

 - Design is verifiable, and verified (integrated testing.)  This is like having "machine readable specifications"</description>
		<content:encoded><![CDATA[<p>I agree with much of the setup, not the conclusion.  I agree that a social methodology of *design* is needed.  The software industry is immature&#8230; similar to when the auto industry made the model-T Ford (it could be argued we are earlier than that&#8230; after all the Model-T was reliable, cheap, and produced efficiently.)  My solution is to create a social requirements engineering system (this would also supersede bug dbs&#8230; since a bug is merely an anti-requirement.)  I would integrate this requirement system directly with the testing system (could be unit tests or other types.)  I&#8217;d call this &#8220;requirement verification&#8221;.  This would make the &#8220;big triangle&#8221; of design-implement-test an actual triangle!  Today, at software companies I&#8217;ve worked at the triangle&#8217;s sides are only vaguely related/connected.  I bought the domain &#8220;OpenRequirements.org&#8221; hoping to advance this idea&#8230; if anybody wants to work on it with me please get in touch.  I do a lot of CAD design (I create CAD software&#8230; IntelliCAD.)  Note that blueprint-style design is actually a thousands of years old practice.  The software industry has no analogous design methodology.  We are at the phase where we construct a wooden Indian from toothpicks, glue and chisels (and we stop when we have a wooden Indian or we run out of time.)  It should not be surprising that our end-products are of such low-quality, given this methodology.  The keys to improving our design capacity are:</p>
<p> - Design captures requirements adequately.  Social &#8220;marketplace of ideas&#8221; methods ensure this.</p>
<p> - Design is verifiable, and verified (integrated testing.)  This is like having &#8220;machine readable specifications&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How Reddit Will (Maybe) Save Software Development by Greg Graham</title>
		<link>http://www.jakevoytko.com/blog/2008/05/12/how-reddit-will-maybe-save-software-development/#comment-5949</link>
		<dc:creator>Greg Graham</dc:creator>
		<pubDate>Mon, 12 May 2008 14:25:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.jakevoytko.com/blog/?p=78#comment-5949</guid>
		<description>When I saw you talking about Reddit and peer-review, I thought you were going to propose that programmers post their code in a Reddit-like forum, subject to votes and comments. The problem would be getting people to actually rigorously review the code. A lot of people comment and vote on things on Reddit without carefully reading the article or thinking about the subject. Reading and understanding code is more difficult than reading and understanding most articles.</description>
		<content:encoded><![CDATA[<p>When I saw you talking about Reddit and peer-review, I thought you were going to propose that programmers post their code in a Reddit-like forum, subject to votes and comments. The problem would be getting people to actually rigorously review the code. A lot of people comment and vote on things on Reddit without carefully reading the article or thinking about the subject. Reading and understanding code is more difficult than reading and understanding most articles.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How Reddit Will (Maybe) Save Software Development by Jake</title>
		<link>http://www.jakevoytko.com/blog/2008/05/12/how-reddit-will-maybe-save-software-development/#comment-5947</link>
		<dc:creator>Jake</dc:creator>
		<pubDate>Mon, 12 May 2008 13:43:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.jakevoytko.com/blog/?p=78#comment-5947</guid>
		<description>@Mitch:

I tried to hint at this (and apparently didn't state the idea clear enough), but design would be another thing that this system could handle.. though design tends to be more of an abstract concept. I don't immediately see how to peer-review sections of design in the general case, but I'll certainly think about it.</description>
		<content:encoded><![CDATA[<p>@Mitch:</p>
<p>I tried to hint at this (and apparently didn&#8217;t state the idea clear enough), but design would be another thing that this system could handle.. though design tends to be more of an abstract concept. I don&#8217;t immediately see how to peer-review sections of design in the general case, but I&#8217;ll certainly think about it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How Reddit Will (Maybe) Save Software Development by Mitch</title>
		<link>http://www.jakevoytko.com/blog/2008/05/12/how-reddit-will-maybe-save-software-development/#comment-5944</link>
		<dc:creator>Mitch</dc:creator>
		<pubDate>Mon, 12 May 2008 13:39:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.jakevoytko.com/blog/?p=78#comment-5944</guid>
		<description>Hey Jake, great article, I agree with you on the Truth about Software Engineering:
 
http://softwareindustrialization.com/TheTruthAboutSoftwareEngineering.aspx

However, I disagree with your approach.  Write more unit tests?  This is after the fact that the software has already been written – it’s too late and a) it has already cost way too much to get there, as you have already pointed out and b) the unit tests may prove (likely) that the software was not designed correctly in the first place and has to be rewritten, again at an exorbitant amount (see a).

The key word I believe is design.  And if you know about Jack Reeves and the source code is the design belief, then you know in reality, our world of software engineering suffers from no way to specify a software design and prove the software design works, before a single line of code has been written.  I believe that is the right problem to be solving as has been done in other “engineering disciplines.
Cheers!</description>
		<content:encoded><![CDATA[<p>Hey Jake, great article, I agree with you on the Truth about Software Engineering:</p>
<p><a href="http://softwareindustrialization.com/TheTruthAboutSoftwareEngineering.aspx" rel="nofollow">http://softwareindustrialization.com/TheTruthAboutSoftwareEngineering.aspx</a></p>
<p>However, I disagree with your approach.  Write more unit tests?  This is after the fact that the software has already been written – it’s too late and a) it has already cost way too much to get there, as you have already pointed out and b) the unit tests may prove (likely) that the software was not designed correctly in the first place and has to be rewritten, again at an exorbitant amount (see a).</p>
<p>The key word I believe is design.  And if you know about Jack Reeves and the source code is the design belief, then you know in reality, our world of software engineering suffers from no way to specify a software design and prove the software design works, before a single line of code has been written.  I believe that is the right problem to be solving as has been done in other “engineering disciplines.<br />
Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How Reddit Will (Maybe) Save Software Development by Jake</title>
		<link>http://www.jakevoytko.com/blog/2008/05/12/how-reddit-will-maybe-save-software-development/#comment-5943</link>
		<dc:creator>Jake</dc:creator>
		<pubDate>Mon, 12 May 2008 13:06:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.jakevoytko.com/blog/?p=78#comment-5943</guid>
		<description>@Bob:

I wondered if someone was going to catch that!</description>
		<content:encoded><![CDATA[<p>@Bob:</p>
<p>I wondered if someone was going to catch that!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How Reddit Will (Maybe) Save Software Development by Bob Holness</title>
		<link>http://www.jakevoytko.com/blog/2008/05/12/how-reddit-will-maybe-save-software-development/#comment-5941</link>
		<dc:creator>Bob Holness</dc:creator>
		<pubDate>Mon, 12 May 2008 12:45:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.jakevoytko.com/blog/?p=78#comment-5941</guid>
		<description>"...projects are still failing at an alarming rate."
"Programming failures are due to a lack of rigor at all levels"
"but if someone else wants to hack up their own version, awesome!"

Ha ha.</description>
		<content:encoded><![CDATA[<p>&#8220;&#8230;projects are still failing at an alarming rate.&#8221;<br />
&#8220;Programming failures are due to a lack of rigor at all levels&#8221;<br />
&#8220;but if someone else wants to hack up their own version, awesome!&#8221;</p>
<p>Ha ha.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How Reddit Will (Maybe) Save Software Development by Dan</title>
		<link>http://www.jakevoytko.com/blog/2008/05/12/how-reddit-will-maybe-save-software-development/#comment-5939</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Mon, 12 May 2008 12:21:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.jakevoytko.com/blog/?p=78#comment-5939</guid>
		<description>There is a plug-in for Hudson that does something similar (although without the modding up and down):

http://hudson.gotdns.com/wiki/display/HUDSON/The+Continuous+Integration+Game+plugin</description>
		<content:encoded><![CDATA[<p>There is a plug-in for Hudson that does something similar (although without the modding up and down):</p>
<p><a href="http://hudson.gotdns.com/wiki/display/HUDSON/The+Continuous+Integration+Game+plugin" rel="nofollow">http://hudson.gotdns.com/wiki/display/HUDSON/The+Continuous+Integration+Game+plugin</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
