<?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: There&#8217;s Still No Silver Bullet</title>
	<atom:link href="http://caseywest.com/2006/12/18/theres-still-no-silver-bullet/feed/" rel="self" type="application/rss+xml" />
	<link>http://caseywest.com/2006/12/18/theres-still-no-silver-bullet/</link>
	<description>Discursive ruminations.</description>
	<pubDate>Fri, 03 Sep 2010 20:07:27 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Taylor</title>
		<link>http://caseywest.com/2006/12/18/theres-still-no-silver-bullet/comment-page-1/#comment-108</link>
		<dc:creator>John Taylor</dc:creator>
		<pubDate>Thu, 23 Apr 2009 23:30:11 +0000</pubDate>
		<guid isPermaLink="false">http://caseywest.com/2006/12/18/theres-still-no-silver-bullet/#comment-108</guid>
		<description>Interesting blog post. What would you say was the most important marketing factor?</description>
		<content:encoded><![CDATA[<p>Interesting blog post. What would you say was the most important marketing factor?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrey Khavryuchenko</title>
		<link>http://caseywest.com/2006/12/18/theres-still-no-silver-bullet/comment-page-1/#comment-91</link>
		<dc:creator>Andrey Khavryuchenko</dc:creator>
		<pubDate>Wed, 20 Dec 2006 12:35:48 +0000</pubDate>
		<guid isPermaLink="false">http://caseywest.com/2006/12/18/theres-still-no-silver-bullet/#comment-91</guid>
		<description>You write:

&lt;blockquote&gt;I recently read Frederick P. Brooks, Jr.'s essay No Silver Bullet: Essence and Accidents of Software Engineering. Brooks wrote this paper 20 years ago and it still rings true today. I like the whole essay and encourage you to read it if you haven't already.

Brooks is an oft quoted writer. I'm going to indulge in the practice by pointing out a few things from this essay that I think will always be true.

&lt;blockquote&gt; Likewise, a scaling-up of a software entity is not merely a repetition of the same elements in larger sizes, it is necessarily an increase in the number of different elements. In most cases, the elements interact with each other in some nonlinear fashion, and the complexity of the whole increases much more than linearly.

The complexity of software is an essential property, not an accidental one. Hence, descriptions of a software entity that abstract away its complexity often abstract away its essence.
&lt;/blockquote&gt;
&lt;/blockquote&gt;

The Silver Bullet is considered yet unknown just because people look for it in wrong place.

See, Brooks himself says

&lt;blockquote&gt;
In many cases, the software must conform because it is the most recent arrival on the scene. In others, it must conform because it is perceived as the most conformable. But in all cases, much complexity comes from conformation to other interfaces; this complexity cannot be simplified out by any redesign of the software alone.
&lt;/blockquote&gt;

In other words, software is complex just because the surrounding world is complex.

So, how someone may dare to conquer the complex world with pure boolean logic and turing automata alone?

Since software reflects the world, I may bring an analogy between writing a software and doing a scientific research.

Any decent scientist will tell you that logic is not his close friend when he makes a breakthrough.  He uses logic to &lt;em&gt;prove&lt;/em&gt; that his idea will work (or won't work).  He uses it to plan experiments, write reports and grant proposals (err... the last one isn't logic).

Looking back at a software, no matter what good tools you have.  Until you've applied some creativity they won't usefull.

So, the Silver Bullet should be looked for in the development psychology, not the realm of yet another software-tools-that-solves-all-your-development-troubles.

Yes, I'm an interested party here.  I did my research and practice that has its way to world in "Software Development Basics", started with &lt;a href="http://www.kds.com.ua/wp/2006/12/13/well-formed-outcome/" rel="nofollow"&gt;Well Formed Outcome&lt;/a&gt; and little note regarding &lt;a href="http://www.kds.com.ua/wp/2006/12/20/decomposition/" rel="nofollow"&gt;Decomposition&lt;/a&gt;.
</description>
		<content:encoded><![CDATA[<p>You write:</p>
<blockquote><p>I recently read Frederick P. Brooks, Jr.&#8217;s essay No Silver Bullet: Essence and Accidents of Software Engineering. Brooks wrote this paper 20 years ago and it still rings true today. I like the whole essay and encourage you to read it if you haven&#8217;t already.</p>
<p>Brooks is an oft quoted writer. I&#8217;m going to indulge in the practice by pointing out a few things from this essay that I think will always be true.</p>
<blockquote><p> Likewise, a scaling-up of a software entity is not merely a repetition of the same elements in larger sizes, it is necessarily an increase in the number of different elements. In most cases, the elements interact with each other in some nonlinear fashion, and the complexity of the whole increases much more than linearly.</p>
<p>The complexity of software is an essential property, not an accidental one. Hence, descriptions of a software entity that abstract away its complexity often abstract away its essence.
</p></blockquote>
</blockquote>
<p>The Silver Bullet is considered yet unknown just because people look for it in wrong place.</p>
<p>See, Brooks himself says</p>
<blockquote><p>
In many cases, the software must conform because it is the most recent arrival on the scene. In others, it must conform because it is perceived as the most conformable. But in all cases, much complexity comes from conformation to other interfaces; this complexity cannot be simplified out by any redesign of the software alone.
</p></blockquote>
<p>In other words, software is complex just because the surrounding world is complex.</p>
<p>So, how someone may dare to conquer the complex world with pure boolean logic and turing automata alone?</p>
<p>Since software reflects the world, I may bring an analogy between writing a software and doing a scientific research.</p>
<p>Any decent scientist will tell you that logic is not his close friend when he makes a breakthrough.  He uses logic to <em>prove</em> that his idea will work (or won&#8217;t work).  He uses it to plan experiments, write reports and grant proposals (err&#8230; the last one isn&#8217;t logic).</p>
<p>Looking back at a software, no matter what good tools you have.  Until you&#8217;ve applied some creativity they won&#8217;t usefull.</p>
<p>So, the Silver Bullet should be looked for in the development psychology, not the realm of yet another software-tools-that-solves-all-your-development-troubles.</p>
<p>Yes, I&#8217;m an interested party here.  I did my research and practice that has its way to world in &#8220;Software Development Basics&#8221;, started with <a href="http://www.kds.com.ua/wp/2006/12/13/well-formed-outcome/" rel="nofollow">Well Formed Outcome</a> and little note regarding <a href="http://www.kds.com.ua/wp/2006/12/20/decomposition/" rel="nofollow">Decomposition</a>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
