<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.construx.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Matt&amp;#39;s Ground Truth - All Comments</title><link>http://blogs.construx.com/blogs/mattp/default.aspx</link><description>Commentary and perspective on challenging, triumphant, and mundane software development experiences. And lots of sacred cow killing. No, really, its like an abattoir in here...</description><dc:language>en</dc:language><generator>CommunityServer 2007.1 (Build: 20917.1142)</generator><item><title>re: Why Is Software Development Different? (and hard)</title><link>http://blogs.construx.com/blogs/mattp/archive/2008/07/30/2170.aspx#2264</link><pubDate>Mon, 13 Oct 2008 02:35:37 GMT</pubDate><guid isPermaLink="false">1c8bc03b-986a-40b9-ab6d-e8d23056df8a:2264</guid><dc:creator>Erich von Hauske</dc:creator><description>&lt;p&gt;&amp;quot;getting excited about the same fundamental principles over and over again&amp;quot;&lt;/p&gt;
&lt;p&gt;I believe that we get excited about them because they solve the problems we have in &amp;quot;simple&amp;quot; ways we didn&amp;#39;t know; we should&amp;#39;ve known them!, yes, but nobody taught them to us in college. In part because there&amp;#39;s little formalization of knowledge (the SWEBOK started in 1998 for example) and because knowledge is very scattered.&lt;/p&gt;
&lt;p&gt;This last point gets exacerbated by the fact that we LOVE the Internet and for that we are more sensitive to the misinformation effect of the Internet.&lt;/p&gt;
&lt;img src="http://blogs.construx.com/aggbug.aspx?PostID=2264" width="1" height="1"&gt;</description></item><item><title>re: Why Is Software Development Different? (and hard)</title><link>http://blogs.construx.com/blogs/mattp/archive/2008/07/30/2170.aspx#2196</link><pubDate>Fri, 22 Aug 2008 02:12:22 GMT</pubDate><guid isPermaLink="false">1c8bc03b-986a-40b9-ab6d-e8d23056df8a:2196</guid><dc:creator>Ben</dc:creator><description>&lt;p&gt;Part of the problem is that a badly made bridge will, generally, look wrong (although they do get made!) but badly written software doesn&amp;#39;t necessarily look any different from well written software. It is harder to spot. &lt;/p&gt;
&lt;p&gt;Also, as you say, the barrier to entry to stupidly low so that people who don&amp;#39;t normally write code can still get stuff done. Conversely, you can&amp;#39;t get an accountant who decides to have a go at building a new kind of smelter in their spare time.&lt;/p&gt;
&lt;p&gt;Put these two together and you have a recipe for chaos. It&amp;#39;s a miracle anything works at all!&lt;/p&gt;
&lt;img src="http://blogs.construx.com/aggbug.aspx?PostID=2196" width="1" height="1"&gt;</description></item><item><title>re: Throw Away Your Gantt Charts!</title><link>http://blogs.construx.com/blogs/mattp/archive/2007/04/20/Throw-away-your-gantt-charts.aspx#144</link><pubDate>Sun, 20 May 2007 19:48:54 GMT</pubDate><guid isPermaLink="false">1c8bc03b-986a-40b9-ab6d-e8d23056df8a:144</guid><dc:creator>Susan</dc:creator><description>This made me smile. I work as a software consultant at a company whose management loves Gantt charts. The software group is forced to have painful reviews of the schedule every couple of months. And, of course, none of the developers take these schedules seriously because they are so poorly estimated. Fortunately, I work with some rebels, so we do our own informal 2-week iteration plans behind the scenes. This has been much more useful to the group than all the Gantt charts lining the recycle bins.&lt;img src="http://blogs.construx.com/aggbug.aspx?PostID=144" width="1" height="1"&gt;</description></item></channel></rss>