<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Toxic Elephant : Tag usability, everything about usability</title>
    <link>http://www.matijs.net/blog/tag/usability.rss</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Don't bury it in your back yard!</description>
    <item>
      <title>Disqualified by advertising</title>
      <description>&lt;p&gt;I was enthousiastic about &lt;a href="http://www.noobkit.com/"&gt;noobkit&lt;/a&gt; for about a week.  Finally an alternative to the rough style of Ruby&amp;#8217;s standard &lt;span class="caps"&gt;API&lt;/span&gt; documentation.&lt;/p&gt;


	&lt;p&gt;Until I actually wanted to use it.&lt;/p&gt;


	&lt;p&gt;Most pages have a full width block of Google ads above the main content. This is just too much. For some methods, the text is one line. The ad block then is five times as big.&lt;/p&gt;


	&lt;p&gt;I&amp;#8217;ll go back to using &lt;a href="http://api.rubyonrails.org/"&gt;the old version&lt;/a&gt;, thanks.&lt;/p&gt;


	&lt;p&gt;[Also, the search function is not geared towards &lt;span class="caps"&gt;API&lt;/span&gt; documentation, but instead uses a generic Google-like method. Why not highlight the search results that actually describe the method or methods with the searched name?]&lt;/p&gt;</description>
      <pubDate>Thu, 23 Aug 2007 16:36:00 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:b55e33e2-e2ae-4200-bc3c-7877df2d125f</guid>
      <author>blog@matijs.net (matijs)</author>
      <comments>http://www.matijs.net/blog/2007/08/23/disqualified-by-advertising#comments</comments>
      <category>web</category>
      <category>usability</category>
      <category>rails</category>
      <category>advertising</category>
      <category>api</category>
      <trackback:ping>http://www.matijs.net/blog/trackbacks?article_id=disqualified-by-advertising&amp;day=23&amp;month=08&amp;year=2007</trackback:ping>
      <link>http://www.matijs.net/blog/2007/08/23/disqualified-by-advertising</link>
    </item>
    <item>
      <title>crontab -r</title>
      <description>&lt;p&gt;I don&amp;#8217;t use the &lt;code&gt;crontab&lt;/code&gt; command on my own machines (I just put files in
&lt;code&gt;/etc/cron*&lt;/code&gt;), but recent experience on another machine made me wonder why
crontab has the following options (this is from &lt;code&gt;crontab --help&lt;/code&gt;):&lt;/p&gt;


	&lt;pre&gt;&lt;code&gt;-e      (edit user's crontab)
-l      (list user's crontab)
-r      (delete user's crontab)&lt;/code&gt;&lt;/pre&gt;


	&lt;p&gt;Right. E is for edit, L is for list, R is for delete. Makes sense. And as a
bonus, it is easier to accidentally delete your crontab when you want to
edit it.&lt;/p&gt;


	&lt;p&gt;Brilliant.&lt;/p&gt;</description>
      <pubDate>Tue, 20 Mar 2007 18:27:00 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:3594dde3-50c7-4b5c-ad11-812c0b2f3509</guid>
      <author>blog@matijs.net (matijs)</author>
      <comments>http://www.matijs.net/blog/2007/03/20/crontab-r#comments</comments>
      <category>software</category>
      <category>usability</category>
      <trackback:ping>http://www.matijs.net/blog/trackbacks?article_id=crontab-r&amp;day=20&amp;month=03&amp;year=2007</trackback:ping>
      <link>http://www.matijs.net/blog/2007/03/20/crontab-r</link>
    </item>
  </channel>
</rss>
