<?xml version="1.0"?>
<rss version="2.0.">
  <channel>
    <title>Advogato blog for jermnelson</title>
    <link>http://www.advogato.org/person/jermnelson/</link>
    <description>Advogato blog for jermnelson</description>
    <language>en-us</language>
    <generator>mod_virgule</generator>
    <pubDate>Thu, 24 Jul 2008 18:37:27 GMT</pubDate>
    <item>
      <pubDate>Fri, 15 Dec 2000 16:29:56 GMT</pubDate>
      <title>15 Dec 2000</title>
      <link>http://www.advogato.org/person/jermnelson/diary.html?start=1</link>
      <guid>http://www.advogato.org/person/jermnelson/diary.html?start=1</guid>
      <description>&lt;p&gt;
&lt;b&gt;Note:&lt;/b&gt; I wrote this rant a couple of months ago and 
since 
it 
kind of follows the same patterns as my diary entry from 
yesterday, I decided to submit it.

&lt;p&gt; &lt;br&gt;
----
&lt;br&gt;
&lt;b&gt;Technology Rant One&lt;/b&gt;
&lt;p align="right"&gt;
&lt;i&gt;Jeremy Nelson&lt;/i&gt;&lt;br&gt;
&lt;i&gt;October 4th, 2000&lt;/i&gt;

&lt;p&gt; &lt;p&gt;
Like Jaron Lanier (both in an &lt;a href=" 
http://www.salon.com/tech/feature/2000/10/04/lanier/index.ht
ml
" &gt;interview&lt;/a&gt; and in his &lt;a href="http://www.edge.org/3rd_culture/lanier/lanier_index.ht
ml" &gt;One Half of a Manifesto&lt;/a&gt;), I hate Microsoft Word's 
auto- spelling and grammar correction. Unfortunately, 
MSWord has become the standard by which all other Word 
Processors are designed too. I noticed this yesterday when 
I was working with a demo copy of AmiPro on Linux. They 
borrow too much from MSWord User Interface then is 
necessary. (Funny sidenote, I pasted this page into MSWord 
97 for spell checking since I couldn't get Window NT 
version of Emacs' spell check to work and noticed the 
following. Linux is automatically marked as a misspelled 
word. I bet that MSWord 2000 recognizes Linux. This is very 
similar to how MSWord 95 marked the words Internet and web-
pages as misspellings in 1995-97.) 

&lt;p&gt; &lt;p&gt;
Neal Stephenson is right in his essay, "&lt;a href="http://www.cryptonomicon.com/beginning.html" &gt;In the 
Beginning was the Command Line&lt;/a&gt;", modern User Interfaces 
prevent too much from the raw power of the machine. Having 
said that, the learning curve to actually use your computer 
at a lower level is still very steep. While installing 
Mandrake Linux's 7.0 installation was a lot less painful 
then my older copy of Red Hat's Linux installation, it 
still is not as easy to use as the MS's Windows 98 
installer. The biggest problem for me with Mandrake 7.0's 
installer was that it hides too many details from me, 
details that later became very important. The Mandrake 7.1 
installer is better, which makes me believe that Open 
Source software could be a desk-top competitor to MS by the 
time of MS's next big consumer OS release because it was 
less then four months between the release of the two 
different versions. 

&lt;p&gt; &lt;p&gt;
These experiences re-enforce my beliefs about what makes 
good software design: Here are a few of them, in no 
particular order: 
&lt;ul&gt;
&lt;li&gt;Good software design allows multiple ways for users to 
accomplish his or her tasks.
&lt;li&gt;A good GUI tool should provide a way to view the 
internal details of what it is doing for interested users. 
These internal details should explain what is going on as 
well providing the raw OS API calls.
&lt;li&gt;Good writing is critical to good software.
&lt;li&gt;Users are normally smarter then developers give them 
credit, just because their actions do not follow the 
developer's own methodology does not mean that the users' 
mode of rational thought is wrong.
&lt;li&gt;Conversely, user's actions are sometimes random, not 
following any rational path. This is the hardest case to 
design for in software.
&lt;/ul&gt;
</description>
    </item>
    <item>
      <pubDate>Thu, 14 Dec 2000 17:48:44 GMT</pubDate>
      <title>14 Dec 2000</title>
      <link>http://www.advogato.org/person/jermnelson/diary.html?start=0</link>
      <guid>http://www.advogato.org/person/jermnelson/diary.html?start=0</guid>
      <description>This is a quick (and my first) Journal entry. It is really 
in response to last night's concession and acceptance 
speeches for the United States' Presidency and how it 
presents a great opportunity for the Open Source Movement.  

&lt;p&gt; Following President Clinton, and others' call for a &lt;a href="http://www.salon.com/politics/wire/2000/12/14/clinton_
text/index.html" &gt;"commonsense bipartisan election 
reforms"&lt;/a&gt;, we should focus on building an open-source 
solution for voting, collecting, and tabulating votes. As 
the source code would be open for all to see, it would 
avoid the criticism of digital manipulation that could 
arise from closed source software. This brings up a number 
challenges for all of us:

&lt;p&gt; &lt;ul&gt;
&lt;li&gt;The technical solution should be robust and inexpensive 
to deploy
&lt;li&gt;Both the raw votes and the tabulation data MUST be open 
for all.
&lt;li&gt;The technical solution must be easy to use and deploy. 
We have to focus on inexperienced users and their needs and 
not on our bias.
&lt;li&gt;We must partner with receptive politicians, no matter 
their party affiliation or politics. This is supercedes 
both. 
&lt;/ul&gt;
For too long we in the technical community (be it open-
source developers, hanger-ons like myself who work as 
developers in corporate IT departments, and the great CS 
academic faculty and students) have absconded our civic 
responsibilities. Let us show the world the power and 
freedom open source has in contributing to democracy. We 
have arrived and we as community are more then the work 
engines of the world's information infrastructure.
</description>
    </item>
  </channel>
</rss>
