This feed does not validate.

In addition, interoperability with the widest range of feed readers could be improved by implementing the following recommendation.


  1. <br />
  2. <b>Warning</b>:  Creating default object from empty value in <b>/home/helpstuf/public_html/blog/b2evocore/_class_settings.php</b> on line <b>36</b><br />
  3. <br />
  4. <b>Warning</b>:  Creating default object from empty value in <b>/home/helpstuf/public_html/blog/b2evocore/_class_settings.php</b> on line <b>36</b><br />
  5. <br />
  6. <b>Warning</b>:  Creating default object from empty value in <b>/home/helpstuf/public_html/blog/b2evocore/_class_settings.php</b> on line <b>36</b><br />
  7. <br />
  8. <b>Warning</b>:  Creating default object from empty value in <b>/home/helpstuf/public_html/blog/b2evocore/_class_settings.php</b> on line <b>36</b><br />
  9. <br />
  10. <b>Warning</b>:  Creating default object from empty value in <b>/home/helpstuf/public_html/blog/b2evocore/_class_settings.php</b> on line <b>36</b><br />
  11. <br />
  12. <b>Warning</b>:  Creating default object from empty value in <b>/home/helpstuf/public_html/blog/b2evocore/_class_settings.php</b> on line <b>36</b><br />
  13. <br />
  14. <b>Warning</b>:  Creating default object from empty value in <b>/home/helpstuf/public_html/blog/b2evocore/_class_settings.php</b> on line <b>36</b><br />
  15. <br />
  16. <b>Warning</b>:  Creating default object from empty value in <b>/home/helpstuf/public_html/blog/b2evocore/_class_settings.php</b> on line <b>36</b><br />
  17. <br />
  18. <b>Warning</b>:  Creating default object from empty value in <b>/home/helpstuf/public_html/blog/b2evocore/_class_settings.php</b> on line <b>36</b><br />
  19. <br />
  20. <b>Warning</b>:  Creating default object from empty value in <b>/home/helpstuf/public_html/blog/b2evocore/_class_settings.php</b> on line <b>36</b><br />
  21. <br />
  22. <b>Warning</b>:  Creating default object from empty value in <b>/home/helpstuf/public_html/blog/b2evocore/_class_settings.php</b> on line <b>36</b><br />
  23. <br />
  24. <b>Warning</b>:  Creating default object from empty value in <b>/home/helpstuf/public_html/blog/b2evocore/_class_settings.php</b> on line <b>36</b><br />
  25. <br />
  26. <b>Warning</b>:  Creating default object from empty value in <b>/home/helpstuf/public_html/blog/b2evocore/_class_settings.php</b> on line <b>36</b><br />
  27. <br />
  28. <b>Warning</b>:  Creating default object from empty value in <b>/home/helpstuf/public_html/blog/b2evocore/_class_settings.php</b> on line <b>36</b><br />
  29. <br />
  30. <b>Warning</b>:  Creating default object from empty value in <b>/home/helpstuf/public_html/blog/b2evocore/_class_settings.php</b> on line <b>36</b><br />
  31. <br />
  32. <b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /home/helpstuf/public_html/blog/b2evocore/_class_settings.php:36) in <b>/home/helpstuf/public_html/blog/xmlsrv/atom.php</b> on line <b>21</b><br />
  33. <?xml version="1.0" encoding="utf-8"?><feed version="0.3" xml:lang="en-US" xmlns="">
  34. <title>helpstuff blog</title>
  35. <link rel="alternate" type="text/html" href="" />
  36. <tagline>helpstuff blog</tagline>
  37. <generator url="" version="">b2evolution</generator>
  38. <modified>2009-01-07T04:17:24Z</modified>
  39. <entry>
  40. <title type="text/plain" mode="xml">JTF Associates announces TechComm Toolbox!</title>
  41. <link rel="alternate" type="text/html" href="" />
  42. <author>
  43. <name>Char</name>
  44. </author>
  45. <id></id>
  46. <issued>2009-01-07T04:17:24Z</issued>
  47. <modified>2009-01-07T04:17:24Z</modified>
  48. <content type="text/html" mode="escaped"><![CDATA[<p><a href=""></a></p> <p>After months (years?) of seeing people asking "what tools do you use for" authoring/editing/indexing/graphics and so on, JTF Associates is pleased to announce <a href="">TechComm Toolbox</a>.</p>
  49. <p>TCT provides a searchable database of entries organized by categories and alphabetically. And everyone is welcome to submit entries for tools not currently listed.</p>
  50. <p>In addition, consultants and trainers are welcome to submit themselves.</p>
  51. <p>All tools are listed for no charge, with the company name and a link to the appropriate website page. Companies can advertise on TCT by adding blurbs, logos, or both to their listing. In addition, sponsored ads are available on each page.</p>
  52. <p>Visit <a href="">TechComm Toolbox</a> today!
  53. </p>
  54. ]]></content>
  55. </entry>
  56. <entry>
  57. <title type="text/plain" mode="xml">Six Word Resume Meme (from WWDS)</title>
  58. <link rel="alternate" type="text/html" href="" />
  59. <author>
  60. <name>Char</name>
  61. </author>
  62. <id></id>
  63. <issued>2008-12-30T23:37:03Z</issued>
  64. <modified>2008-12-30T23:37:03Z</modified>
  65. <content type="text/html" mode="escaped"><![CDATA[<p><a href=""></a></p> <p>So over at "What Would Dad Say", GL Hoffman (author of <em>Dig Your Job: Keep it or Find a New One</em>) has asked readers to post their six-word resumes. By 1 January 2009.</p>
  66. <p>With no time to waste, here's mine:</p>
  67. <p><strong>Connecting social media and user assistance.</strong> (I think it could have more "punch"...I'll have to work on that.)</p>
  68. <p>(My personal six-word meme is <strong>Playing the hand I was dealt.</strong>)</p>
  69. <p>What are your six-word memes?</p>
  70. ]]></content>
  71. </entry>
  72. <entry>
  73. <title type="text/plain" mode="xml">Get ready for First Night Boston!</title>
  74. <link rel="alternate" type="text/html" href="" />
  75. <author>
  76. <name>Char</name>
  77. </author>
  78. <id></id>
  79. <issued>2008-12-29T03:09:21Z</issued>
  80. <modified>2008-12-29T03:09:21Z</modified>
  81. <content type="text/html" mode="escaped"><![CDATA[<p><a href=""></a></p> <p>We try to get to Boston's First Night every year, at least for a couple of hours. So every year, I go to their <a href="">website</a> to see what's new...</p>
  82. <p>And what's new is that First Night has gone social :-) They have a <a href="">blog</a> (which has actually been around since December 2006) and they're using <a href="">Twitter</a>, too.</p>
  83. <p>(I don't remember seeing the blog in previous years, but the website has undergone a complete update. It's much nicer than what I remember and much better organized. My only complaint is that you have to use Back from the blog to return to the main site. And be sure to click First Night 2009 in the upper left to get to this year's information.)</p>
  84. <p>If you're going to be in the Boston area for New Year's, check out their <a href="">program guide</a>, build an <a href="">itinerary</a> (you have to type your email address to continue), and the rest of their site.</p>
  85. <p>And if you're going to First Night, let me know! Maybe we can meet up somewhere :-)</p>
  86. ]]></content>
  87. </entry>
  88. <entry>
  89. <title type="text/plain" mode="xml">Get User Interface Checklist before the price goes up!</title>
  90. <link rel="alternate" type="text/html" href="" />
  91. <author>
  92. <name>Char</name>
  93. </author>
  94. <id></id>
  95. <issued>2008-12-15T13:02:19Z</issued>
  96. <modified>2008-12-18T15:18:01Z</modified>
  97. <content type="text/html" mode="escaped"><![CDATA[<p><a href=""></a></p> <p>In March 2008, my good friend Rhonda Bracey of CyberText presented <em>Techniques for Reviewing a User Interface</em> at the WritersUA Conference. (It was an awesome presentation and she was then asked to give it at AODC and ASTC (NSW).)</p>
  98. <p>After she got back to the office, she set up a <a href="">page on her website</a> that includes the presentation (through SlideShare and in PDF), a voice recording of the presentation (MP3), handouts (PDF), and a five-page User Interface Checklist (PDF). She has also been offering the checklist in an editable Word version for $4.95USD.</p>
  99. <p>In January, the price of the checklist goes up to $20USD. Get it now and take advantage of the price break! </p>
  100. ]]></content>
  101. </entry>
  102. <entry>
  103. <title type="text/plain" mode="xml">Helping your customers ((i) Inspired by Seth Godin)</title>
  104. <link rel="alternate" type="text/html" href="" />
  105. <author>
  106. <name>Char</name>
  107. </author>
  108. <id></id>
  109. <issued>2008-11-24T20:08:12Z</issued>
  110. <modified>2008-11-28T13:07:13Z</modified>
  111. <content type="text/html" mode="escaped"><![CDATA[<p><a href=""></a></p> <p>"How to answer the phone" was Seth Godin's blog entry today, and this one struck a nerve...not because we make customers go through nine prompts when they call us (we answer the phone if we're here and, amazingly enough, don't answer it when we're not here)...but because lately, it seems like every time I try to help someone out by answering a survey, I'm told after answering two questions that I'm not the target market.</p>
  112. <p>As Seth says, "The only reason to answer the phone when a customer calls is to make the customer happy." In his case, after he finally made it through the nine prompts, he was told that he needed to call back after 10 am. Wouldn't it have been so much better to get that information first?</p>
  113. <p>In my case, someone was researching information on a technical communication subject. No problem...I'm glad to help and I'll take your survey. I click the link and get...</p>
  114. <ul>
  115. <li>Screen 1: Read the quick introduction and click Continue.</li>
  116. <li>Screen 2: A qualifying question (think along the lines of "Do you have green eyes?").</li>
  117. <li>Screen 3: A message ("You do not meet our qualifying criteria.").
  118. </li>
  119. </ul>
  120. <p>I don't have a problem not meeting the criteria. What I <em>do</em> have a problem with is not being told what the criteria are ahead of time. If they had said that they only wanted green-eyed survey takers, I wouldn't have clicked the link.</p>
  121. <p>Now maybe what they wanted to do is get everyone to take their survey so that they know how many non-green-eyed people had applied. (I have no way of knowing if they want to aggregate this information or not.) But if that was part of their goal, they could have asked a couple more questions...maybe "Would you consider wearing green contacts?" or "Does anyone in your house have green eyes?" They should have been able to come up with a few questions so that those of us with eyes of blue or brown or whatever aren't irritated.</p>
  122. <p>Because right now? I am irritated that I was asked to help out when I wasn't the target market. And the next time this company posts a survey, I'll be less likely to help out, which means that they lose my input for future surveys that might apply to blue-eyed people.</p>
  123. <p>I guess you could call this one of my new pet peeves. Do you have any? (We can cover grammar in another post if you'd like!)</p>
  124. ]]></content>
  125. </entry>
  126. </feed>
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda