<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
<channel>
<title>Blogcritics Author: Mashalpha</title>
<link>http://blogcritics.org/</link>
<description>A sinister cabal of superior bloggers on music, books, film, popular culture, politics, and technology - updated continuously.</description>
<language>en</language>
<copyright>Copyright 2005-2007 by the authors</copyright>
<lastBuildDate>Sat, 9 Jun 2007 14:32:10 EDT</lastBuildDate>
<docs>http://backend.userland.com/rss</docs>
<generator>Blogcritics.org custom software</generator>

<item>
<title>Announcement: Short-content feeds</title>
<link>http://blogcritics.org/</link>
<author>Phillip Winn</author><description>Sunday, August 26, 2007, marks the switch of all Blogcritics.org article feeds from full-content to short-content. This is the result of several converging factors, and is unfortunately a permanent decision (as permanent as any decision can be on the web, that is). We are aware of all of the reasons that this is a Bad Idea, and we are aware that some of you will be quite upset about having to click on something to read the free content, and we&#039;re sorry. Unfortunately, despite great effort, full-content feeds are not currently economically viable.

Two other factors are involved: full-content feeds have resulted in an unprecedented level of content theft, with BC content appearing on many websites, usually spam sites, without attribution or permission. This duplicate content causes a cascading set of problems, not the least of which is that search engines generally aren&#039;t favorable to duplicate content, and don&#039;t always guess correctly. Finally, our RSS advertising partner is strongly in favor of short-content feeds.

We hope that you&#039;ll continue to subscribe to BC via RSS, and when an article grabs your eye, it&#039;s only a click away, still free on the BC website. Thank you for your understanding.</description>
<category>Administration</category><guid isPermaLink="false">0@blogcritics.org</guid>
<pubDate>Sun, 26 Aug 2007 12:00:00 EDT</pubDate>
</item>
<item>
<title>Technology Investment Advice</title>
<link>http://blogcritics.org/archives/2007/06/09/143210.php</link>
<author>Mashalpha</author><description>All to often I&amp;rsquo;ll get a call from a client who asks me if I can do something.  I usually can figure out how to do it, which is one of my specialties because their IT person or programmer or whomever has told them it &amp;ldquo;CAN&amp;rsquo;T BE DONE&amp;rsquo;. Well, when I take care of their problem, it usually causes some issues. Most of the time I have to spend just as much time helping them figure out why their employee said it couldn&amp;rsquo;t be done in the first place. But what I find out may surprise most people and a lot of businesses never do it.I find out that although they may have spent up to $250,000 on their new &amp;ldquo;state of the art&amp;rdquo; software package they barely set aside any time and money for training or they put someone in the position who is woefully under qualified. Often, it isn&amp;rsquo;t all the client&amp;rsquo;s fault.  They have been told by the salesperson that &amp;ldquo;anyone can use it&amp;rdquo;, that it is &amp;ldquo;so simple any one can control it&amp;rdquo;. As any IT administrator knows this is usually said out of fear of telling them the extra costs involved in months of training to use the system and hiring a new person qualified to run this system.  Or it&amp;rsquo;s just the &amp;ldquo;good old boy&amp;rdquo; system, their friend is one of their vendors, and is just a salesperson at best who tells them he is a &amp;ldquo;expert&amp;rdquo; when he is not. In the end, the employee who said it &amp;ldquo;can&amp;rsquo;t be done&amp;rdquo; may be tapped to administer the new system. Their negativity can be traced to a fear of losing their job, of looking incompetent, or they overstated their abilities and are afraid to ask for help. Here are some tips to avoid this pitfall:1.  Always add 10% to 20% of the project cost for training and possibly more for a new position.2.  Test anyone applying for the position even if they are your best employee; see if they are up to the job in a real world environment.3.  If your person does say it can&amp;rsquo;t be done check around see if anyone else has done it.    If so, offer to put your employee in touch with them to see if they could work together and maybe learn something new.  Also, offer to help in anyway; tell them it is alright not to know an answer, that&amp;rsquo;s how one learns.4.  Always get an outside opinion on any project.  All too often everyone has their own agenda.  A consultant only has one agenda:  what is best for his client.5.  Build a high level of trust with your employees; let them know you are open-minded and always willing to provide training for them to grow.  It will help your company grow too.Remember, always include training even for a $100 software program.  If it&amp;rsquo;s new then you&amp;#39;ll want them trained on how to use it.&lt;div id=&quot;authorbio&quot;&gt;Technology consultant and writer specializing in health care reporting and EMRs, software design, technology implementations, and training. With 20 years of hands on experience.&lt;/div&gt;</description>
<category>Sci/Tech</category><guid isPermaLink="false">64972@blogcritics.org</guid>
<pubDate>Sat, 9 Jun 2007 14:32:10 EDT</pubDate>
</item>

</channel>
</rss>