<?xml version='1.0' encoding='utf-8' ?>

<rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/' xmlns:atom10='http://www.w3.org/2005/Atom'>
<channel>
  <title>Rick Scott</title>
  <link>https://rickscott.dreamwidth.org/</link>
  <description>Rick Scott - Dreamwidth Studios</description>
  <lastBuildDate>Thu, 08 Jul 2010 17:13:46 GMT</lastBuildDate>
  <generator>LiveJournal / Dreamwidth Studios</generator>
  <lj:journal>rickscott</lj:journal>
  <lj:journaltype>personal</lj:journaltype>
  <image>
    <url>https://v2.dreamwidth.org/505476/518129</url>
    <title>Rick Scott</title>
    <link>https://rickscott.dreamwidth.org/</link>
    <width>100</width>
    <height>97</height>
  </image>

<item>
  <guid isPermaLink='true'>https://rickscott.dreamwidth.org/4360.html</guid>
  <pubDate>Thu, 08 Jul 2010 17:13:46 GMT</pubDate>
  <title>Every Act of Software is an Act of Invention</title>
  <link>https://rickscott.dreamwidth.org/4360.html</link>
  <description>&lt;p&gt;
Robert O’Callahan 
&lt;a href=&quot;http://weblogs.mozillazine.org/roc/archives/2010/07/mozilla_and_sof.html&quot;&gt;very coherently expressed&lt;/a&gt;
something I&apos;ve thought about software for a long time:
&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;
In software, especially cutting-edge software like Firefox, every
developer is an inventor; coming up with new ways of doing things is
not exceptional, it&apos;s what our developers do every single day. 
&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p style=&quot;text-align: right; font-size: smaller;&quot;&gt;
(h/t
&lt;a href=&quot;http://coffee.geek.nz/firefoxs-robert-ocallahan-software-patents-nz.html&quot;&gt;Br3nda&lt;/a&gt;)
&lt;/p&gt;


&lt;p&gt;
&lt;strong&gt;
Every piece of software is something new.  
&lt;/strong&gt;
Every time we sit down to create software, we&apos;re inventing something.
We&apos;re creating something that, in a very specific sense, has never
existed before -- much like we didn&apos;t have 
&lt;em&gt;&lt;a href=&quot;http://en.wikipedia.org/wiki/War_and_Peace&quot;&gt;War and Peace&lt;/a&gt;&lt;/em&gt;
before Tolstoy sat down to write it.  After all, if you wanted an
exact replica of some existing piece of software, wouldn&apos;t you just
copy it instead of making it yourself?
&lt;/p&gt;

&lt;p&gt;
Horrible metaphors of construction, engineering, or manufacturing are 
&lt;em&gt;so&lt;/em&gt; frequently applied to software creation.  
&quot;Making software should be just like building a house!&quot; people say,
less-than-subtly implying that it should be perfectly predictable
in both time and cost
(and ignoring the massive schedule and cost overruns that often 
plague construction projects).
But 
&lt;strong&gt;making a new program isn&apos;t like making other programs one might
have made before&lt;/strong&gt;.  You may be informed by similarities 
between a new project and older ones, and you certainly get better
with the tools, but you&apos;re not faster because an identical item has 
been made before -- &lt;strong&gt;it hasn&apos;t&lt;/strong&gt;.
&lt;/p&gt;&lt;br /&gt;&lt;br /&gt;&lt;img src=&quot;https://www.dreamwidth.org/tools/commentcount?user=rickscott&amp;ditemid=4360&quot; width=&quot;30&quot; height=&quot;12&quot; alt=&quot;comment count unavailable&quot; style=&quot;vertical-align: middle;&quot;/&gt; comments</description>
  <comments>https://rickscott.dreamwidth.org/4360.html</comments>
  <category>software creation</category>
  <category>creativity</category>
  <category>innovation</category>
  <category>software development</category>
  <category>artistic software development</category>
  <category>software</category>
  <category>metaphor</category>
  <category>process</category>
  <lj:security>public</lj:security>
  <lj:reply-count>0</lj:reply-count>
</item>
</channel>
</rss>
