<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Endeavour &#187; Creativity</title>
	<atom:link href="http://www.johndcook.com/blog/category/creativity/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.johndcook.com/blog</link>
	<description>The blog of John D. Cook</description>
	<lastBuildDate>Thu, 09 Feb 2012 20:24:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Limiting your options leads to better options</title>
		<link>http://www.johndcook.com/blog/2012/02/03/limiting-your-options-creates-better-options/</link>
		<comments>http://www.johndcook.com/blog/2012/02/03/limiting-your-options-creates-better-options/#comments</comments>
		<pubDate>Fri, 03 Feb 2012 13:10:58 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=10591</guid>
		<description><![CDATA[Limiting your options leads to better options.
… when you study the evidence, it’s clear that you’re not likely to encounter real interesting opportunities in your life until after you’re really good at something.
If you avoid focus because you want to keep your options open, you’re likely accomplishing the opposite. Getting good is a prerequisite to [...]]]></description>
			<content:encoded><![CDATA[<p>Limiting your options leads to better options.</p>
<blockquote><p>… when you study the evidence, it’s clear that you’re not likely to encounter real interesting opportunities in your life until after you’re really good at something.</p>
<p>If you avoid focus because you want to keep your options open, you’re likely accomplishing the opposite. Getting good is a prerequisite to encountering options worth pursuing.</p></blockquote>
<p>From <a href="http://calnewport.com/blog/2012/01/29/closing-your-interests-opens-more-interesting-opportunities-the-power-of-diligence-in-creating-a-remarkable-life/">Closing your interests opens more interesting opportunities</a>.</p>
<p><strong>Related post</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2011/10/05/demonstrating-persistence/">Demonstrating persistence</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2012/02/03/limiting-your-options-creates-better-options/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Rule of the last inch</title>
		<link>http://www.johndcook.com/blog/2012/01/30/rule-of-the-last-inch/</link>
		<comments>http://www.johndcook.com/blog/2012/01/30/rule-of-the-last-inch/#comments</comments>
		<pubDate>Mon, 30 Jan 2012 14:55:00 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=10558</guid>
		<description><![CDATA[From The First Circle by Alexander Solzhenitsyn:
Now listen to the rule of the last inch. The realm of the last inch. The job is almost finished, the goal almost attained, everything possible  seems to have been achieved, every difficulty overcome — and yet the quality is just not there. The work needs more finish, [...]]]></description>
			<content:encoded><![CDATA[<p>From <a href="http://www.amazon.com/gp/product/0061479012/ref=as_li_ss_tl?ie=UTF8&amp;tag=theende-20&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=0061479012">The First Circle</a> by Alexander Solzhenitsyn:</p>
<blockquote><p>Now listen to the rule of the last inch. The realm of the last inch. The job is almost finished, the goal almost attained, everything possible  seems to have been achieved, every difficulty overcome — and yet the quality is just not there. The work needs more finish, perhaps further research. In that moment of weariness and self-satisfaction, the temptation is greatest to give up, not to strive for the peak of quality. That&#8217;s the realm of the last inch — here, the work is very, very complex, but it&#8217;s also particularly valuable because it&#8217;s done with the most perfect means. The rule of the last inch is simply this — not to leave it undone. And not to put it off — because otherwise your mind loses touch with that realm. And not to mind how much time you spend on it, because the aim is not to finish the job quickly, but to reach perfection.</p></blockquote>
<p>Via <a href="http://sue-still-i-am-one.blogspot.com/2012/01/rule-of-last-inch.html">Still I Am One</a></p>
<p>It can be hard to know when something deserves the kind of polish Solzhenitsyn talks about. Sometimes you&#8217;re in the realm of rapidly diminishing return and it&#8217;s time to move on. Other times, the finishing touches are everything.</p>
<p><strong>Related post</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2011/04/29/scripting-and-the-last-mile-problem/">Scripting and the last mile problem</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2012/01/30/rule-of-the-last-inch/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Customizing conventional wisdom</title>
		<link>http://www.johndcook.com/blog/2012/01/11/customizing-conventional-wisdom/</link>
		<comments>http://www.johndcook.com/blog/2012/01/11/customizing-conventional-wisdom/#comments</comments>
		<pubDate>Wed, 11 Jan 2012 14:34:45 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>
		<category><![CDATA[Scalability]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=10418</guid>
		<description><![CDATA[From Solitude and Leadership by William Deresiewicz:
I find for myself that my first thought is never my best thought. My  first thought is always someone else’s; it’s always what I’ve already  heard about the subject, always the conventional wisdom. It’s only by  concentrating, sticking to the question, being patient, letting all the [...]]]></description>
			<content:encoded><![CDATA[<p>From <a href="http://theamericanscholar.org/solitude-and-leadership/">Solitude and Leadership</a> by William Deresiewicz:</p>
<blockquote><p>I find for myself that my first thought is never my best thought. My  first thought is always someone else’s; it’s always what I’ve already  heard about the subject, always the conventional wisdom. It’s only by  concentrating, sticking to the question, being patient, letting all the  parts of my mind come into play, that I arrive at an original idea. By  giving my brain a chance to make associations, draw connections, take me  by surprise. And often even that idea doesn’t turn out to be very good.  I need time to think about it, too, to make mistakes and recognize  them, to make false starts and correct them, to outlast my impulses, to  defeat my desire to declare the job done and move on to the next thing.</p></blockquote>
<p>Conventional wisdom summarizes the experience of many people. As a result, it&#8217;s often a good starting point. But like a blurred photo, it has gone through a sort of averaging process, loosing resolution along the way. It takes hard work to decide how, or even whether, conventional wisdom applies to your particular circumstances.</p>
<p>Bureaucracies are infuriating because they cannot <a href="http://www.johndcook.com/blog/2011/01/18/hanlons-razor-and-corporations/">deliberate on particulars</a> the way Deresiewicz recommends. In order to <a href="http://www.johndcook.com/blog/2010/07/19/stupidity-scales/">scale up</a>, they develop procedures that work well under common scenarios.</p>
<p>The context of Deresiewicz&#8217;s advice is a speech he gave at West Point. His audience will spend their careers in one of the largest and most bureaucratic organizations in the world. Deresiewicz is aware of this irony and gives advice for how to be a deep thinker while working within a bureaucracy.</p>
<p><strong>Related posts</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2010/08/15/john-cleese-on-creativity/">John Cleese on creativity</a><br />
<a href="http://www.johndcook.com/blog/2011/09/13/advanced-or-just-obscure/">Advanced or just obscure?</a><br />
<a href="http://www.johndcook.com/blog/2010/05/20/in-defense-of-reinventing-wheels/">In defense of reinventing wheels</a><br />
<a href="http://www.johndcook.com/blog/2011/08/11/small-local-old-particular/">Small, local, old, and particular</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2012/01/11/customizing-conventional-wisdom/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to know it all</title>
		<link>http://www.johndcook.com/blog/2011/12/19/how-to-know-it-all/</link>
		<comments>http://www.johndcook.com/blog/2011/12/19/how-to-know-it-all/#comments</comments>
		<pubDate>Mon, 19 Dec 2011 15:08:43 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>
		<category><![CDATA[Math]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=10254</guid>
		<description><![CDATA[The way to know it all is to change the definition of &#8220;all.&#8221; Schools do this, for example, by defining &#8220;all&#8221; to mean everything on a test. Then it&#8217;s possible for someone to know it all. Schools create the illusion that the world is finite. You may not know everything, but someone does.
The desire to [...]]]></description>
			<content:encoded><![CDATA[<p>The way to know it all is to change the definition of &#8220;all.&#8221; Schools do this, for example, by defining &#8220;all&#8221; to mean everything on a test. Then it&#8217;s possible for someone to know it all. Schools create the illusion that the world is finite. You may not know everything, but someone does.</p>
<p>The desire to know it all is pernicious. The only way to accomplish it is to shrink your world. That may be OK for a while to focus your attention. The danger is that you can succeed and forget that you started by drawing arbitrary boundaries.</p>
<p>When I was very young, I thought that if I read every volume of the World Book Encyclopedia, I&#8217;d know everything. Of course I wouldn&#8217;t know everything, only what the editors of the encyclopedia chose to include.</p>
<p>If you want to learn English by first learning all the vocabulary, you&#8217;ll never speak English. Even if you learn every word in a particular dictionary, you still haven&#8217;t learned every word in the language.</p>
<p>Computer languages are orders of magnitude simpler than human languages, but they&#8217;re still too complex to learn exhaustively. If you want to learn every nuance of C++ before writing programs, you&#8217;ll never write a program. And if you think this is because C++ is a large language, it&#8217;s hardly possible to understand C exhaustively either if you take into account all the subtleties of how features are actually implemented on various platforms.</p>
<p>A common problem in math is how to select a finite sample from an infinite space. Maybe you have a function defined at an infinite number of points and you want to approximate it by sampling it at a carefully chosen finite set of points. This is a good metaphor for life.</p>
<p>Even when things are finite, it&#8217;s often very practical to think of them as being infinite. (See <a href="http://www.johndcook.com/blog/2010/09/09/infinite-is-easier-than-big/">Infinite is easier than big</a>.) Many aspects of life are effectively infinite.</p>
<p><strong>Related post</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2009/03/03/evaluate-people-at-their-best/">Evaluate people at their best or at their worst?</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2011/12/19/how-to-know-it-all/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Avoidance of distraction</title>
		<link>http://www.johndcook.com/blog/2011/12/08/avoidance-of-distraction/</link>
		<comments>http://www.johndcook.com/blog/2011/12/08/avoidance-of-distraction/#comments</comments>
		<pubDate>Fri, 09 Dec 2011 04:12:17 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>
		<category><![CDATA[Productivity]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=10171</guid>
		<description><![CDATA[My previous post gave examples of how David Souter and Donald Knuth chose not to use some common technologies. John Venier left an insightful comment.
I think the avoidance of technology in these cases is really an  avoidance of distraction.  These same fellows would probably not keep a  parrot in their office if [...]]]></description>
			<content:encoded><![CDATA[<p>My <a href="http://www.johndcook.com/blog/2011/12/08/selective-use-of-technology-2/">previous post</a> gave examples of how David Souter and Donald Knuth chose not to use some common technologies. John Venier left an insightful comment.</p>
<blockquote><p>I think the avoidance of technology in these cases is really an  avoidance of distraction.  These same fellows would probably not keep a  parrot in their office if it screeched every couple of minutes,  regardless of their affinity for birds.</p></blockquote>
<p>I believe he&#8217;s right. My intention was to write more broadly about how tools influence our thinking, but the examples I gave were only about one kind of influence: distraction.</p>
<p><strong>Related posts</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2011/10/04/how-to-neutralize-intelligence/">How to neutralize intelligence</a><br />
<a href="http://www.johndcook.com/blog/2010/09/01/two-kinds-of-multitasking/">Two kinds of multitasking</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2011/12/08/avoidance-of-distraction/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Selective use of technology</title>
		<link>http://www.johndcook.com/blog/2011/12/08/selective-use-of-technology-2/</link>
		<comments>http://www.johndcook.com/blog/2011/12/08/selective-use-of-technology-2/#comments</comments>
		<pubDate>Thu, 08 Dec 2011 13:49:40 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Computing]]></category>
		<category><![CDATA[Creativity]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=10148</guid>
		<description><![CDATA[In his book The Nine, Jeffrey Toobin gives a few details of former Supreme Court Justice David Souter&#8217;s decidedly low-tech life. Souter has no cell phone or voice mail. He does not use email. He was given a television once but never turned it on. He moves his chair around his office throughout the day [...]]]></description>
			<content:encoded><![CDATA[<p>In his book <a href="http://www.amazon.com/gp/product/0385516401?ie=UTF8&amp;tag=theende-20&amp;linkCode=xm2&amp;camp=1789&amp;creativeASIN=0385516401">The Nine</a>, Jeffrey Toobin gives a few details of former Supreme Court Justice David Souter&#8217;s decidedly low-tech life. Souter has no cell phone or voice mail. He does not use email. He was given a television once but never turned it on. He moves his chair around his office throughout the day so he can read by natural light. Toobin says Souter lives something like an eighteenth century gentleman.</p>
<p>I find it interesting that Justice Souter would have such independence of mind that he chooses not to use much of the technology that our world takes for granted. He made it to the top of his profession and had a job for life, so he could afford to be eccentric. But he wasn&#8217;t born on the Supreme Court. I would like to know whether his low-tech work habits developed before or after his legal success.</p>
<p>I imagine most readers of this blog could more easily relate to Donald Knuth than David Souter. Knuth obviously doesn&#8217;t reject technology, but he is selective in how he uses it.</p>
<p>I had the opportunity to see Knuth speak while I was in college. Much to my surprise, his slides were handwritten. The author of TeX didn&#8217;t see the need to use TeX for his slides. While he cares about the <a href="http://www-cs-faculty.stanford.edu/~knuth/cm.html">fine details</a> of how math looks in print, he apparently didn&#8217;t feel it was worth the effort to typeset his notes for an informal presentation.</p>
<p>In 1990 Knuth decided to stop using email.</p>
<blockquote><p>I&#8217;d used email since about 1975, and it seems to me that 15 years of email is plenty for one lifetime. Email is a wonderful thing for people whose role in life is to be on top of things. But not for me; my role is to be on the bottom of things.</p></blockquote>
<p>I believe I&#8217;ve read that Knuth does most of his work on a Linux box with no network connection. He also has a Mac for creating graphics and using the Internet. He has a secretary to handle his correspondence, including email.</p>
<p>If you&#8217;re reading legal briefs by sunlight, your thoughts will not be exactly the same as they would be if you were reading by fluorescent light. If you&#8217;re writing a presentation by hand, you&#8217;re not going to think the same way you would if you were pecking on a computer keyboard. And if you do use a computer, your thinking is subtlety different depending on what program you use. Technology affects the way you think. The effect is not uniformly better or worse, but it is certainly real.</p>
<p><strong>Related posts</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2009/06/11/create-offline-analyze-online/">Create offline, analyze online</a><br />
<a href="http://www.johndcook.com/blog/2009/04/21/tim-brays-high-tech-monastic-cell/">Tim Bray’s high-tech monastic cell</a><br />
<a href="http://www.johndcook.com/blog/2009/04/02/living-within-chosen-limits/">Living within chosen limits</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2011/12/08/selective-use-of-technology-2/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
		<item>
		<title>An array of hammers</title>
		<link>http://www.johndcook.com/blog/2011/12/02/an-array-of-hammers/</link>
		<comments>http://www.johndcook.com/blog/2011/12/02/an-array-of-hammers/#comments</comments>
		<pubDate>Fri, 02 Dec 2011 10:02:02 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=10124</guid>
		<description><![CDATA[In a comment on the previous post, vonjd brought up the famous quote from Abraham Maslow:
It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail.
Sometimes you don&#8217;t just have a hammer, you have an array of hammers. You have rock hammers, claw hammers, and [...]]]></description>
			<content:encoded><![CDATA[<p>In a comment on the <a href="http://www.johndcook.com/blog/2011/12/01/amputating-reality/">previous post</a>, vonjd brought up the famous quote from Abraham Maslow:</p>
<blockquote><p>It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail.</p></blockquote>
<p>Sometimes you don&#8217;t just have a hammer, you have an array of hammers. You have rock hammers, claw hammers, and sledge hammers, all in numerous sizes. You have a variety of wooden and rubber mallets too. You&#8217;ve even got a gavel. Because you have such an impressive collection of specialized hammers, you think you&#8217;re broad in your problem solving, but your basic instinct is still only to beat on things.</p>
<p>Related posts:</p>
<p><a href="http://www.johndcook.com/blog/2009/12/16/good-work-with-bad-tools/">Doing good work with bad tools</a><br />
<a href="http://www.johndcook.com/blog/2011/09/30/just-an-approximation/">Just an approximation</a><br />
<a href="http://www.johndcook.com/blog/2009/03/24/redbelt-problem-solving/">Redbelt problem solving</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2011/12/02/an-array-of-hammers/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Better mousetraps</title>
		<link>http://www.johndcook.com/blog/2011/11/30/better-mousetraps/</link>
		<comments>http://www.johndcook.com/blog/2011/11/30/better-mousetraps/#comments</comments>
		<pubDate>Wed, 30 Nov 2011 16:00:25 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=9029</guid>
		<description><![CDATA[From Ike Pigott:
Build a better mousetrap, and cats will beat a path to your door to picket.
Related post:
It takes more than a better mousetrap
]]></description>
			<content:encoded><![CDATA[<p>From <a href="http://twitter.com/#!/ikepigott/status/96601425051795457">Ike Pigott</a>:</p>
<blockquote><p>Build a better mousetrap, and cats will beat a path to your door to picket.</p></blockquote>
<p><strong>Related post</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2011/06/29/a-better-mouse-trap/">It takes more than a better mousetrap</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2011/11/30/better-mousetraps/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>John Coltrane versus Kenny G</title>
		<link>http://www.johndcook.com/blog/2011/11/20/john-coltrane-versus-kenny-g/</link>
		<comments>http://www.johndcook.com/blog/2011/11/20/john-coltrane-versus-kenny-g/#comments</comments>
		<pubDate>Sun, 20 Nov 2011 23:13:16 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>
		<category><![CDATA[Music]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=10011</guid>
		<description><![CDATA[My previous post began with a story about a performance by John Coltrane. Douglas Groothuis left a comment saying that he used the same story in his book Truth Decay. Before telling the Coltrane story, Groothuis compares the philosophies of Kenny G and John Coltrane.
Kenny G&#8217;s philosophy is as shallow as his music.
I just play [...]]]></description>
			<content:encoded><![CDATA[<p>My <a href="http://www.johndcook.com/blog/2011/11/19/nunc-dimittis/">previous post</a> began with a story about a performance by John Coltrane. Douglas Groothuis left a comment saying that he used the same story in his book <a href="http://www.amazon.com/gp/product/0830822283/ref=as_li_ss_tl?ie=UTF8&amp;tag=theende-20&amp;linkCode=as2&amp;camp=217145&amp;creative=399369&amp;creativeASIN=0830822283">Truth Decay</a>. Before telling the Coltrane story, Groothuis compares the philosophies of Kenny G and John Coltrane.</p>
<p>Kenny G&#8217;s philosophy is as shallow as his music.</p>
<blockquote><p>I just play for myself, the way I want to play, and it comes out sounding like me.</p></blockquote>
<p>Coltrane&#8217;s philosophy, like his music, is more ambitious.</p>
<blockquote><p>Overall, I think the main thing a musician would like to do is give a picture to the listener of the many wonderful things he knows and senses in the universe. That&#8217;s what music is to me — it&#8217;s just another way of saying this is a big, wonderful universe we live in, that&#8217;s been given to us, and here&#8217;s an example of just how magnificent and encompassing it is. That&#8217;s what I would like to do. I think that&#8217;s one of the greatest things you can do in life, and we all try to do it in some way. The musician&#8217;s is through his music.</p></blockquote>
<p>As Groothuis comments, Kenny G only spoke of expressing <em>himself</em>, while Coltrane &#8220;expressed a yearning to represent objective realities musically.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2011/11/20/john-coltrane-versus-kenny-g/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>Productivity and negative space</title>
		<link>http://www.johndcook.com/blog/2011/11/16/productivity-and-negative-space/</link>
		<comments>http://www.johndcook.com/blog/2011/11/16/productivity-and-negative-space/#comments</comments>
		<pubDate>Wed, 16 Nov 2011 18:58:43 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>
		<category><![CDATA[Productivity]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=9970</guid>
		<description><![CDATA[My post Why programmers are not paid in proportion to their productivity has been getting a lot of buzz today. One of the arguments in that post is that the most productive programmers know where they can find software to do parts of their job. When they reuse existing code rather than writing their own [...]]]></description>
			<content:encoded><![CDATA[<p>My post <a href="http://www.johndcook.com/blog/2009/12/23/why-programmers-are-not-paid-in-proportion-to-their-productivity">Why programmers are not paid in proportion to their productivity</a> has been getting a lot of buzz today. One of the arguments in that post is that the most productive programmers know where they can find software to do parts of their job. When they reuse existing code rather than writing their own from scratch, nobody notices. They probably don&#8217;t even notice themselves, at least not often.</p>
<p>The work you don&#8217;t do is a sort of negative space, like the shape formed by the empty space in a painting or the silence in a piece of music. It&#8217;s hard to appreciate what&#8217;s not there. It&#8217;s hard for a business to reward the unnecessary work that someone avoids doing.</p>
<p>Venkatesh Rao has a different take on what makes some people far more effective than others. In his post <a href="http://www.tempobook.com/2011/10/25/thrust-drag-and-the-10x-effect/">Thrust, Drag, and the 10x Effect</a>, he says that the people who are 10x more productive are the those who allocate large, uninterrupted blocks of time to work on difficult creative tasks.</p>
<p>Rao&#8217;s observation would also help explain why super programmers do not earn super wages, and it ties into the idea of negative space. People who fracture their time putting out fires seem more productive, or at least more responsive, than the people who block out time to think. It&#8217;s harder to notice someone <em>not</em> being frantic. Thinkers don&#8217;t fare well in environments that reward activity more than accomplishment.</p>
<p><strong>Related post</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2008/12/23/negative-space-operating-systems/">Negative space in operating systems</a><br />
<a href="http://www.johndcook.com/blog/2009/11/22/the-computer-guy/">It doesn&#8217;t pay to be the computer guy</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2011/11/16/productivity-and-negative-space/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>How to neutralize intelligence</title>
		<link>http://www.johndcook.com/blog/2011/10/04/how-to-neutralize-intelligence/</link>
		<comments>http://www.johndcook.com/blog/2011/10/04/how-to-neutralize-intelligence/#comments</comments>
		<pubDate>Tue, 04 Oct 2011 12:00:58 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>
		<category><![CDATA[Productivity]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=9564</guid>
		<description><![CDATA[Kurt Vonnegut&#8217;s short story Harrison Bergeron begins &#8220;The year was 2081, and everybody was finally equal.&#8221; Beautiful people are required to wear ugly masks, strong people are required to carry weights, etc. Every excellence is handicapped.
But how do you handicap intelligence? With interruptions. In Vonnegut&#8217;s story, those deemed too intelligent are required to wear a [...]]]></description>
			<content:encoded><![CDATA[<p>Kurt Vonnegut&#8217;s short story <a href="http://www.nationalreview.com/nroriginals/?q=MDllNmVmNGU1NDVjY2IzODBlMjYzNDljZTMzNzFlZjc=">Harrison Bergeron</a> begins &#8220;The year was 2081, and everybody was finally equal.&#8221; Beautiful people are required to wear ugly masks, strong people are required to carry weights, etc. Every excellence is handicapped.</p>
<p>But how do you handicap intelligence? With interruptions. In Vonnegut&#8217;s story, those deemed too intelligent are required to wear a device in their ear that regularly interrupts their thoughts with a loud noise.</p>
<p><strong>Related posts</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2008/02/04/rethinking-interruptions/">Rethinking interruptions</a><br />
<a href="http://www.johndcook.com/blog/2009/12/26/multitasking/">Multitasking makes us shallow</a><br />
<a href="http://www.johndcook.com/blog/2010/09/01/two-kinds-of-multitasking/">Two kinds of multitasking</a><br />
<a href="http://www.johndcook.com/blog/2010/09/09/screwtape-on-music-and-silence/">Screwtape on music and silence</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2011/10/04/how-to-neutralize-intelligence/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Odd little bookshops</title>
		<link>http://www.johndcook.com/blog/2011/08/17/odd-little-bookshops/</link>
		<comments>http://www.johndcook.com/blog/2011/08/17/odd-little-bookshops/#comments</comments>
		<pubDate>Wed, 17 Aug 2011 09:38:38 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>
		<category><![CDATA[Books]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=9152</guid>
		<description><![CDATA[From Tristan Gylberd:
The smaller, the odder, the more out of the way, and the more specialized, the better. That is my philosophy on bookshops. Come to think of it, that is my philosophy on everything else too — it makes for a very interesting life unconstrained by the smothering expectations of the tyranny of fashion [...]]]></description>
			<content:encoded><![CDATA[<p>From Tristan Gylberd:</p>
<blockquote><p>The smaller, the odder, the more out of the way, and the more specialized, the better. That is my philosophy on bookshops. Come to think of it, that is my philosophy on everything else too — it makes for a very interesting life unconstrained by the smothering expectations of the tyranny of fashion or popularity.</p></blockquote>
<p><strong>Related post</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2011/08/11/small-local-old-particular/">Small, local, old, and particular</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2011/08/17/odd-little-bookshops/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>On being wrong</title>
		<link>http://www.johndcook.com/blog/2011/08/03/on-being-wrong/</link>
		<comments>http://www.johndcook.com/blog/2011/08/03/on-being-wrong/#comments</comments>
		<pubDate>Thu, 04 Aug 2011 02:54:46 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=9081</guid>
		<description><![CDATA[TED Talk by &#8220;Wrongologist&#8221; Kathryn Schulz:

It could be depressing to be reminded that you&#8217;re probably wrong about many things you believe. But I thought about a number of things I&#8217;d like to find out I&#8217;m wrong about, and maybe I am wrong about at least one of them.  
Related posts:
Peripeteia
Statisticians take themselves too seriously
]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.ted.com/talks/lang/eng/kathryn_schulz_on_being_wrong.html">TED Talk</a> by &#8220;Wrongologist&#8221; Kathryn Schulz:</p>
<p><!--copy and paste--><object width="450" height="320"><param name="movie" value="http://video.ted.com/assets/player/swf/EmbedPlayer.swf"></param><param name="allowFullScreen" value="true" /><param name="allowScriptAccess" value="always"/><param name="wmode" value="transparent"></param><param name="bgColor" value="#ffffff"></param><param name="flashvars" value="vu=http://video.ted.com/talk/stream/2011/Blank/KathrynSchulz_2011-320k.mp4&#038;su=http://images.ted.com/images/ted/tedindex/embed-posters/KathrynSchulz-2011.embed_thumbnail.jpg&#038;vw=512&#038;vh=288&#038;ap=0&#038;ti=1126&#038;lang=eng&#038;introDuration=15330&#038;adDuration=4000&#038;postAdDuration=830&#038;adKeys=talk=kathryn_schulz_on_being_wrong;year=2011;theme=new_on_ted_com;theme=how_the_mind_works;theme=a_taste_of_ted2011;theme=master_storytellers;event=TED2011;tag=Culture;tag=failure;&#038;preAdTag=tconf.ted/embed;tile=1;sz=512x288;" /><embed src="http://video.ted.com/assets/player/swf/EmbedPlayer.swf" pluginspace="http://www.macromedia.com/go/getflashplayer" type="application/x-shockwave-flash" wmode="transparent" bgColor="#ffffff" width="450" height="320" allowFullScreen="true" allowScriptAccess="always" flashvars="vu=http://video.ted.com/talk/stream/2011/Blank/KathrynSchulz_2011-320k.mp4&#038;su=http://images.ted.com/images/ted/tedindex/embed-posters/KathrynSchulz-2011.embed_thumbnail.jpg&#038;vw=512&#038;vh=288&#038;ap=0&#038;ti=1126&#038;lang=eng&#038;introDuration=15330&#038;adDuration=4000&#038;postAdDuration=830&#038;adKeys=talk=kathryn_schulz_on_being_wrong;year=2011;theme=new_on_ted_com;theme=how_the_mind_works;theme=a_taste_of_ted2011;theme=master_storytellers;event=TED2011;tag=Culture;tag=failure;&#038;preAdTag=tconf.ted/embed;tile=1;sz=512x288;"></embed></object></p>
<p>It could be depressing to be reminded that you&#8217;re probably wrong about many things you believe. But I thought about a number of things I&#8217;d like to find out I&#8217;m wrong about, and maybe I am wrong about at least one of them.  </p>
<p><strong>Related posts</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2010/07/16/peripeteia/">Peripeteia</a><br />
<a href="http://www.johndcook.com/blog/2010/01/28/statisticians-take-themselves-too-seriously/">Statisticians take themselves too seriously</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2011/08/03/on-being-wrong/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Write the other way</title>
		<link>http://www.johndcook.com/blog/2011/06/16/write-the-other-way/</link>
		<comments>http://www.johndcook.com/blog/2011/06/16/write-the-other-way/#comments</comments>
		<pubDate>Thu, 16 Jun 2011 14:46:38 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=8735</guid>
		<description><![CDATA[This notebook made me think of the quote from William Carlos Williams:
&#8220;If they give you lined paper, write the other way.&#8221;

]]></description>
			<content:encoded><![CDATA[<p>This <a href="http://www.tmsprl.com/shop.html">notebook</a> made me think of the quote from William Carlos Williams:</p>
<p>&#8220;If they give you lined paper, write the other way.&#8221;</p>
<p style="text-align:center"><a href="http://www.tmsprl.com/shop.html"><img src="http://www.johndcook.com/notebook.jpg" alt="" width="450" height="311" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2011/06/16/write-the-other-way/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Have you saved a milliwatt today?</title>
		<link>http://www.johndcook.com/blog/2011/06/13/have-you-saved-a-milliwatt-today/</link>
		<comments>http://www.johndcook.com/blog/2011/06/13/have-you-saved-a-milliwatt-today/#comments</comments>
		<pubDate>Mon, 13 Jun 2011 14:41:30 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=8696</guid>
		<description><![CDATA[Research In Motion (RIM) is best known for making the BlackBerry. In the early days of the company, RIM focused on reducing the BlackBerry&#8217;s power consumption. The engineers put up a sign:
Have you saved a milliwatt today?
This was a specific, reasonable challenge. Instead of some nebulous exhortation to corporate greatness, something worthy of a Dilbert [...]]]></description>
			<content:encoded><![CDATA[<p>Research In Motion (RIM) is best known for making the BlackBerry. In the early days of the company, RIM focused on reducing the BlackBerry&#8217;s power consumption. The engineers put up a sign:</p>
<blockquote><p>Have you saved a milliwatt today?</p></blockquote>
<p>This was a specific, reasonable challenge. Instead of some nebulous exhortation to corporate greatness, something worthy of a Dilbert cartoon, they asked engineers to reduce power consumption by a milliwatt.</p>
<p>What&#8217;s your equivalent of saving a milliwatt?</p>
<p><strong>Related post</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2009/02/12/originality/">Don&#8217;t try to be God, try to be Shakespeare</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2011/06/13/have-you-saved-a-milliwatt-today/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Theory and practice</title>
		<link>http://www.johndcook.com/blog/2011/05/13/theory-and-practice/</link>
		<comments>http://www.johndcook.com/blog/2011/05/13/theory-and-practice/#comments</comments>
		<pubDate>Fri, 13 May 2011 12:18:28 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>
		<category><![CDATA[Science]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=8517</guid>
		<description><![CDATA[Donald Knuth explains how he combines theory and practice:
This has always been the main credo of my professional life. I have always tried to develop theories that shed light on the practical things I do, and I&#8217;ve always tried to do a variety of practical things so that I have a better chance of discovering [...]]]></description>
			<content:encoded><![CDATA[<p>Donald Knuth explains how he combines theory and practice:</p>
<blockquote><p>This has always been the main credo of my professional life. I have always tried to develop theories that shed light on the practical things I do, and I&#8217;ve always tried to do a variety of practical things so that I have a better chance of discovering rich and interesting theories. It seems to me that my chosen field, computer science — information processing — is a field where theory and practice come together more than in any other discipline, because of the nature of computing machines. …</p>
<p>History teaches us that the greatest mathematicians of past centuries combined theory and practice in their own careers. …</p>
<p>The best theory is inspired by practice. The best practice is inspired by theory.</p></blockquote>
<p>Taken from <a href="http://www.amazon.com/gp/product/1881526917/ref=as_li_ss_tl?ie=UTF8&amp;tag=theende-20&amp;linkCode=as2&amp;camp=217145&amp;creative=399349&amp;creativeASIN=1881526917">Selected Papers on Computer Science</a>.</p>
<p><a href="http://www.amazon.com/gp/product/1881526917/ref=as_li_ss_il?ie=UTF8&amp;tag=theende-20&amp;linkCode=as2&amp;camp=217145&amp;creative=399349&amp;creativeASIN=1881526917"><img src="http://ws.assoc-amazon.com/widgets/q?_encoding=UTF8&amp;Format=_SL160_&amp;ASIN=1881526917&amp;MarketPlace=US&amp;ID=AsinImage&amp;WS=1&amp;tag=theende-20&amp;ServiceVersion=20070822" border="0" alt="" /></a><img style="border:none !important; margin:0px !important;" src="http://www.assoc-amazon.com/e/ir?t=&amp;l=as2&amp;o=1&amp;a=1881526917&amp;camp=217145&amp;creative=399349" border="0" alt="" width="1" height="1" /></p>
<p><strong>Related post</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2008/08/12/works-in-the-field-not-in-the-lab/">Works in the field, not in the lab</a><br />
<a href="http://www.johndcook.com/blog/2011/05/10/well-understood/">Works well versus well understood</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2011/05/13/theory-and-practice/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Third-system effect</title>
		<link>http://www.johndcook.com/blog/2011/04/18/third-system-effect/</link>
		<comments>http://www.johndcook.com/blog/2011/04/18/third-system-effect/#comments</comments>
		<pubDate>Mon, 18 Apr 2011 13:04:33 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>
		<category><![CDATA[Software development]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Simplicity]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=8335</guid>
		<description><![CDATA[The third-system effect describes a simple system rising like a phoenix out of the ashes of a system that collapsed under its own complexity.
A notorious &#8217;second-system effect&#8217; often afflicts the successors of small experimental prototypes. The urge to add everything that was left out the first time around all too frequently leads to huge and [...]]]></description>
			<content:encoded><![CDATA[<p>The third-system effect describes a simple system rising like a phoenix out of the ashes of a system that collapsed under its own complexity.</p>
<blockquote><p>A notorious &#8217;second-system effect&#8217; often afflicts the successors of small experimental prototypes. The urge to add everything that was left out the first time around all too frequently leads to huge and overcomplicated design. Less well known, because less common, is the &#8216;third-system effect&#8217;: sometimes, after the second system has collapsed of its own weight, there is a chance to go back to simplicity and get it right.</p></blockquote>
<p>From <a href="http://www.amazon.com/gp/product/0131429019/ref=as_li_ss_tl?ie=UTF8&amp;tag=theende-20&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=0131429019">The Art of Unix Programming</a> by Eric S. Raymond. Available online <a href="http://www.catb.org/~esr/writings/taoup/html/">here</a>.</p>
<p>Raymond says that Unix was such a third system. What are other examples of the third-system effect?</p>
<p><strong>Related posts</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2008/10/15/simple-legacy/">Simple legacy</a><br />
<a href="http://www.johndcook.com/blog/2010/06/30/where-the-unix-philosophy-breaks-down/">Where the Unix philosophy breaks down</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2011/04/18/third-system-effect/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Forced to be simple</title>
		<link>http://www.johndcook.com/blog/2011/04/08/forced-to-be-simple/</link>
		<comments>http://www.johndcook.com/blog/2011/04/08/forced-to-be-simple/#comments</comments>
		<pubDate>Fri, 08 Apr 2011 14:40:28 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>
		<category><![CDATA[Quotes]]></category>
		<category><![CDATA[Simplicity]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=8224</guid>
		<description><![CDATA[From Paul Graham:
When you&#8217;re forced to be simple, you&#8217;re forced to face the real problem. When you can&#8217;t deliver ornament, you have to deliver substance.
Related posts:
Confusing familiar with simple
Rewarding complexity
A little simplicity goes a long way
]]></description>
			<content:encoded><![CDATA[<p>From Paul Graham:</p>
<blockquote><p>When you&#8217;re forced to be simple, you&#8217;re forced to face the real problem. When you can&#8217;t deliver ornament, you have to deliver substance.</p></blockquote>
<p><strong>Related posts</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2010/03/25/confusing-familiar-with-simple/">Confusing familiar with simple</a><br />
<a href="http://www.johndcook.com/blog/2010/04/05/rewarding-complexity/">Rewarding complexity</a><br />
<a href="http://www.johndcook.com/blog/2008/04/09/a-little-simplicity-goes-a-long-way/">A little simplicity goes a long way</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2011/04/08/forced-to-be-simple/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Priorities</title>
		<link>http://www.johndcook.com/blog/2011/03/25/priorities/</link>
		<comments>http://www.johndcook.com/blog/2011/03/25/priorities/#comments</comments>
		<pubDate>Fri, 25 Mar 2011 11:02:24 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[Creativity]]></category>
		<category><![CDATA[Productivity]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=8146</guid>
		<description><![CDATA[From Merlin Mann:
If you&#8217;ve got more than two priorities, you might as well think you have more than two arms.
Related posts:
Task switching
Four reasons we don&#8217;t apply the 80/20 rule
]]></description>
			<content:encoded><![CDATA[<p>From Merlin Mann:</p>
<blockquote><p>If you&#8217;ve got more than two priorities, you might as well think you have more than two arms.</p></blockquote>
<p><strong>Related posts</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2008/02/02/task-switching/">Task switching</a><br />
<a href="http://www.johndcook.com/blog/2009/02/03/obstacles-to-applying-pareto-rule/">Four reasons we don&#8217;t apply the 80/20 rule</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2011/03/25/priorities/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Appropriate scale</title>
		<link>http://www.johndcook.com/blog/2011/03/23/appropriate-scale/</link>
		<comments>http://www.johndcook.com/blog/2011/03/23/appropriate-scale/#comments</comments>
		<pubDate>Wed, 23 Mar 2011 13:32:50 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>
		<category><![CDATA[Software development]]></category>
		<category><![CDATA[Minimalism]]></category>
		<category><![CDATA[Productivity]]></category>
		<category><![CDATA[Scalability]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=8125</guid>
		<description><![CDATA[&#8220;Scale&#8221; became a popular buzz word a couple decades ago. Suddenly everyone was talking about how things scale. At first the term was used to describe how software behaved as problems became larger or smaller. Then the term became more widely used to describe how businesses and other things handle growth.
Now when people say something [...]]]></description>
			<content:encoded><![CDATA[<p>&#8220;Scale&#8221; became a popular buzz word a couple decades ago. Suddenly everyone was talking about how things <em>scale</em>. At first the term was used to describe how software behaved as problems became larger or smaller. Then the term became more widely used to describe how businesses and other things handle growth.</p>
<p>Now when people say something &#8220;won&#8217;t scale&#8221; they mean that it won&#8217;t perform well as things get larger. &#8220;Scale&#8221; most often means &#8220;scale up.&#8221; But years ago the usage was more symmetric. For example, someone might have said that a software package didn&#8217;t scale well because it took too long to solve small problems, too long relative to the problem size. We seldom use &#8220;scale&#8221; to discuss scaling <em>down</em>, except possibly in the context of moving something to smaller electronic devices.</p>
<p>This asymmetric view of scaling can be harmful. For example, little companies model themselves after big companies because they hope to scale (up). But running a small software business, for example, as a Microsoft in miniature is <a href="http://www.johndcook.com/blog/2010/07/19/stupidity-scales/">absurd</a>. A small company&#8217;s procedures might not scale up well, but neither do a large company&#8217;s procedures scale down well.</p>
<p>I&#8217;ve been interested in the idea of <strong>appropriate scale</strong> lately, both professionally and personally.</p>
<p>I&#8217;ve realized that some of the software I&#8217;ve been using scales in a way that I don&#8217;t need it to scale. These applications scale up to handle problems I don&#8217;t have, but they&#8217;re overly complex for addressing the problems I do have. They scale up, but they don&#8217;t scale down. Or maybe they don&#8217;t scale up in the way I need them to.</p>
<p>I&#8217;m learning to make better use of fewer tools. This quote from Hugh MacLeod suggests that other people may come to the same point as they gain experience.</p>
<blockquote><p>Actually, as the artist gets more into her thing, and gets more successful, the number of tools tends to go down.</p></blockquote>
<p>On a more personal level, I think that much frustration in life comes from living at an inappropriate scale. Minimalism is gaining attention because minimalists are saying &#8220;Scale down!&#8221; while the rest of our culture is saying &#8220;Scale up!&#8221; Minimalists provide a valuable counterweight, but they can be a bit <a href="http://www.johndcook.com/blog/2010/08/20/defining-minimalism/">extreme</a>. As Milton Glaser pointed out, <a href="http://www.johndcook.com/blog/2009/12/11/less-isnt-more-just-enough-is-more/">less isn&#8217;t more, just enough is more</a>. Instead of simply scaling up or down, we should find an appropriate scale.</p>
<p>How do you determine an appropriate scale? The following suggestion from <a href="http://circeinstitute.com/blog/wendell-berry-on-ignorance/">Andrew Kern</a> is a good starting point:</p>
<blockquote><p>There is an appropriate scale to every human activity and it is the scale of personal responsibility.</p></blockquote>
<p><strong>Update</strong>: See the follow-up post <a href="http://www.johndcook.com/blog/2011/03/30/arrogant-ignorance/">Arrogant ignorance</a>.</p>
<p><strong>Related posts</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2010/07/19/stupidity-scales/">Stupidity scales</a><br />
<a href="http://www.johndcook.com/blog/2008/01/11/million-dollar-cutoff-for-software-technique/">Million dollar software technique</a><br />
<a href="http://www.johndcook.com/blog/2008/07/16/scaling-the-number-of-projects/">Scaling the number of projects</a><br />
<a href="http://www.johndcook.com/blog/2010/08/20/defining-minimalism/">Defining minimalism</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2011/03/23/appropriate-scale/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Art critics versus artists</title>
		<link>http://www.johndcook.com/blog/2011/02/15/art-critics-versus-artists/</link>
		<comments>http://www.johndcook.com/blog/2011/02/15/art-critics-versus-artists/#comments</comments>
		<pubDate>Tue, 15 Feb 2011 12:55:03 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=7800</guid>
		<description><![CDATA[From Pablo Picasso:
When  art critics get together they talk about Form and Structure and  Meaning. When artists get together they talk about where you can buy  cheap turpentine.

Related posts:
Two videos on craftsmanship
Doing good work with bad tools
]]></description>
			<content:encoded><![CDATA[<p>From Pablo Picasso:</p>
<blockquote><p>When  art critics get together they talk about Form and Structure and  Meaning. When artists get together they talk about where you can buy  cheap turpentine.</p></blockquote>
<p style="text-align:left"><img src="http://www.johndcook.com/picasso.jpeg" alt="Pablo Picasso" width="132" height="184" /></p>
<p><strong>Related posts</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2010/11/19/two-videos-on-craftsmanship/">Two videos on craftsmanship</a><br />
<a href="http://www.johndcook.com/blog/2009/12/16/good-work-with-bad-tools/">Doing good work with bad tools</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2011/02/15/art-critics-versus-artists/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Style and understanding</title>
		<link>http://www.johndcook.com/blog/2011/01/05/style-and-understanding/</link>
		<comments>http://www.johndcook.com/blog/2011/01/05/style-and-understanding/#comments</comments>
		<pubDate>Wed, 05 Jan 2011 23:07:35 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>
		<category><![CDATA[Software development]]></category>
		<category><![CDATA[Programming]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=7135</guid>
		<description><![CDATA[From Let Over Lambda by Doug Hoyte:
Style is necessary only when understanding is missing. A corollary to this is that sometimes the only way to effectively use something you don&#8217;t understand is to copy styles observed elsewhere.
I liked those lines when I first read them. But as I thought about them more, they started to [...]]]></description>
			<content:encoded><![CDATA[<p>From <a href="http://www.amazon.com/gp/product/1435712757?ie=UTF8&amp;tag=theende-20&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=1435712757">Let Over Lambda</a> by Doug Hoyte:</p>
<blockquote><p>Style is necessary only when understanding is missing. A corollary to this is that sometimes the only way to effectively use something you don&#8217;t understand is to copy styles observed elsewhere.</p></blockquote>
<p>I liked those lines when I first read them. But as I thought about them more, they started to sound sophomoric.</p>
<p>In context, Hoyte  is arguing that one should not avoid  advanced programming techniques just because they are not in common use.  Also, I believe he has in mind a single programmer working in  isolation. Hoyte&#8217;s statement is easier to accept within those boundaries than when applied more generally, but even in context there is room to disagree.</p>
<p>Novices may not realize that a style <em>is</em> a style. They may confuse what <em>they</em> find necessary with what <em>is</em> necessary.</p>
<p>But style can be the mark of experts as well as novices. Novices may follow a convention because they know no alternative. Experts may be aware of alternatives and deliberately choose the limitations of the same convention.Experts may see the wisdom in convention, or may see convention as a small price to pay out of consideration for other people.</p>
<p>It&#8217;s not saying much to say style is only necessary &#8220;when understanding is missing.&#8221; Understanding is nearly always missing to some extent on any <a href="http://www.johndcook.com/blog/2010/02/03/little-programs-versus-big-programs/">large project</a>. We hardly ever understand what we&#8217;re doing so thoroughly that we can completely disregard style.</p>
<p><strong>Related posts</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2010/11/11/wizards/">The trouble with wizards</a><br />
<a href="http://www.johndcook.com/blog/2010/11/23/lisp-and-the-anti-lisp/">Lisp and the anti-Lisp</a><br />
<a href="http://www.johndcook.com/blog/2009/02/12/originality/">Don&#8217;t try to be God, try to be Shakespeare</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2011/01/05/style-and-understanding/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Two contrasting articles on minimalism</title>
		<link>http://www.johndcook.com/blog/2011/01/01/periodic-minimalism/</link>
		<comments>http://www.johndcook.com/blog/2011/01/01/periodic-minimalism/#comments</comments>
		<pubDate>Sat, 01 Jan 2011 14:57:02 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>
		<category><![CDATA[Minimalism]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=7455</guid>
		<description><![CDATA[This morning I ran across a couple articles on minimalism:

Minimalism is NOT a viable intellectual strategy (30 Dec 2010)
Minimalism IS a viable long term intellectual strategy (31 Dec 2010)

The former has a sense of humor; the latter does not. The former contains thoughtful criticism; the latter is a knee-jerk reaction. The former makes an interesting [...]]]></description>
			<content:encoded><![CDATA[<p>This morning I ran across a couple articles on minimalism:</p>
<ul>
<li><a href="http://vivekhaldar.tumblr.com/post/2525332092/minimalism-is-not-a-viable-intellectual-strategy">Minimalism is NOT a viable intellectual strategy</a> (30 Dec 2010)</li>
<li><a href="http://kirindave.tumblr.com/post/2544990560/minimalism-works">Minimalism IS a viable long term intellectual strategy</a> (31 Dec 2010)</li>
</ul>
<p>The former has a sense of humor; the latter does not. The former contains thoughtful criticism; the latter is a knee-jerk reaction. The former makes an interesting argument; the latter quibbles about definitions.</p>
<p>The former article is by Vivek Haldar. I cannot tell who wrote the latter.</p>
<p>Here&#8217;s an excerpt from Haldar&#8217;s article:</p>
<blockquote><p>The zenith … is a calm geek, sitting in a bare room with a desk upon which sits only a MacBook Air, his backpack of possessions on one side, the broadband internet cable available but unplugged, fingers ready to type into the empty white screen of a minimalist editor.</p></blockquote>
<p>I think that&#8217;s pretty funny. And I would hope that minimalists would be able to get a chuckle out of it.</p>
<p>But Haldar does not just lampoon hipster minimalism. He argues that you need periods of stimulation and clutter to be creative. He also argues that minimalism has its place.</p>
<blockquote><p>Now I agree with most of the premises of the minimalists … My gripe is with the way they sell it as a <strong>way</strong> of life. It’s much more valuable as a <strong>periodic phase</strong> of life.</p>
<p>Minimalism cannot be a long-term strategy, but it makes an excellent short-term tactic.</p></blockquote>
<p>The second article essentially argues that Haldar has the definition of minimalism wrong.</p>
<blockquote><p>Minimalism, at its core, is the process of prioritizing your life and working towards concrete goals without giving in to distraction. … Like any school of thought with a certain critical mass, there is dissent and corruption among the ranks.</p></blockquote>
<p>Who can find fault with prioritizing your life, working toward concrete goals, and avoiding distraction? And who wants to defend corruption? But this is just quibbling about definitions. By contrast, Haldar makes an argument independent of such a definition. Haldar argues that a certain set of attitudes and behaviors &#8212; however you want to label them &#8212; are not conducive to sustained creativity.</p>
<p><a href="http://www.johndcook.com/blog/2010/08/20/defining-minimalism/"></a>Here are some ideas I threw out a while ago on <a href="http://www.johndcook.com/blog/2010/08/20/defining-minimalism/">defining minimalism</a>.</p>
<blockquote><p>“Minimal” literally means an extreme. I appreciate moderate  minimalists, though strictly speaking “moderate minimalist” is a  contradiction in terms. A more accurate but unwieldy name for  minimalists might be “people who are keenly aware of the indirect costs  of owning stuff.”</p>
<p>… you could define a minimalist as someone  who wants to eliminate non-essential possessions … But by that definition, Donald Trump  would be a minimalist if he believes everything he owns is essential.</p></blockquote>
<p>Generic discussions of minimalism are fluff. Haldar&#8217;s argument is more substantial because he makes a specific suggestion.</p>
<p><strong>Related posts</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2010/12/07/cascading-needs/">Maybe you only need it because you have it</a><br />
<a href="http://www.johndcook.com/blog/2010/08/20/defining-minimalism/">Defining minimalism</a><br />
<a href="http://www.johndcook.com/blog/2010/08/19/selfish-minimalism/">Selfish minimalism</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2011/01/01/periodic-minimalism/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Take chances, make mistakes, and get messy</title>
		<link>http://www.johndcook.com/blog/2010/12/10/magic-school-bus/</link>
		<comments>http://www.johndcook.com/blog/2010/12/10/magic-school-bus/#comments</comments>
		<pubDate>Fri, 10 Dec 2010 13:41:57 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>
		<category><![CDATA[Education]]></category>
		<category><![CDATA[Science]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=7182</guid>
		<description><![CDATA[From Magic School Bus:
Take chances, make mistakes, and get messy.
Magic School Bus is an educational television show for children. The quote above is often repeated by the main character of the show, Ms. Frizzle.
Too many programs that supposedly teach science only teach results from science. Magic School Bus does both. It teaches specific facts, such [...]]]></description>
			<content:encoded><![CDATA[<p>From <a href="http://www.scholastic.com/magicschoolbus/">Magic School Bus</a>:</p>
<blockquote><p>Take chances, make mistakes, and get messy.</p></blockquote>
<p>Magic School Bus is an educational television show for children. The quote above is often repeated by the main character of the show, Ms. Frizzle.</p>
<p>Too many programs that supposedly teach <em>science</em> only teach <em>results from</em> science. Magic School Bus does both. It teaches specific facts, such as the names of the planets, but it also teaches that science is about taking chances, making mistakes, and getting messy.</p>
<p><strong>Related post</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2010/06/01/preparing-students-for-innovation/">Preparing for innovation</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2010/12/10/magic-school-bus/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Maybe you only need it because you have it</title>
		<link>http://www.johndcook.com/blog/2010/12/07/cascading-needs/</link>
		<comments>http://www.johndcook.com/blog/2010/12/07/cascading-needs/#comments</comments>
		<pubDate>Tue, 07 Dec 2010 15:13:11 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>
		<category><![CDATA[Minimalism]]></category>
		<category><![CDATA[Productivity]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=7272</guid>
		<description><![CDATA[Some cities need traffic lights because they have traffic lights.  If one traffic light goes out, it causes a traffic jam.  But sometimes when all traffic lights go out, say due to a storm, traffic flows better than before.
Some buildings need air conditioning because they have air conditioning.  Because they were designed [...]]]></description>
			<content:encoded><![CDATA[<p>Some cities need traffic lights because they have traffic lights.  If <em>one</em> traffic light goes out, it causes a traffic jam.  But sometimes when <em>all</em> traffic lights go out, say due to a storm, traffic flows better than before.</p>
<p>Some buildings need air conditioning because they have air conditioning.  Because they were designed to be air conditioned, they have no natural ventilation and would be miserable to inhabit without air conditioning.</p>
<p>Some people need to work because they work.  A family may find that their second income is going entirely to expenses that would go away if one person stayed home.</p>
<p>It&#8217;s hard to tell when you&#8217;ve gotten into a situation where you need something because you have it.  I had a friend that worked for a company that sold expensive software development tools.  He said that one of the best perks of his job was that he could buy these tools at a deep discount.  But he didn&#8217;t realize that without his job, he wouldn&#8217;t need these tools!  He wasn&#8217;t using them to develop software.  He was only using them so he could demonstrate and sell them.</p>
<p>It may be even harder for organizations to realize it has been caught in a cascade of needs.  Suppose a useless project adds staff.  These staff need to be managed, so they hire a manager.  Then they hire people for IT, accounting, marketing, etc. Eventually they have their own building. This building needs security, maintenance, and housekeeping.  No one questions the need for the security guard, but the guard would not have been necessary without the original useless project.</p>
<p>When something seems absolutely necessary, maybe it&#8217;s only necessary because of something else that isn&#8217;t necessary.</p>
<p><strong>Related post</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2010/08/20/defining-minimalism/">Defining minimalism</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2010/12/07/cascading-needs/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>You can be a hero with a simple idea</title>
		<link>http://www.johndcook.com/blog/2010/12/03/you-can-be-a-hero-with-a-simple-idea/</link>
		<comments>http://www.johndcook.com/blog/2010/12/03/you-can-be-a-hero-with-a-simple-idea/#comments</comments>
		<pubDate>Fri, 03 Dec 2010 15:24:46 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>
		<category><![CDATA[Originality]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=7243</guid>
		<description><![CDATA[Yesterday I mentioned someone who published a scholarly paper in 1994 for a technique commonly taught in freshman calculus. There&#8217;s been a lot of discussion of this (the paper, not my blog post) on the web. The general take has been that this was an egregious failure in the peer review system. No one recognized [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.johndcook.com/blog/2010/12/02/three-surprises-with-the-trapezoid-rule/">Yesterday</a> I mentioned someone who published a scholarly paper in 1994 for a technique commonly taught in freshman calculus. There&#8217;s been a lot of discussion of this (the paper, not my blog post) on the web. The general take has been that this was an egregious failure in the peer review system. No one recognized a simple, centuries-old idea. No one called up a high school math teacher and asked &#8220;Hey, have you seen this before?&#8221; All that is true, but here&#8217;s a different take on the situation.</p>
<p>The paper reinventing the trapezoid rule has been cited 75 times. It must have filled a need. Yes, the author was ignorant of basic calculus. But apparently a lot of other doctors are just as ignorant of calculus. The author did the medical profession a service by pointing out a simple way to estimate the area under a glucose-response curve. The technique was not original, and should not have been published as original research, but it was valuable.</p>
<p>Surely some doctors already knew how to find the area under a glucose-response curve. But apparently many others did not, and they learned something useful from the article. The article did some good, more good than original but arcane articles that <a href="http://www.johndcook.com/blog/2010/06/23/write-only-articles/">no one reads</a>, even though it was bad scholarship.</p>
<p>The author made a connection that not everyone else had made. This reminds me of Picasso&#8217;s sculpture <em>Head of a Bull</em>.</p>
<p style="text-align:center"><img src="http://www.johndcook.com/head_of_a_bull_jpg" alt="Picasso: Head of a Bull" width="300" height="243" /></p>
<p>All Picasso did was put handle bars on top of a bicycle seat and say &#8220;Hey, that looks like a bull.&#8221; His sculpture took zero technical skill, but it was clever. Was Picasso the first human to ever have this idea? Maybe, but I doubt it.</p>
<p>Sometimes you can be a hero by taking what is common as dirt in one context and applying it to a new context.</p>
<p><strong>Related posts</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2008/10/15/simple-legacy/">Simple legacy</a><br />
<a href="http://www.johndcook.com/blog/2008/01/12/three-quotes-on-originality/">Three quotes on originality</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2010/12/03/you-can-be-a-hero-with-a-simple-idea/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Fairy dust on the diploma</title>
		<link>http://www.johndcook.com/blog/2010/11/24/fairy-dust-on-the-diploma/</link>
		<comments>http://www.johndcook.com/blog/2010/11/24/fairy-dust-on-the-diploma/#comments</comments>
		<pubDate>Wed, 24 Nov 2010 13:10:13 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>
		<category><![CDATA[Education]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=6915</guid>
		<description><![CDATA[When I was in college, a friend of mine gave me a math book that I found hard to get through. When I complained about it, he told me &#8220;You&#8217;re going to finish a PhD someday. When you do, do you think there&#8217;s going to be fairy dust on the diploma that&#8217;s going to enable [...]]]></description>
			<content:encoded><![CDATA[<p>When I was in college, a friend of mine gave me a math book that I found hard to get through. When I complained about it, he told me &#8220;You&#8217;re going to finish a PhD someday. When you do, do you think there&#8217;s going to be fairy dust on the diploma that&#8217;s going to enable you to do anything you can&#8217;t do now?&#8221;</p>
<p>That conversation stuck with me. I realized that I just needed to work hard rather than wait for my intelligence to mysteriously rise at graduation.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2010/11/24/fairy-dust-on-the-diploma/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Two kinds of generalization</title>
		<link>http://www.johndcook.com/blog/2010/11/22/two-kinds-of-generalization/</link>
		<comments>http://www.johndcook.com/blog/2010/11/22/two-kinds-of-generalization/#comments</comments>
		<pubDate>Mon, 22 Nov 2010 14:00:58 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>
		<category><![CDATA[Math]]></category>
		<category><![CDATA[Software development]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Quotes]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=7133</guid>
		<description><![CDATA[From George Pólya:
There are two kinds of generalizations. One is cheap and the other is valuable. It is easy to generalize by diluting a little idea with a big terminology. It is much more difficult to prepare a refined and condensed extract from several good ingredients.
Related post:
Jenga mathematics
]]></description>
			<content:encoded><![CDATA[<p>From George Pólya:</p>
<p style="padding-left: 30px;">There are two kinds of generalizations. One is cheap and the other is valuable. It is easy to generalize by diluting a little idea with a big terminology. It is much more difficult to prepare a refined and condensed extract from several good ingredients.</p>
<p><strong>Related post</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2009/02/14/old-math-books/"></a><a href="http://www.johndcook.com/blog/2008/05/11/jenga-mathematics/">Jenga mathematics</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2010/11/22/two-kinds-of-generalization/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Two videos on craftsmanship</title>
		<link>http://www.johndcook.com/blog/2010/11/19/two-videos-on-craftsmanship/</link>
		<comments>http://www.johndcook.com/blog/2010/11/19/two-videos-on-craftsmanship/#comments</comments>
		<pubDate>Fri, 19 Nov 2010 12:24:56 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=7123</guid>
		<description><![CDATA[Here are a couple inspiring videos about craftsmen, sign artist David A. Smith and machinist Neil Youngberg.

David A Smith &#8211; Sign Artist from Danny Cooke on Vimeo.

PROFESSIONal from VITA BREVIS FILMS on Vimeo.
]]></description>
			<content:encoded><![CDATA[<p>Here are a couple inspiring videos about craftsmen, sign artist David A. Smith and machinist Neil Youngberg.</p>
<p><iframe src="http://player.vimeo.com/video/14985356" width="400" height="225" frameborder="0"></iframe>
<p><a href="http://vimeo.com/14985356">David A Smith &#8211; Sign Artist</a> from <a href="http://vimeo.com/dannycooke">Danny Cooke</a> on <a href="http://vimeo.com">Vimeo</a>.</p>
<p><object width="400" height="225"><param name="allowfullscreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="movie" value="http://vimeo.com/moogaloop.swf?clip_id=16435404&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=1&amp;color=&amp;fullscreen=1&amp;autoplay=0&amp;loop=0" /><embed src="http://vimeo.com/moogaloop.swf?clip_id=16435404&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=1&amp;color=&amp;fullscreen=1&amp;autoplay=0&amp;loop=0" type="application/x-shockwave-flash" allowfullscreen="true" allowscriptaccess="always" width="400" height="225"></embed></object>
<p><a href="http://vimeo.com/16435404">PROFESSIONal</a> from <a href="http://vimeo.com/user745342">VITA BREVIS FILMS</a> on <a href="http://vimeo.com">Vimeo</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2010/11/19/two-videos-on-craftsmanship/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>The trouble with wizards</title>
		<link>http://www.johndcook.com/blog/2010/11/11/wizards/</link>
		<comments>http://www.johndcook.com/blog/2010/11/11/wizards/#comments</comments>
		<pubDate>Thu, 11 Nov 2010 14:56:51 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Creativity]]></category>

		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=7032</guid>
		<description><![CDATA[It&#8217;s usually a compliment to call someone a &#8220;wizard.&#8221; For example, the stereotypical Unix wizard is a man with a long gray beard who can solve any problem in minutes by typing furiously at a command prompt.
Here&#8217;s a different take on wizards. Think about wizards, say, in the Harry Potter novels. Wizards learn to say [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s usually a compliment to call someone a &#8220;wizard.&#8221; For example, the stereotypical Unix wizard is a man with a long gray beard who can solve any problem in minutes by typing furiously at a command prompt.</p>
<p>Here&#8217;s a different take on wizards. Think about wizards, say, in the Harry Potter novels. Wizards learn to say certain spells in certain situations. There&#8217;s never any explanation of why these spells work. They just do. Unless, of course, they don&#8217;t. Wizards are powerful, but they can be incompetent.</p>
<p>You might use <em>wizard</em> to describe someone who lacks curiosity about what they&#8217;re doing. They don&#8217;t know why their actions work, or sometimes even whether they work. They&#8217;ve learned a Pavlovian response to problems: when you see this, do this.</p>
<p>Wizards can be valuable. Sometimes you just need a problem solved and you don&#8217;t care why the solution works. Someone who doesn&#8217;t understand what they&#8217;re doing but can fix your problem quickly may be better than someone who knows what they&#8217;re doing but works too slowly. But if your problem doesn&#8217;t quite fit the intended situation for a spell, the wizard is either powerless or harmful.</p>
<p>Wizards can&#8217;t learn a better way of doing anything because &#8220;better&#8221; makes no sense. When you see problem <em>A</em>, carry out procedure <em>B</em>. That&#8217;s just what you do. How can you address problem <em>A </em>better when &#8220;solving <em>A</em>&#8221; means &#8220;do <em>B</em>&#8220;? Professional development for a wizard consists of learning more spells for more situations, not learning a better spell or learning why spells work.</p>
<p>Wizards may be able to solve your problem for you, but they can&#8217;t teach you how to solve your own problems.</p>
<p><strong>Related posts</strong>:</p>
<p><a href="http://www.johndcook.com/blog/2010/04/27/chauffers-and-ferraris-revisited/">Chauffeurs and Ferraris revisited</a><br />
<a href="http://www.johndcook.com/blog/2010/05/20/in-defense-of-reinventing-wheels/">In defense of reinventing wheels</a><br />
<a href="http://www.johndcook.com/blog/2009/10/14/opening-black-boxes/">Opening black boxes</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.johndcook.com/blog/2010/11/11/wizards/feed/</wfw:commentRss>
		<slash:comments>17</slash:comments>
		</item>
	</channel>
</rss>

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

