<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0"><channel><title>mike's web log</title><link>http://www.mikepope.com/blog/</link><description>mike pope's Web log</description><language>en-US</language><docs>http://www.mikepope.com/blog/BlogFeed.rss</docs><webMaster>mike@mikepope.com</webMaster><lastBuildDate>Thu, 16 Jul 2009 01:32:54 GMT</lastBuildDate><pubDate>Monday, July 20, 2009 9:22:15 PM</pubDate><ttl>60</ttl><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/mikepope/wAZr" type="application/rss+xml" /><feedburner:browserFriendly>This is an XML content feed. It is intended to be viewed in a newsreader or syndicated to another site, subject to copyright and fair use.</feedburner:browserFriendly><item><title>This is not the Mike Pope you are looking for</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/pGoUn7difIs/DisplayBlog.aspx</link><description>I subscribe to Google Ads (over there on the left). It's been kind of interesting; for example, if I keep showing the ads for the next 1.8 million years, I'll definitely start making enough for them to send me a check. &lt;br /&gt;&lt;br /&gt;Haha. It is interesting, sort of, to watch their contextualization process in action. For the first little while, alls I saw were ads for blogging software. Now and again I'll see an ASP.NET ad. Other than that, it's sort of a crapshoot.&lt;br /&gt;&lt;br /&gt;Today I saw one that made me grin, because it indicated that the Ad Sense algorithm isn't quite foolproof. Here's the ad I saw:&lt;br /&gt;&lt;br /&gt;&lt;div style="margin-left:50px"&gt;&lt;img src="http://www.mikepope.com/blog/images/BassAd.png" width='249' height='208' /&gt;&lt;/div&gt;&lt;br /&gt;Now, if you know me, you probably know that I flail away at learning to play the guitar. On odd occasions I have blathered about that here. So if there's something on the blog that's about guitar, that's not an unreasonable context for displaying an ad for learning to play bass.&lt;br /&gt;&lt;br /&gt;But I know better. You see, there are several of us Mike Popes, and if you &lt;a href="http://www.google.com/search?q=mike+pope&amp;rls=com.microsoft:en-us&amp;ie=UTF-8&amp;oe=UTF-8&amp;startIndex=&amp;startPage=1" target="_blank"&gt;search Google&lt;/a&gt;, the &lt;em&gt;first&lt;/em&gt; Mike Pope you get is the &lt;a href="http://www.mikepopejazz.com/" target="_blank"&gt;Mike Pope who plays jazz bass&lt;/a&gt;.[&lt;a href='#thisisnotthemikepopeyouarelookingfor1'&gt;1&lt;/a&gt;] Which is to say, a Mike Pope who actually knows what he's doing around string instruments.&lt;br /&gt;&lt;br /&gt;Thus Google ad sense has gotten slightly confused. It seems to think that folks reading this blog are fans of the jazzy Mike Pope. That would flattering to me, but ... I don't think so.&lt;br /&gt;&lt;br /&gt;Still, if you &lt;em&gt;are&lt;/em&gt; interested in learning bass, by all means, click through the ad. Wth Ad Sense, every little bit counts. :-)&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;span class='footnote'&gt;&lt;a name='thisisnotthemikepopeyouarelookingfor1'&gt;[1]&lt;/a&gt; "Walk Your Dogma," how excellent a CD title is that?&lt;/span&gt;</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>technology</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2144</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2144</guid><pubDate>Thu, 16 Jul 2009 01:32:54 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2144">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2144</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2144</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2144</wfw:commentRss><slash:comments>0</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2144</feedburner:origLink></item><item><title>If you can't say something nice ...</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/PRjByz3k_0s/DisplayBlog.aspx</link><description>At work, we write documentation for programmers, so our docs include many code examples[&lt;a href='#ifyoucantsaysomethingnice1'&gt;1&lt;/a&gt;]. We should comment our code, right? Of course. However, a discussion broke out in our ranks yesterday about the whole idea of commenting the example code. The discussion arose out of the complaint that a lot of comments in a lot of code (not just ours) are actually lame. This was an observation made in a recent &lt;a href="http://hackingon.net/post/Thoughts-on-nerddinner.aspx" target="_blank"&gt;blog entry&lt;/a&gt;, which used the following as an example:&lt;br /&gt;&lt;br /&gt;&lt;img src="http://www.mikepope.com/blog/images/LameComments.png" width='518' height='193' /&gt;&lt;br /&gt;&lt;br /&gt;In the wake of this, a semi-unserious proposal was made that because most comments are dumb, we should just strip all comments from the example code. Because code examples are not translated, we have to explain the code in the text of a topic anyway. &lt;br /&gt;&lt;br /&gt;Hmmm. This type of proposal is useful for goading me into thinking through our policy. Herewith my thots:&lt;ul&gt;&lt;li&gt;Having &lt;em&gt;decent&lt;/em&gt; comments in a snippet is useful for the person who copies and pastes an example into their application, even if the code is explained in the topic.&lt;/li&gt;&lt;br /&gt;&lt;li&gt;As with &lt;a href="http://msdn.microsoft.com/en-us/library/system.web.mvc.actionnameattribute.name.aspx" target="_blank"&gt;member descriptions&lt;/a&gt;, &lt;a href="http://msdn.microsoft.com/en-us/library/02se1ya4(VS.80).aspx" target="_blank"&gt;descriptions in orientation topics&lt;/a&gt;, &lt;a href="http://msdn.microsoft.com/en-us/library/fshz3d5x(VS.80).aspx" target="_blank"&gt;UI reference topics&lt;/a&gt;, and other such, it takes time and thought to create a comment that is actually useful to the reader. All of these types of text share the characteristic that they are often written as an afterthought, in a hurry, only to fulfill a general requirement, or while the writer's attention is focused elsewhere.&lt;/li&gt;&lt;br /&gt;&lt;li&gt; [&lt;a href='http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2143'&gt;more&lt;/a&gt;]</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>writing,aspnet</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2143</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2143</guid><pubDate>Thu, 02 Jul 2009 11:18:53 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2143">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2143</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2143</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2143</wfw:commentRss><slash:comments>4</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2143</feedburner:origLink></item><item><title>Two things at a time</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/rBJEx16NZj8/DisplayBlog.aspx</link><description>Have I ever recounted my Theory of Two Things? The theory is this: there are many things to attend to in one's life, but I can only attend to two things at a time. For example, here are the sorts of things that are part of my life:&lt;a href="http://blogs.pcworld.com/phoneconnection/archives/006333.html" target="_blank" &gt;&lt;img src="http://www.mikepope.com/blog/images/Juggling.gif" width='198' height='182' style="float:right;border:none;" alt="Click to see original source of image."/&gt;&lt;/a&gt;&lt;ul&gt;&lt;li&gt;family&lt;br /&gt;&lt;li&gt;work&lt;br /&gt;&lt;li&gt;friends&lt;br /&gt;&lt;li&gt;reading&lt;br /&gt;&lt;li&gt;home improvement&lt;br /&gt;&lt;li&gt;guitar&lt;br /&gt;&lt;li&gt;blogging&lt;br /&gt;&lt;li&gt;exercising&lt;br /&gt;&lt;li&gt;taking classes&lt;br /&gt;&lt;li&gt;teaching classes&lt;/ul&gt;And etc. Per my theory, I can only really be putting serious energy into two of these at a time. So, if work is intense and I'm practicing guitar diligently, I'm ignoring family and blogging. If we're doing family things and I'm working on some house project or other, work and guitar and all the rest get short shrift. I can prep to teach a class and work, or I can work and have a busy social life, or I can work out regularly and do home improvement, or I can blog regularly and read a lot, or ... anyway, you get the idea.&lt;br /&gt;&lt;br /&gt;Clearly there are people who can handle three or four or more of these types of things concurrently. (I seem to work with a lot of people like that.) But one has to know oneself, no? And I have to recognize, after long experience, that taking on some attention-sucking task means I have to jettison something else, until the total count of tasks is, like, two. &lt;br /&gt;&lt;br /&gt;What's your limit for number of concurrent tasks?</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>personal</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2142</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2142</guid><pubDate>Thu, 25 Jun 2009 01:28:15 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2142">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2142</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2142</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2142</wfw:commentRss><slash:comments>4</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2142</feedburner:origLink></item><item><title>More web site usability</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/NO-A2uiGrG8/DisplayBlog.aspx</link><description>I recently &lt;a href="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2137" target="_blank"&gt;whined&lt;/a&gt; about the confusing UI that many web sites present for navigating through the (many!) options that they offer. I used to really have it in for the sites run by banks, but I am obliged to acknowledge that they've gotten much better over time.&lt;br /&gt;&lt;br /&gt;But I am happy to say that I can still be snotty about the sites run by universities. Having two kids in college, I go through a quarterly/semesterly exercise in which I log in and behold the price of ... uh ... well, different topic.&lt;br /&gt;&lt;br /&gt;Anyway, here's an example. This is the "menu" that the "authorized payer" site at Indiana U presents, with the one I generally need highlighted. Tell me what logic went into the order of the elements.&lt;br /&gt;&lt;br /&gt;&lt;div style="margin-left:50px"&gt;&lt;img src="http://www.mikepope.com/blog/images/IUPayer.png" width='153' height='201' /&gt;&lt;/div&gt;</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>technology</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2141</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2141</guid><pubDate>Wed, 24 Jun 2009 09:56:28 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2141">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2141</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2141</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2141</wfw:commentRss><slash:comments>0</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2141</feedburner:origLink></item><item><title>Happy (Belated) Birthday, Zack!</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/jvwF4KbmSBg/DisplayBlog.aspx</link><description>A day late, dang! This was 22 years ago yesterday:&lt;br /&gt;&lt;br /&gt;&lt;img src="http://www.mikepope.com/blog/images/ZackJustBorn.png" width='604' height='368' /&gt;</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>family</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2140</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2140</guid><pubDate>Fri, 12 Jun 2009 12:06:26 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2140">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2140</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2140</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2140</wfw:commentRss><slash:comments>0</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2140</feedburner:origLink></item><item><title>One reason I haven't gotten a Kindle</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/rGbAKilj_GE/DisplayBlog.aspx</link><description>I like the &lt;em&gt;idea&lt;/em&gt; of e-book readers. But economically it isn't making sense to me.&lt;br /&gt;&lt;br /&gt;&lt;div style="margin-left:50px"&gt;&lt;a href="http://www.amazon.com/Windows-Presentation-Foundation-Unleashed-WPF/dp/0672328917" target="_blank"&gt;&lt;img src="http://www.mikepope.com/blog/images/Kindle_Price.png" width='434' height='303' /&gt;&lt;/a&gt;&lt;/div&gt;</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>technology,books</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2139</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2139</guid><pubDate>Wed, 10 Jun 2009 08:12:13 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2139">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2139</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2139</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2139</wfw:commentRss><slash:comments>3</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2139</feedburner:origLink></item><item><title>Of giants and fossil fuels</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/vvN5Iel1Z1U/DisplayBlog.aspx</link><description>Recently I finished &lt;em&gt;&lt;a href="http://www.amazon.com/Invention-Air-Steven-Johnson/dp/1594488525" target="_blank"&gt;The Invention of Air&lt;/a&gt;&lt;/em&gt; by Steven Johnson, which is a book about the English scientist Joseph Priestley, who is &lt;img src="http://www.mikepope.com/blog/images/InventionOfAir.jpg" width='145' height='216' style="float:right;margin:8px"/&gt; best known as the discoverer of oxygen. Johnson shows how Priestley had a strong influence on both science and politics (he was a close friend Jefferson and Franklin). But Priestley also sat at a historical confluence that was conducive to, basically, Enlightenment thinking, and Johnson ties together many threads in a way reminiscent of &lt;a href="http://en.wikipedia.org/wiki/James_Burke_(science_historian)" target="_blank"&gt;James Burke&lt;/a&gt;: coffeehouses and efficient postal delivery, which fostered open and fast communication; innovations in scientific technology, which let Priestley engage in the experiments he did; the wealth of the industrial age, which indirectly provided Priestley with the time to do research; and so on. &lt;br /&gt;&lt;br /&gt;At times the chains of connections go quite far indeed -- for example, from Priestley's simple experiment with a mint plant all the way to the field of planetary ecology. A continuing theme is energy: sunlight to feed plants, coffee to feed scientific minds, oxygen to feed animals, coal to feed the industrial revoltuion, and so on. To discuss these last two, Johnson takes a side trip way back in Earth history to the Carboniferous era, where he tells the following story.&lt;br /&gt;&lt;br /&gt;&lt;hr/&gt;&lt;br /&gt;Many of the fossils that Brongniart uncovered shared a defining characteristic: compared to their modern equivalents, they were massive. He discovered ferns the size of oak trees, and flies as big as birds. In 1880 he unearthed his most startling find: a monster dragonfly (&lt;em&gt;Meganeura&lt;/em&gt;) with a wingspan of 63 centimeters [2 feet]. Subsequent fossils have been discovered with a wingspan of more than 75 centimeters. &lt;br /&gt;&lt;br /&gt;&lt;em&gt; [&lt;a href='http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2138'&gt;more&lt;/a&gt;]</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>readings,history,books</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2138</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2138</guid><pubDate>Sun, 07 Jun 2009 11:20:36 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2138">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2138</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2138</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2138</wfw:commentRss><slash:comments>1</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2138</feedburner:origLink></item><item><title>No wonder I get confused using Web apps</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/i3zm8OXNHBg/DisplayBlog.aspx</link><description>I am one of those people who tends to have multiple instances of multiple browsers open at any given time, usually with several tabs open in each instance:&lt;br /&gt;&lt;br /&gt;&lt;img src="http://www.mikepope.com/blog/images/Taskbar1.png" width='691' height='30' /&gt; &lt;br /&gt;&lt;br /&gt;In this way I often manage to confuse myself -- I'll Alt+Tab between browsers, hunting around for a page I was sure I had open. Which it is, just not in the current tab. (A side effect of this is that sometimes I'll just open another instance of the same page.) &lt;br /&gt;&lt;br /&gt;So simply &lt;em&gt;getting&lt;/em&gt; to an open Web page can occasionally be confounding. But even once I've managed to find my way to the right page, using a Web application can be a challenge. I've noticed this particularly with Facebook, in the form of people having all sorts of trouble figuring out how to post photos, write on walls, etc. Two reasons, I think. The first is that a lot of people use Facebook who are not 24/7 computer users and are not used to (good for them) doing the sort of poking around that seems to be required. The second reason is that Facebook's layout kind of sucks.&lt;br /&gt;&lt;br /&gt;Here's a typical experience, in pictures! First I need to find my way to Facebook. Note the many choices that just the browser presents here:&lt;br /&gt;&lt;br /&gt;&lt;img src="http://www.mikepope.com/blog/images/WebPageChoices_Mask1_70.png" width='661' height='308' /&gt;&lt;br /&gt;&lt;br /&gt;1 - Menu&lt;br /&gt;2 - Favorites bar&lt;br /&gt;3 - Tabs&lt;br /&gt;&lt;br /&gt;Now to Facebook itself, which presents me, by default, with no less than 5 menus that I need to navigate in order to accomplish anything other than post a simple entry:&lt;br /&gt;&lt;br /&gt;&lt;img src="http://www.mikepope.com/blog/images/WebPageChoices_Mask2.png" width='665' height='331' /&gt;&lt;br /&gt;&lt;br /&gt;An even worse example is Gmail, which is a mish-mash of links, buttons, and (for variety?) a drop-down list. I count 10 menu-type items, but I suppose it depends on how exactly one wants to count:&lt;br /&gt;&lt;br /&gt; [&lt;a href='http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2137'&gt;more&lt;/a&gt;]</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>technology</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2137</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2137</guid><pubDate>Thu, 04 Jun 2009 10:27:08 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2137">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2137</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2137</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2137</wfw:commentRss><slash:comments>2</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2137</feedburner:origLink></item><item><title>Is college the only path?</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/A4IgWo7088A/DisplayBlog.aspx</link><description>Among people I know, the discussion for the most part is not &lt;em&gt;whether&lt;/em&gt; a kid will go to college, but how this college business is going to be paid for. People start college funds for their toddlers. A college degree is seen as the minimum entry point to a career, or was back when people still talked about careers.&lt;img src="http://www.mikepope.com/blog/images/mortarboard.png" width='186' height='125' style="float:right;margin:10px;"/&gt;&lt;br /&gt;&lt;br /&gt;But between the mania for outsourcing that started in the 90s (or thereabouts) and the current economic downturn, the golden ticket of a college degree is looking a little tarnished.[&lt;a href='#iscollegetheonlypath1'&gt;1&lt;/a&gt;] A person with a pessimistic POV might wonder why we're training all these kids to jump into a job pool that, at least for the moment, seems to be drying up.&lt;br /&gt;&lt;br /&gt;Assuming I'm reading trends correctly, we therefore seem to be undergoing a little bit of a, um, adjustment in how we view the skilled trades. Back in March, the NPR correspondent Adam Davidson appeared on the radio program "This American Life." His mission, he said, was "to save his cousin DJ's life, to make his life better." Save it how? Cousin DJ had &lt;em&gt;dropped out of college&lt;/em&gt;. By dropping out of college, Davidson maintained, you are making a conscious decision "to not partake in the economic growth and possibilities of the coming decade." The program then featured a three-way conversation between Davidson, his cousin DJ, and the economist Pietra Rivoli, whom Davidson had enlisted to help him convince cousin DJ of his folly. &lt;br /&gt;&lt;br /&gt;&lt;img src="http://www.mikepope.com/blog/images/hammers.png" width='127' height='191' style="float:left;margin:10px;"/&gt; [&lt;a href='http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2136'&gt;more&lt;/a&gt;]</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>general,readings</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2136</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2136</guid><pubDate>Wed, 27 May 2009 18:38:23 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2136">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2136</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2136</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2136</wfw:commentRss><slash:comments>2</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2136</feedburner:origLink></item><item><title>More instructions we probably didn't need</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/wfn8BTpGmb0/DisplayBlog.aspx</link><description>From the instructions (!) for a dog collar:&lt;br /&gt;&lt;br /&gt;&lt;img style="border:1px solid black"  src="http://mikepope.com/blog/images/DogCollarInstructions.png" width='496' height='180' /&gt;&lt;br /&gt;&lt;br /&gt;Not evident from this is that the collar does not have a buckle (plastic snap instead) and that there's no "sliver" loop. &lt;br /&gt;&lt;br /&gt;More dubious guidance: &lt;a href="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2125" target="_blank"&gt;1&lt;/a&gt;, &lt;a href="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2087" target="_blank"&gt;2&lt;/a&gt;, &lt;a href="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2071" target="_blank"&gt;3&lt;/a&gt;.</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>writing</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2135</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2135</guid><pubDate>Wed, 27 May 2009 08:13:49 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2135">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2135</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2135</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2135</wfw:commentRss><slash:comments>0</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2135</feedburner:origLink></item><item><title>Magical phrases for search-engine listings?</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/9cNzMZpIRQY/DisplayBlog.aspx</link><description>As with most things, I am several years behind in getting interested in attemtping to, er, "manage" how search engines crawl, weight, and display information from Web pages. I have still not gotten hugely excited about the murky field of search-engine optimization, aka SEO, which is all about trying to make your site as prominent as possible.&lt;br /&gt;&lt;br /&gt;However, I did recently take a passing interest in if and how a body might control what a search engine &lt;em&gt;displays&lt;/em&gt; for a site. I record some observations here largely for my own amusement; I suspect that if you have an interest in gaming search engines, this is all old news. &lt;br /&gt;&lt;br /&gt;So. The default (or perhaps better stated, the fallback) strategy is to display the first real text from the page, which excludes headings and the like. For example, if you search for &lt;a href="http://www.google.com/search?client=firefox-a&amp;rls=org.mozilla%3Aen-US%3Aofficial&amp;channel=s&amp;hl=en&amp;q=asp.net+gridview+control&amp;btnG=Google+Search" target="_blank"&gt;ASP.NET gridview control&lt;/a&gt;, the first hit looks like this:&lt;br /&gt;&lt;br /&gt;&lt;div style="margin-left:50px"&gt;&lt;img src="http://mikepope.com/blog/images/SearchEngineListing1.png" width='418' height='67' /&gt;&lt;/div&gt;&lt;br /&gt;And indeed, when one looks at the &lt;a href="http://www.devx.com/dotnet/Article/22141" target="_blank"&gt;article&lt;/a&gt; in question, it starts off with that very text:&lt;br /&gt;&lt;br /&gt;&lt;div style="margin-left:50px"&gt;&lt;img src="http://mikepope.com/blog/images/SearchEngineListing2.png" width='558' height='276' /&gt;&lt;/div&gt;&lt;br /&gt;I say "fallback" because there are other ways to establish search-engine listing text that take precedence. A well-known one is to set the description meta tag and specify the &lt;code&gt;content&lt;/code&gt; attribute, like this:&lt;br /&gt;&lt;br /&gt;&lt;code&gt;&amp;lt;meta name="Description" content="ASP.NET technical editor writes about coding, writing, editing, and more."&amp;gt;&lt;/code&gt;&lt;br /&gt;&lt;br /&gt; [&lt;a href='http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2134'&gt;more&lt;/a&gt;]</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>technology</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2134</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2134</guid><pubDate>Tue, 26 May 2009 22:16:55 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2134">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2134</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2134</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2134</wfw:commentRss><slash:comments>0</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2134</feedburner:origLink></item><item><title>Sign(s) o' the Times</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/14YYdbte3Z4/DisplayBlog.aspx</link><description>This is by a condo complex not far from where I live.&lt;br /&gt;&lt;br /&gt;&lt;img src="http://www.mikepope.com/blog/images/RealEstateSigns.png" width='757' height='420' /&gt;&lt;br /&gt;&lt;br /&gt;</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>general</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2133</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2133</guid><pubDate>Mon, 25 May 2009 15:08:10 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2133">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2133</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2133</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2133</wfw:commentRss><slash:comments>1</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2133</feedburner:origLink></item><item><title>Wolfram|Alpha</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/TxxKBPqSTck/DisplayBlog.aspx</link><description>Have you played with &lt;a href="http://www.wolframalpha.com/" target="_blank"&gt;Wolfram|Alpha&lt;/a&gt; yet? Fun. Here's their own description:&lt;blockquote&gt;[A]n ambitious, long-term project to make all systematic knowledge immediately computable by anyone.  You enter your question or calculation, and Wolfram|Alpha uses its built-in algorithms and growing collection of data to compute the answer. &lt;/blockquote&gt;There's a &lt;a href="http://www.wolframalpha.com/screencast/introducingwolframalpha.html" target="_blank"&gt;screencast&lt;/a&gt; by Mr. Alpha himself (kidding. It's by Mr. Wolfram) that shows a lot of cool stuff of what the site can do, showing examples from math, chemistry, currency, geography, etc.&lt;br /&gt;&lt;br /&gt;The parser is pretty good, but it isn't hard to stump it. In my case, it was a case of using syntax it understood. So, for example, I started with this:&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;&lt;code&gt;day of week Feb 19 1957&lt;/code&gt;&lt;/strong&gt;&lt;br /&gt;&lt;br /&gt;W|A didn't like it:&lt;br /&gt;&lt;br /&gt;&lt;div style="margin-left:50px"&gt;&lt;img src="http://www.mikepope.com/blog/images/WolframAlphaError1.png" width='482' height='392' /&gt;&lt;/div&gt;&lt;br /&gt;I tried &lt;strong&gt;&lt;code&gt;2/19/1957 day of week&lt;/code&gt;&lt;/strong&gt; and got this:&lt;br /&gt;&lt;br /&gt;&lt;div style="margin-left:50px"&gt;&lt;img src="http://www.mikepope.com/blog/images/WolframAlphaError2.png" width='472' height='500' /&gt;&lt;/div&gt;&lt;br /&gt;But it did like &lt;strong&gt;&lt;code&gt;Feb 19 1957 day&lt;/code&gt;&lt;/strong&gt;:&lt;br /&gt;&lt;br /&gt;&lt;div style="margin-left:50px"&gt;&lt;img src="http://www.mikepope.com/blog/images/WolframAlphaSuccess.png" width='471' height='428' /&gt;&lt;/div&gt;&lt;br /&gt;(There's a lot more below this on the actual screen, I just cut it off for space.)&lt;br /&gt;&lt;br /&gt;It does music, too, so I played around to see if I could type in a succession of notes and have it tell me what chord they make up. I initially tried &lt;strong&gt;&lt;code&gt;c&amp;nbsp;eb&amp;nbsp;g&amp;nbsp;c&lt;/code&gt;&lt;/strong&gt;, but W|A parsed it as multiplication calculation:&lt;br /&gt;&lt;br /&gt;&lt;div style="margin-left:50px"&gt;&lt;img src="http://www.mikepope.com/blog/images/WolframAlphaNotes1.png" width='268' height='109' /&gt;&lt;/div&gt;&lt;br /&gt; [&lt;a href='http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2132'&gt;more&lt;/a&gt;]</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>technology</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2132</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2132</guid><pubDate>Mon, 18 May 2009 21:57:02 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2132">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2132</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2132</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2132</wfw:commentRss><slash:comments>0</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2132</feedburner:origLink></item><item><title>This keyboard shortcut requires the mouse</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/1iy7CJq_l3w/DisplayBlog.aspx</link><description>Bil Simser &lt;a href="http://weblogs.asp.net/bsimser/archive/2009/05/13/internet-explorer-keyboard-shortcuts.aspx?" target="_blank"&gt;spots&lt;/a&gt; a problem in the Internet Explorer online Help:&lt;br /&gt;&lt;br /&gt;&lt;img src="http://www.mikepope.com/blog/images/IE8_KeyboardShortcuts.png" width='462' height='521' /&gt;&lt;br /&gt;&lt;br /&gt;I had a look, and this (or similar text) appears in the Help for IE 6, IE7, and IE8. (The example above is from IE 8.)[&lt;a href='#1'&gt;1&lt;/a&gt;]&lt;br /&gt;&lt;br /&gt;Simser comments: "Reading this just makes me wonder if anyone proofs this stuff. Fail."&lt;br /&gt;&lt;br /&gt;I am hypersensitive to issues like this for a couple of reasons. One is that errors in the documentation annoy people. Even this small error has a disproportionate effect on how the Help system is perceived.&lt;br /&gt;&lt;br /&gt;Another issue is that Simser specifically impugns (correctly) editors. This concerns me because the overall trend -- in newspapers, in technical writing, everywhere -- is to get by with less editing. Various reasons are proposed for this, but one of them is that the general quality of writing on the Web has lowered the bar for what people will accept. Perhaps it's true that readers are willing to wade through subexcellent writing on a blog post that addresses a technical issue of particular concern to them. But it seems clear from this one example, anyway, that people continue to have high expectations for the accuracy of official documentation. &lt;br /&gt;&lt;br /&gt;Hat tip: Michael B.&lt;br /&gt;&lt;br /&gt;&lt;span class='footnote'&gt;&lt;a name='1'&gt;[1]&lt;/a&gt; It is conceivable that by "click", the Help authors meant "press Enter," which works. If that's so, however, a) it's not clear and b) they do use the word ENTER elsewhere, so this is confusing at best.&lt;/span&gt;</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>writing,editing</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2131</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2131</guid><pubDate>Sun, 17 May 2009 10:19:44 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2131">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2131</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2131</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2131</wfw:commentRss><slash:comments>4</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2131</feedburner:origLink></item><item><title>Loquerisne linguam latinam?</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/AO12z6V38os/DisplayBlog.aspx</link><description>Quick, &lt;em&gt;without looking it up,&lt;/em&gt; tell us what the following literally stand for:&lt;br /&gt; &lt;br /&gt;&lt;img src="http://www.mikepope.com/blog/images/OxfordLatinDictionary.png" width='99' height='130' style="float:right;margin:4px;"&gt;i. e.&lt;br /&gt;e. g.&lt;br /&gt;etc.&lt;br /&gt; &lt;br /&gt;... and then tell us what those words mean.&lt;br /&gt; &lt;br /&gt;Ok, smart guy, maybe you know all these, but does everyone? (Like people who read anything you write?) I'm going to guess no. &lt;br /&gt;&lt;br /&gt;Our style guide at work (&lt;a href="http://en.wikipedia.org/wiki/Microsoft_Manual_of_Style_for_Technical_Publications" target="_blank"&gt;MSTP&lt;/a&gt;) has a strong bias against Latin terms that are, you know, still in Latin. They recommend that we don't use Latin if there's a common English equivalent. MSTP: " ... even if you think they are generally known and understood."&lt;br /&gt; &lt;br /&gt;Thus:&lt;br /&gt; &lt;br /&gt;&lt;em&gt;i.e.&lt;/em&gt; (&lt;em&gt;id est&lt;/em&gt;) = that is &lt;br /&gt;&lt;em&gt;e.g.&lt;/em&gt; (&lt;em&gt;exempli gratia&lt;/em&gt;, "for the sake of example") = for example &lt;br /&gt;&lt;em&gt;ergo&lt;/em&gt; = therefore &lt;br /&gt;&lt;em&gt;etc.&lt;/em&gt; (&lt;em&gt;et cetera,&lt;/em&gt; "and the rest")  = and so on[&lt;a href='#loquerisnelinguamlatinam1'&gt;1&lt;/a&gt;]&lt;br /&gt;&lt;em&gt;via&lt;/em&gt; = through, by&lt;br /&gt;&lt;em&gt;de facto&lt;/em&gt; ("from the fact") = real, actual&lt;br /&gt;&lt;strike&gt;&lt;em&gt;exit&lt;/em&gt; ("he/she leaves") = leave, stop, quit, close &lt;/strike&gt; &lt;strong&gt;Update&lt;/strong&gt;: See comments.&lt;br /&gt; &lt;br /&gt;... and, um, etc. So to speak.&lt;br /&gt; &lt;br /&gt;Sticking with English has multiple benefits. One is that ESL readers don't have to rassle with weirdo academese when reading the docs.[&lt;a href='#loquerisnelinguamlatinam2'&gt;2&lt;/a&gt;] A second one is that even a lot of English-language writers can't seem to keep &lt;em&gt;i.e.&lt;/em&gt; and &lt;em&gt;e.g.&lt;/em&gt; straight (why? &lt;em&gt;Coz it's a frickin' foreign language&lt;/em&gt;), and not using those terms neatly bypasses that particular problem.&lt;br /&gt; &lt;br /&gt;&lt;img src="http://www.mikepope.com/blog/images/HabeasCorpus.png" width='210' height='136' style="float:left;margin:8px;"&gt;Of course, there are some, haha, bona fide[&lt;a href='#loquerisnelinguamlatinam3'&gt;3&lt;/a&gt; [&lt;a href='http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2130'&gt;more&lt;/a&gt;]</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>writing,language</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2130</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2130</guid><pubDate>Sat, 16 May 2009 15:18:46 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2130">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2130</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2130</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2130</wfw:commentRss><slash:comments>3</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2130</feedburner:origLink></item><item><title>Why &lt;i&gt;not&lt;/i&gt; link to Wikipedia?</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/xkxKdZ0xTp0/DisplayBlog.aspx</link><description>An issue that has come up a number of times at work is the question of linking to articles in Wikipedia. It's not terribly unusual for us to link from the documentation set to non-Microsoft resources. A common example in my world is linking to the W3C site. For example, in the topic (article) &lt;a href="http://msdn.microsoft.com/en-us/library/exc57y7e.aspx" target="_blank"&gt;ASP.NET and XHTML&lt;/a&gt;, we discuss how we implement (or don't) XHTML standards, but we refer you to the W3C site for actual standards.&lt;br /&gt;&lt;br /&gt;Other examples where we've linked to external sites:&lt;ul&gt;&lt;li&gt;The &lt;a href="http://www.section508.gov/" target="_blank"&gt;Section 508&lt;/a&gt; site for information about accessibility.&lt;br /&gt;&lt;li&gt;The &lt;a href="http://www.iana.org/assignments/media-types/" target="_blank"&gt;IANA site&lt;/a&gt; for a reference of MIME types.&lt;br /&gt;&lt;li&gt;The &lt;a href="https://developer.mozilla.org/en/Gecko_DOM_Reference" target="_blank"&gt;Mozilla developer site&lt;/a&gt; for information about the document object model (DOM) supported in the Gecko browser rendering engine.&lt;br /&gt;&lt;li&gt;The &lt;a href="http://www.unicode.org/" target="_blank"&gt;Unicode site&lt;/a&gt; for (duh) information about Unicode.&lt;/ul&gt;There are more, but you get the idea. The thought here is that these sites provide information that is not specific to our product but that is useful to our audience. It would be silly for us to copy this info or (god forbid) rewrite it so it could be part of our documentation site.&lt;br /&gt;&lt;br /&gt;&lt;img src="http://www.mikepope.com/blog/images/expertquality.png" width='95' height='168' align="right" style="margin:10px;"/&gt;You will probably note that sites have certain features in common. They are:&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Authoritative&lt;/strong&gt;. Many of our links are to the sites of standards bodies.&lt;br /&gt;&lt;li&gt;&lt;strong&gt;Commercially neutral&lt;/strong&gt;, at least for the purposes for which we are linking. For example, the Mozilla site could be thought of as a competitor to, say, Internet Explorer, but from our perspective (server-based Web coding), it's just another client. &lt;br /&gt;&lt;li&gt;&lt;strong&gt; [&lt;a href='http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2129'&gt;more&lt;/a&gt;]</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>writing,aspnet,editing</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2129</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2129</guid><pubDate>Thu, 07 May 2009 22:07:40 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2129">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2129</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2129</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2129</wfw:commentRss><slash:comments>2</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2129</feedburner:origLink></item><item><title>The many dimensions of fasteners</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/fXIkAN2fUgY/DisplayBlog.aspx</link><description>I’m going to propose to you that each of the items in the following picture is an eight-dimensional object:&lt;br /&gt;&lt;br /&gt;&lt;img src="http://www.mikepope.com/blog/images/Screws_bw_40.png" width='320' height='215' /&gt;&lt;br /&gt;&lt;br /&gt;Eight? Yes. Or more. Or fewer. It all depends. &lt;br /&gt;&lt;br /&gt;Of course, I’m screwing with you. (haha, get it?) I'm using a mathematical definition of dimensions: In Cartesian terms, an object's dimension is "correlated with the number of coordinates that is required to map it."[&lt;a href='#themanydimensionsoffasteners1'&gt;1&lt;/a&gt;]  It seems probable that when Descartes was inventing analytic geometry, he did not realize that he could have been analyzing a problem I've been having with coffee cans. Which I'll get to in a moment.&lt;br /&gt;&lt;br /&gt;So, eight dimensions? Here are eight attributes/characteristics/coordinates/dimensions to identify this object uniquely:&lt;br /&gt;&lt;br /&gt;&lt;div style="margin-left:50px"&gt;&lt;table&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Fastener type&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;screw&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Category&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;machine screw&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Drive type&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Philips&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Length&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;3/4"&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Diameter/Gauge&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;#8&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Thread count[&lt;a href='#themanydimensionsoffasteners2'&gt;2&lt;/a&gt;]/pitch&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;32&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Material&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Zinc-plated steel&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Head style&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;pan&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&lt;/div&gt;&lt;br /&gt;Go on down to the hardware store and take a stroll through the eponymously labeled Hardware department. Screws, nuts, bolts, washers, pins, nails, anchors ... this department consists of a very large number of small boxes. The boxes are grouped by the categories listed above, and probably several more, like measuring system (US or metric)[&lt;a href='#themanydimensionsoffasteners3'&gt;3&lt;/a&gt; [&lt;a href='http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2128'&gt;more&lt;/a&gt;]</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>general,personal</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2128</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2128</guid><pubDate>Sun, 03 May 2009 22:50:16 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2128">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2128</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2128</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2128</wfw:commentRss><slash:comments>3</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2128</feedburner:origLink></item><item><title>Tweeting Twitter</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/h2Xqj73dYA0/DisplayBlog.aspx</link><description>Social applications need to hit some sort of critical mass for success. In 2006, it was blogs. This year it's Twitter.&lt;br /&gt;&lt;br /&gt;You know a phenom has gone mainstream when it reaches Business Week (&lt;a href="http://tinyurl.com/58x9gz" target="_blank"&gt;http://tinyurl.com/58x9gz&lt;/a&gt;) and Forbes (&lt;a href="http://tinyurl.com/cy55ka" target="_blank"&gt;http://tinyurl.com/cy55ka&lt;/a&gt;).&lt;br /&gt;&lt;br /&gt;"Twitter is the stupidest application you’re ever going to see." &lt;a href="http://tinyurl.com/bx3g4q" target="_blank"&gt;http://tinyurl.com/bx3g4q&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;Why is Twitter hard for people to grasp? Maybe they describe themselves all wrong: &lt;a href="http://tinyurl.com/cmatvh" target="_blank"&gt;http://tinyurl.com/cmatvh&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;Twitter asks "What are you doing?" Wrong question. Better: "What has your attention?" (I forget who said that, sorry.)&lt;br /&gt;&lt;br /&gt;What to tweet? News, articles, pithy observations, commentary. NOT your lunch. Unless you want to.&lt;br /&gt;&lt;br /&gt;Who to follow? Friends, colleagues, "influencers." Follow the most interesting of your follows' follows and followers.&lt;br /&gt;&lt;br /&gt;Some people tweet minor things but blog major things. Some people preview blog entries with tweets. &lt;br /&gt;&lt;br /&gt;From the perspective of size and currency, Tweeting is to blogging what IM is to email. (?) &lt;br /&gt;&lt;br /&gt;140 characters is a useful limit. Sometimes challenging to meet. More space would not produce better tweets, imo.&lt;br /&gt;&lt;br /&gt;Twitter really put URL "tinification" on the map. &lt;a href="http://tinyurl.com/decd5s" target="_blank"&gt;http://tinyurl.com/decd5s&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Twitter v Facebook: Facebook is closed (you approve your circle), Twitter is wide (wide, wide) open. &lt;br /&gt;&lt;br /&gt;Twitter descriptions don't convey that it's like conversation. Follow; join if you like. It's a party! (As in life, some talk too much.)&lt;br /&gt;&lt;br /&gt;Twitter: community, community, community, community. :-)&lt;br /&gt;&lt;br /&gt;Sarah says reading Twitter is like watching the news crawl at the bottom of the TV screen. Except you can jump in and add your own.&lt;br /&gt; [&lt;a href='http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2127'&gt;more&lt;/a&gt;]</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>technology</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2127</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2127</guid><pubDate>Wed, 15 Apr 2009 12:11:44 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2127">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2127</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2127</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2127</wfw:commentRss><slash:comments>0</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2127</feedburner:origLink></item><item><title>Teh taxonomy of typo's </title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/WrUCca6Z4Hc/DisplayBlog.aspx</link><description>I've been soliciting thoughts about blogging from various people, and one of the questions I ask has to do with how important it is that you get all the spelling right. People sort of agree that email and blog writing is in general held to a lesser standard than production writing, but they also sort of agree that spelling errors detract from the text, even so. This was &lt;a href="http://www.hanselman.com/blog/DoesSpellingMatterIThinkItDoes.aspx" target="_blank"&gt;stated&lt;/a&gt; most succinctly by Scott Hanselman about his blog: "Hopefully folks don't think TOO poorly of me when I misspell words. Of course, I think horribly of YOU when YOU misspell." Or as John Scalzi once &lt;a href="http://whatever.scalzi.com/2006/02/12/writing-tips-for-non-writers-who-dont-want-to-work-at-writing/" target="_blank"&gt;wrote&lt;/a&gt; "Here's a good rule of thumb: For every spelling error you make, your apparent IQ drops by 5 points."&lt;br /&gt;&lt;br /&gt;&lt;div style="float:left;padding:10px;"&gt;&lt;img src="http://www.mikepope.com/blog/images/typo_illustration.png" width='163' height='163'/&gt;&lt;br /&gt;[&lt;a href="http://libizblog.wordpress.com/2008/02/13/but-your-past-experience-reads-chef-executive/" target="_blank"&gt;credit&lt;/a&gt;]&lt;/div&gt;It never hurts to spell correctly 100% of the time. I was thinking about Scalzi's observation, though, and I realized that it's more subtle than that. I decided that there is a kind of taxonomy of typos, and my reaction to a typo depends on what type of misspelling I encounter. Here's what I've come up with so far:&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;1. Mechanical.&lt;/strong&gt; Typos that result from simple fumbles. You obviously know how to spell the word, but got it wrong in haste: &lt;em&gt;teh&lt;/em&gt; or &lt;em&gt;alreayd&lt;/em&gt;; more generally, transposed letters or missing spaces. (Another way to characterize these might be that they're typos that Word's auto-correct feature would catch and fix.)&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;2. Language mastery.&lt;/strong&gt; Typos that confuse words where you should ("should") know better. This includes &lt;em&gt;its/it's&lt;/em&gt;, &lt;em&gt;their/there/they're&lt;/em&gt; [&lt;a href='http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2126'&gt;more&lt;/a&gt;]</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>writing</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2126</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2126</guid><pubDate>Mon, 06 Apr 2009 14:25:58 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2126">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2126</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2126</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2126</wfw:commentRss><slash:comments>7</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2126</feedburner:origLink></item><item><title>More instructions we probably didn't need</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/aRTtGDqmFk0/DisplayBlog.aspx</link><description>From the instructions for the &lt;a href="http://www.smarthome.com/9034/Kill-A-Watt-P4400/p.aspx" target="_blank"&gt;Kill A Watt EZ&lt;/a&gt; electric-power usage meter:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;img style="border:1px solid black" src="http://www.mikepope.com/blog/images/KillAWattEZ_Instructions.png" width='562' height='107' /&gt;&lt;br /&gt;</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>writing</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2125</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2125</guid><pubDate>Sat, 04 Apr 2009 22:33:38 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2125">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2125</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2125</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2125</wfw:commentRss><slash:comments>0</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2125</feedburner:origLink></item><item><title>DIY (almost) guitar setup</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/I3Y-vk5ZYtk/DisplayBlog.aspx</link><description>This post is strictly about guitar setup; for those who care naught for guitar mechanics, nothing here to see. Catch you next time.&lt;br /&gt;&lt;br /&gt;I had an interesting guitar setup experience recently. If you have even moderate experience with guitar setup, this will probably all be old hat. (And if you have none, you probably don't care. So who's reading? Hmmm.)&lt;br /&gt;&lt;br /&gt;I got my electric a year and some ago. It's a knockoff of a Gibson ES-330:&lt;br /&gt;&lt;br /&gt;&lt;a target="_blank" href="http://www.mikepope.com/blog/images/BlackGuitar.jpg"&gt;&lt;img src="http://www.mikepope.com/blog/images/BlackGuitar2_sm.jpg" width="140" height="280" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I like it fine. As I got it, it had some relatively high-gauge strings (11s, probably). Being new to electric, I had nothing to go by, so I used that guitar as-is. I had a setup done at one point, but didn't have it restrung. During one of my lessons, tho, we were talking about bending, and my teacher had a go on my guitar. "Lighter strings, dang!" was his recommendation, so I had one of the shop guys put on some lighter ones (10). It was sort of a rush job, which more-or-less explains the rest.&lt;br /&gt;&lt;br /&gt;The lighter strings were a definite plus. However, it seemed to me that the guitar had developed a slight buzz. (This is where the experienced folks say "duh.") I kept thinking I should take it in for another setup, but didn't get around to it.&lt;br /&gt;&lt;br /&gt;One night, tho, I was at guitar school (not to be confused with lessons), and the owner dude (Jay) introduced Ryan, a new guy they had. Ryan was a guitar builder, Jay said, and was open for business. Specifically, you could bring him your guitar for repair or whatever. It was the same price as taking the guitar to a shop, but -- the cool part -- you could watch and, if you wanted, Ryan would teach you to do what he was doing. &lt;br /&gt;&lt;br /&gt; [&lt;a href='http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2124'&gt;more&lt;/a&gt;]</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>music,technology</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2124</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2124</guid><pubDate>Fri, 03 Apr 2009 00:07:27 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2124">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2124</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2124</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2124</wfw:commentRss><slash:comments>2</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2124</feedburner:origLink></item><item><title>Blog feed changes</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/qDWKM-dCKPs/DisplayBlog.aspx</link><description>What started as a simple request from Phil -- use fully qualified URLs for images -- turned, naturally, into something a bit more. I fixed the feed, then needed to update the feed URL in Feedburner, which led to moving the feed to Google (which bought Feedburner), which led to an error, which led to some further tweaking of the actual feed. &lt;br /&gt;&lt;br /&gt;Anyway. If I broke your feed, let me know. PS Sorry if so. &lt;br /&gt;&lt;br /&gt;One URL that should always work is this:&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.mikepope.com/blog/blogfeed.rss" target="_blank"&gt;http://www.mikepope.com/blog/blogfeed.rss&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;or this:&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.mikepope.com/blog/blogfeed.rss?full=true" target="_blank"&gt;http://www.mikepope.com/blog/blogfeed.rss?full=true&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;if you want full entries in the feed.&lt;br /&gt;&lt;br /&gt;But of course that does not go through a subscription service. </description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>blog</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2123</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2123</guid><pubDate>Tue, 31 Mar 2009 23:26:22 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2123">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2123</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2123</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2123</wfw:commentRss><slash:comments>0</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2123</feedburner:origLink></item><item><title>HP support: "What, haven't you given up &lt;i&gt;yet?&lt;/i&gt;"</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/GuSL-W5JHRE/DisplayBlog.aspx</link><description>I work for a company that's often accused of having evil intentions. If it does, that doesn't manifest at my level: we &lt;em&gt;obsess&lt;/em&gt; about trying to do the right thing for customers, even if we don't necessarily achieve this to the level of everyone's satisfaction. As but one example in my little world, we really do go to extreme lengths to try to be sure that our text is a) readily translatable into multiple languages and b) comprehensible to non-native speakers who do choose to read it in English. (More on that in the near future.)&lt;br /&gt;&lt;br /&gt;&lt;img src="http://www.mikepope.com/blog/images/HearNoEvil.gif" width='194' height='140' style="float:right;padding:8px;"/&gt;What brings this to mind is an ongoing, um, discussion that I've been having with the customer service (I did not actually write customer "service," although I was tempted to) at HP. I bought an HP Pavilion[&lt;a href='#hpsupportwhathaventyougiveupyet1'&gt;1&lt;/a&gt;] a couple of months ago for work stuff. I specifically wanted a multi-&lt;strike&gt;processor&lt;/strike&gt;core box that had lotsa-lotsa RAM because I want to run Vista 64-bit on it. The computer actually came with Vista Home 64-bit. Begone, said I. I flattened the box, loaded Vista Ultimate 64-bit, and began configuring it with goodies like Virtual PC.&lt;br /&gt;&lt;br /&gt;A couple of weeks after I got the box, it refused to boot. After some diagnostics and some hardware switcheroo, I determined that I had one bad bank (2GB) of RAM. With that block of RAM in it, the machine froze; when I removed the memory unit, all was fine except, of course, that I was short 2GB of RAM. &lt;br /&gt;&lt;br /&gt;I contacted (via chat) HP support. After about an hour of highly intermittent chatting, I was instructed to do what I had already done (test all the bits of RAM). This was interspersed with crap like "Don’t worry I will help you" and "I will pull up the records and resolve the issue."&lt;br /&gt;&lt;br /&gt; [&lt;a href='http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2122'&gt;more&lt;/a&gt;]</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>general,technology</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2122</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2122</guid><pubDate>Tue, 31 Mar 2009 15:07:25 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2122">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2122</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2122</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2122</wfw:commentRss><slash:comments>5</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2122</feedburner:origLink></item><item><title>Sign o' the Times</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/cLJ_hi-vpGY/DisplayBlog.aspx</link><description>Just got back from vacation. Here's something we saw in Chicago:&lt;br /&gt;&lt;br /&gt;&lt;img src="http://www.mikepope.com/blog/images/WaMuSign.jpg" width='638' height='319' /&gt;</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>general</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2121</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2121</guid><pubDate>Tue, 31 Mar 2009 08:46:09 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2121">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2121</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2121</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2121</wfw:commentRss><slash:comments>4</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2121</feedburner:origLink></item><item><title>In case of missing child, consult Pub. 501</title><link>http://feedproxy.google.com/~r/mikepope/wAZr/~3/M2duS2kcZJw/DisplayBlog.aspx</link><description>Ok, this is the weirdest thing we've found (so far) in the &lt;a href="http://www.irs.gov/pub/irs-pdf/i1040ez.pdf" target="_blank"&gt;IRS publications for 2008 taxes&lt;/a&gt;:&lt;blockquote&gt;&lt;strong&gt;Parent of a Kidnapped Child&lt;/strong&gt;&lt;br /&gt;The parent of a child who is presumed by law enforcement authorities to have been  kidnapped by someone who is not family member may be able to take the child into account in determining his or her eligibility for the head of household or qualifying widow(er) filing status, deduction for dependents, child tax credit, and the earned income credit (EIC). But you have to file Form 1040 or Form 1040A to take the child into account to claim these benefits. For details, see Pub. 501 (Pub. 596 for the EIC).&lt;/blockquote&gt;Don't get me wrong, this is a tragedy. But does the IRS get so many questions about this that they need to include this note in the instructions for the 1040EZ form? Odd.</description><author>Mike Pope&lt;mike@mikepope.com&gt;</author><category>writing</category><wfw:comment>http://www.mikepope.com/blog/AddComment.aspx?blogID=2120</wfw:comment><guid isPermaLink="false">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2120</guid><pubDate>Sun, 22 Mar 2009 22:17:20 GMT</pubDate><source url="http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2120">http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2120</source><trackback:ping>http://www.mikepope.com/blog/BlogTrackback.aspx?id=2120</trackback:ping><wfw:commentRss>http://www.mikepope.com/blog/BlogCommentsFeed.rss?id=2120</wfw:commentRss><slash:comments>1</slash:comments><feedburner:origLink>http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=2120</feedburner:origLink></item></channel></rss>
