<?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: Software misengineering</title>
	<atom:link href="http://sketches.bumblebeelabs.com/software-misengineering/feed/" rel="self" type="application/rss+xml" />
	<link>http://sketches.bumblebeelabs.com/software-misengineering/</link>
	<description>Ideas, unorganized</description>
	<lastBuildDate>Fri, 12 Mar 2010 18:52:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Gregory Michael Travis</title>
		<link>http://sketches.bumblebeelabs.com/software-misengineering/comment-page-1/#comment-8651</link>
		<dc:creator>Gregory Michael Travis</dc:creator>
		<pubDate>Fri, 04 Dec 2009 20:44:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bumblebeelabs.com/?p=993#comment-8651</guid>
		<description>&quot;Mask&quot; is the operative word here.  Software is very complicated, and we use abstraction to hide things, in the hopes that we can create more complicated things without screwing them up.&lt;br&gt;&lt;br&gt;Programming is all about *hiding* stuff.  There is so much that is invisible.  While debugging a program, you are generally looking at a tiny tiny portion of it, like scanning a stadium with a flashlight.&lt;br&gt;&lt;br&gt;Every programmer of a certain age knows that software was more stable years ago, because it was smaller.  As it has gotten bigger, it&#039;s gotten less stable.  We&#039;re still surprised by this because we are employing increasingly sophisticated tools and techniques, but apparently they can&#039;t possibly keep up with the problems caused by size.&lt;br&gt;&lt;br&gt;Larger programs mean more things are hidden.  Code rot is almost never discovered early.  Programmers who cause code rot are almost never discovered early.&lt;br&gt;&lt;br&gt;I can&#039;t account for the FizzBuzz effect at all, but it&#039;s been a while since I was in school so I really have no idea what goes on there; all I know is that it has got to be really different than it was when I was in school.</description>
		<content:encoded><![CDATA[<p>&#8220;Mask&#8221; is the operative word here.  Software is very complicated, and we use abstraction to hide things, in the hopes that we can create more complicated things without screwing them up.</p>
<p>Programming is all about *hiding* stuff.  There is so much that is invisible.  While debugging a program, you are generally looking at a tiny tiny portion of it, like scanning a stadium with a flashlight.</p>
<p>Every programmer of a certain age knows that software was more stable years ago, because it was smaller.  As it has gotten bigger, it&#39;s gotten less stable.  We&#39;re still surprised by this because we are employing increasingly sophisticated tools and techniques, but apparently they can&#39;t possibly keep up with the problems caused by size.</p>
<p>Larger programs mean more things are hidden.  Code rot is almost never discovered early.  Programmers who cause code rot are almost never discovered early.</p>
<p>I can&#39;t account for the FizzBuzz effect at all, but it&#39;s been a while since I was in school so I really have no idea what goes on there; all I know is that it has got to be really different than it was when I was in school.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
