CMS Report and I now have a Twitter account.  This adventure into micro-blogging reflects my willingness to be easily coerced into doing things I normally wouldn't do after long months of winter cabin fever here in South Dakota.

Personally, I cannot see the real benefit of answering Twitter's question, "What are you doing?".  Does anyone really want to see me tweet, that "after I'm done blogging, I'm going to take a shower" on the Web?  Deane Barker once called Twitter "creepy" and I tend to agree with him.  Sadly, Deane Barker allowed himself to be coerced into his own Twitter account last Fall.

Julia Angwin of the Wall Street Journal recently wrote that she wanted to remake herself into a new person...at least into a new person as seen by Google.  When Ms Angwin searched on Google using her own name she continued to see an old article written by her on top of the search results page .  Although the link to the old article was popular, she didn't feel the article was her best work nor that it reflected who she was today.  She then starts on an adventure into search engine optimization (SEO) as she tries to get what she tries to get the search engine to list instead the artides and Internet sites she would want people to see on top of the search results page.

A recent article in ComputerWorld discusses observations made by a Denmark-based analyst regarding wikis in the enterprise.  The analyst points out that wiki technology alone won't deliver if the organization cannot overcome obstacles in its own culture as well as the lack of true content management in a wiki.

One issue is the hype surrounding wikis or the blind faith with which they are approached, said Jespersen. "People often look to Wikipedia as a free form where everyone is contributing, and why could we not do the same with our organization?," she said, having observed wikis entering the scene to compensate for an intranet that has fallen to the wayside. But, she said, technology alone won't resolve that issue.

Jespersen lists three myths surrounding wiki implementation that might make some organizations rethink the expectations they've built around their platform.

The three myths given about wikis in the enterprise are:

1. Myth One: Wikis will motivate employees to contribute content.
2. Myth Two: Employees know how to contribute.
3. Myth Three: Wikis will always provide the information employees need.

Myth three is of special interest to me. The analyst points out that although search is a selling point for wikis...the search capability found in wikis are often not as good as those found in content management systems.  She goes on to explain that given there is little structure built into wikis, "it is difficult to
structure this information to make it findable the next day even."

Make no mistake, Wikis provide an organization with a fantastic tool for employee's in an organization to learn how to collaborate.  I believe organizations often underestimate the paradigm shift needed in their own culture for their employees to properly contribute to a centralized knowledge base.  Wikis and other social publishing tools have proven to be a valuable tool for the collaboration component needed in information systems.  However, eventually wikis fall short of what a more well rounded content management system can provide an organization.

Mary Jander of Internet Evolution takes a hard look at at what IT must do to survive the next few years of economic woes.  She has some sobering things to say, and while we might not like it, she is probably right.  For example, in her first step to IT surviving she says:

Staff levels must go down. Job cuts are now a fact of IT life. Recent announcements portend 5,000 layoffs at Microsoft; a projected 6,000 at Intel; up to 10,000 at IBM. Cuts like these could decimate an already-pressed IT staff, unless measures are taken to automate and virtualize more functions.

The idea of reducing costs in hardware and human resources through virtualization has been suggested before (many times). Now is the time to finally give it a try.

I have never had good luck hosting my Drupal sites on shared hosting plans.  My last venture into budget hosting was a disaster with the hosting company locking me out of my own account due to too many requests to the remote database.  The truth is that I've only been happy with running my personal Drupal sites on virtual private servers (VPS).  However, I'm having a difficult time justifying my yearly costs of using a VPS to host my sites.

Last year I was one of the beta testers for Acquia's Drupal distribution and the Acquia Network.  I was evaluating Acquia's products and services for a potential intranet project at work.  For this particular project, unfortunately, it looks as if Acquia or Drupal wasn't the right solution.  Our regional folks wanted a solution similar to Microsoft's Sharepoint that is more integrated with Microsoft Office and heavily featured in document management.  That's alright though because there are a number of smaller intranet projects at work where Drupal is the perfect solution and a lot of pr

Not long ago I wrote that KDE 4 might produce enough changes to its look and feel to help Linux become more Mac-like.  At the time, Windows Vista seemed to be trying to move in the same direction.  Interestingly, someone has noted that Windows 7 now appears to be moving towards Linux's direction with the Windows desktop looking more like KDE 3.5.

Early Tuesday morning, Ubuntu Linux and Windows XP joined Windows Vista as available operating systems for the Dell Inspiron Mini 12.  By Tuesday evening, I found myself ordering the Ubuntu version of the Mini 12 with the 6-cell battery and 80GB hard drive.  Despite having installed Linux on countless systems, this will be the first time I've ordered Linux pre-installed for the client PC.  I'm eager to find out how well Dell supports their Linux systems.

While the Mini 12 tops the end of the scale for netbooks due to its 12.1 inch widescreen, I believe the Mini 12 will be a perfect Linux replacement for my aging Averatec notebook.  Although I wouldn't have minded a smaller netbook, the Mini 12 with its 1280x800 screen resolution and comfortable keyboard was just too enticing.  Plus the thought of constantly needing to use the browser's scroll bars with the lower resolution (1024x600) of the smaller netbooks was a concern of mine.