http://radio.weblogs.com/0103391/categories/myProfession/ Developments and news about clear communication of technical information. en Copyright 2002 Peter Harbeson Thu, 04 Apr 2002 02:47:08 GMT http://backend.userland.com/rss092 peterh@empire.net peterh@empire.net Well, there it is. After using blogger, radio userland, and bbedit to write three different bloggish sites, I've decided I just don't have the time to keep it up; one of them has to go. And since Radio is my least favorite system of the three -- even though it's the most feature-rich -- this one drew the short straw. On the other hand, while I have this extra site, I can use it to try to Google-bomb my Infoliage.com site with the term <a href="http://www.infoliage.com/">technical writer</a>. I wonder, do multiple links at the same site have any effect? <a href="http://www.infoliage.com/">technical writer</a> <a href="http://www.infoliage.com/">technical writer</a> <a href="http://www.infoliage.com/">technical writer</a> <a href="http://www.infoliage.com/">technical writer</a> <a href="http://www.infoliage.com/">technical writer</a> Well <i>that</i> was more fun than it looked! <h3>Technical Communication Darwin Awards</h3> From TecStandards comes the results of the latest <a href="http://www.tecstandards.com/Contest_Information/contest_information.html"><b><i>Bad Manual Contest!</i></b></a> This is great stuff. I've often wished that I had long ago started collecting all the terrible documention I've seen. My "favorite" is the set of graphics in the last honorable mention. Just like seeing the boom microphone in low-budget movie scene. <h4>Notes for instruction</h4> Most of the notes I'm posting here are the kind of notes I take when I'm learning a new piece of software that I need to document. It's a luxury to use software that <i>really works</i> as I do this; in real life most of the software I document isn't nearly done. This is getting a bit more organized; I've been completely through the preferences and categories interfaces, and entered some tweaks. I'm not sure how far I would have been able to get without having experience with Frontier. I hope somebody is writing user documentation for Radio -- or maybe I should just go ahead and do it myself.