<?xml version="1.0"?>
<rss version="2.0.">
  <channel>
    <title>Advogato blog for scav</title>
    <link>http://www.advogato.org/person/scav/</link>
    <description>Advogato blog for scav</description>
    <language>en-us</language>
    <generator>mod_virgule</generator>
    <pubDate>Wed, 9 Jul 2008 06:51:57 GMT</pubDate>
    <item>
      <pubDate>Wed, 14 Feb 2001 13:50:33 GMT</pubDate>
      <title>14 Feb 2001</title>
      <link>http://www.advogato.org/person/scav/diary.html?start=2</link>
      <guid>http://www.advogato.org/person/scav/diary.html?start=2</guid>
      <description>I am wondering about whether to get Linux certification, 
and how valuable it would be. Not valuable as "marketable" 
but valuable personally.
&lt;p&gt;
Anyway, I wonder if it would differ from MS certification 
in the way that really counts - would it be "grey" 
knowledge or "green" knowledge?
&lt;p&gt;
I would call "grey" any knowledge that is arbitrary facts 
you just have to remember. Eg. which menu option to choose 
to do a word count, what year a certain battle took place, 
how to conjugate an irregular verb. The facts may be useful 
as they are, but that's all they are.
&lt;p&gt;
"Green" knowledge reflects an underlying reality, and can 
grow by interlinking with other things, related or 
otherwise, to contribute to a deeper understanding. Not 
just how things are, but WHY. E.g. how to use pipes to 
filter text files (including getting a word 
count), what influences caused a battle to take place, how 
conjugation of regular verbs works and which verbs to 
expect to be irregular.
&lt;p&gt;
So, would Linux certification leave me with a better mental 
map of OS design and good practice, or just a head full 
of "how to install Red Hat"?
</description>
    </item>
    <item>
      <pubDate>Thu, 8 Feb 2001 15:00:08 GMT</pubDate>
      <title>8 Feb 2001</title>
      <link>http://www.advogato.org/person/scav/diary.html?start=1</link>
      <guid>http://www.advogato.org/person/scav/diary.html?start=1</guid>
      <description>Recently released 1.2beta2 of f2w helpdesk.
&lt;p&gt;
Now, I really have a very na&#xEF;ve understanding of how to 
choose version numbers, so it should probably not be above 
version 1.0. I live and learn.
&lt;p&gt;
Also, less recently, I've read Erich Fromm's book "To Have 
or To Be". Heavy going in places, but pretty sound and 
satisfyingly spiritual. In short, he says what you 
&lt;i&gt;are&lt;/i&gt; is important (and by 
extension, what you can become); what you &lt;i&gt;have&lt;/i&gt; is 
not.
&lt;p&gt;
A parallel with software development: contrast "owning 
intellectual property" with "being creative".
&lt;p&gt;
I notice this viewpoint helps with the usually difficult 
but serious 
question "What do you REALLY want?". If you interpret this 
as "what do you want to HAVE?", there is no end to it, and 
you are into that old finite resources and infinite options 
thing. If you ask instead "what do you want to BE?", it's a 
question you can answer to the first approximation, and the 
answer can be a productive one.
&lt;p&gt;
Or so I think, anyway.</description>
    </item>
    <item>
      <pubDate>Mon, 8 Jan 2001 14:54:31 GMT</pubDate>
      <title>8 Jan 2001</title>
      <link>http://www.advogato.org/person/scav/diary.html?start=0</link>
      <guid>http://www.advogato.org/person/scav/diary.html?start=0</guid>
      <description>Just spent a gruelling couple of days writing documentation
for &lt;a href="http" ://f2w.sourceforge.net&gt;f2w helpdesk&lt;/a&gt;.
&lt;p&gt;
It strikes me this is where free software projects are most
likely to repel potential users and contributors. Because
I had a look at my project, imagining I was a newcomer to
it, and I was repelled.
&lt;p&gt;
Hence, the User Guide and Admin Guide that I knew all along 
would be needed finally got written.
&lt;p&gt;
Oh well.
</description>
    </item>
  </channel>
</rss>
