Tagged: Productivity

Rich Versus Reach – my perspective

The Rich versus Reach debate is raging in the blogsphere at the moment.  The debate has been very healthy with less of the usual emotional clutter that clogs up most debates that touch on the future of Microsoft.  I am an enterprise guy, with a complex home network as well, which gives me an interesting perspective so I thought it would good to pull some of the threads together.

 

The debate mainly started with a post by Joel on How Microsoft Lost the API War it’s a good article at the start but then begins to lose its focus and starts to make some bold assertions which are hard to substantiate.  These are partially rebutted by Olivier Travers in his post Microsoft Lost the API War? Not So Fast and more thoroughly by Robert in his post Seven Reasons Why the API War is Not Lost After All, which comes over a bit evangelistic but is still a good contribution to the debate.  Robert introduces a new perspective for me on Avalon where he describes how it may be possible to download XAML directly from the web as an alternative UI experience to HTML …

Calendar Feeds

In this blog, I started to talk about the evolution of subscription beyond news.  Here is a great example of how this might work.  This site describes the RDF Calendar format.  It provides a few examples, (I have added a few as well), of why you migt want to subscribe to a calendar, and includes ToDo list examples:

  1. Subscribe to you travel itinery and have the events automatically added to your calendar, flight times etc, and automatically updated

  2. Subscribe to a list of bugs which flow into your todo list

  3. Subscribe to an event schedule, for example football matches

  4. Subscribe to a favorite TV show

More information is available here

Some of the scenarios are listed below:

One more example of the Personal Information Disaster that is the web today!

Personal Information Disaster!

I wrote this post then lost it!  So this is just a place holder to remind me to get around to writing it again.

links I need are

http://www.novell.com/products/ifolder/

http://haystack.lcs.mit.edu/index.html

http://esw.w3.org/topic/PersonalInformationDisaster

http://www.kde.org/

http://oopm.openoffice.org/

 

http://news.com.com/2009-1016-5103226.html?tag=nl

 

http://www.adambosworth.net/archives/000021.html

 

http://www.microsoft.com/mac/products/office2004/office2004.aspx?pid=highlights

 

http://weblog.infoworld.com/udell/2004/06/17.html#a1025

 

http://www.opensource.org/halloween/halloween11.html

and my own blog entries

Which Office Suite?

Which Office Suite? Is shaping up to be a fascinating decision making process.  I am not ready to expose all of my thinking on this topic but it goes something like this:

 

  1. Some people think its easy, MS Office alternatives are cheaper and most people don’t use the bells and whistles in Office so people will migrate provided the alternatives meet peoples core needs.

  2. I think its more complex than this and as a minimum the costs of migration, lost productivity, and compatibility and rework need to be factored in

  3. Intertia is a big one in Microsofts favour, for a business that has SW Assurance or an EA, the decision is deferred probably for at least 2-3 years after their EA expires and probably longer if they do a lot of data interchange.  That probably means 4-5 years from now!

  4. But this is the trivial stuff.  Sure direct and indirect cost comparison is important but I want to consider:

    1. How do people really use Office and is it really true that people only use a small amount of the functionality, and if they do, do they all use a different small amount?

    2. I also want to consider …

Choosing a PDA – can it really be so difficult!

I used to have an IPAQ years ago and despite using it a lot in the beginning I gradually stopped using it mainly for the following reasons:

 

  1. I did not like having to sync it

  2. It was too big to carry around everywhere

  3. I did not have a case that gave me instant access to it when carrying it around, so it tended to be in a bag

  4. The battery life deteriorated to the point where it could not be relied upon

  5. It did not have enough storage space without a great big expansion jacket add-on

 

Then along came a Blackberry which I instantly fell in love with, I have talked about my love affair with my Blackberry before in my gadget blog.  However I recently started working from home and the subscription costs to the Blackberry service no longer seemed worthwhile so I decided that I would take that money and invest it in something that was a higher priority, I decided I would try a traditional Palm or Pocket PC PDA again.

 

The process of choosing is a classic example of the tyranny of too much choice.

 

My experience went something …

Another short article that describes whats important about RSS

This site has just appeared http://www.reallysimplesyndication.com it includes the following bullet list of things that make up RSS.

RSS is…

1. A format.

2. Content management tools that generate feeds in the format.

3. Aggregators and readers that subscribe to the feeds.

4. Search engines and utilities that crunch the information and ideas.

5. Services from technology companies like Microsoft and Apple.

6. Authoritative publications like the BBC, The New York Times, CNET, InfoWorld, PC World, Time, Wired, Salon, Yahoo, Reuters — that distribute news and opinion in RSS.

7. Many thousands of weblogs covering virtually every aspect of life on this planet.

8. A vast and growing community of thinkers, writers, educators, public servants, and technologists.

The revolution of RSS is what people are doing with it, what it enables, the way it works for people who use technology, the freedom it offers, and the way it makes timely information, that used to be expensive and for the select-few so inexpensive and broadly available.

RSS is the next thing in Internet and knowledge management. It’s big. A lot bigger than a format.

My personal information processing pipeline!

In this blog I talked about a generic concept of operations associated with a conceptual information lifecycle. 

however with the advent of RSS, we now have an Open and Simple way for applications to publish, for users to locate and  subscribe and for subscribed content to be accessed, processed and ultimately scanned and consumed, discussed, archived and subsequently retrieved

In this article talk about my personal application of tools and techniques to that lifecycle.

  1. Publishing, I used to use radio for all of my web publishing, either directly through the Radio Userland Web UI, or through MailEdit which provides an email interface which I can use through my BlackBerry.  MailEdit uses a number of directives to define for example the title for the entry and the categories that it belongs to.  I use autotext on the BlackBerry to make entering these easier.  I now use Blogmedia that uses the BlogWare SW.  I tend to write the entries in Word though because the screen area is bigger and because of the spell checking, and then just paste and post.  You can read my blog here

  2. Location, like most people I locate RSS feeds …

Information Bridge Framework

My first thought when I cam across IBF, (who could miss it!), was that it was another Microsoft thick client solution.  I am still not sure but it looks like it might be a bit more creative than that for the following reasons:

  1. I have always been a big advocate of standardizing the infrastructure capability layer and integrating it with the line of business layer.  That way an enterprise has its infrastructure in common, regardless of which process or division of the company you work in.  IBF looks like it addresses that need pretty well

  2. I have also felt that the ad-hoc processes and information and collaborative processes are under emphasized in businesses that have a lot of formal mega processes that they like to optimize.  I talked about this in another blog entry.  IBF allows you to integrate ad-hoc and formal business processes.

  3. It seems that a lot of thought has gone into making the maintenance of the IBF client environment as ‘thin’ as possible.  It still requires a client component to get started though.  I need to look into this more to be sure but it looks hopeful.

  4. Its all about consuming web services, caching them …

Exchange Futures

Infoworld talks to David Thompson, a Microsoft corporate vice president who has been in charge of the Exchange Server group since early this year.   It maybe just me but I get the distinct impression that the Exchange Group is in a bit of a state.  They don’t seem to really know where storage is going because of the flux around Longhorn server, and they don’t seem to know where to take Public Folders and other Document management like capabilities because they are dropping the old store and because of ‘competition’ from SharePoint services.  Core email does not have much growth potential in it, so all that seems to be left to work on is Edge Servers!  Not a very exiting roadmap!!

Last year I thought that the ‘big thinking’ that must be going on in Microsoft was starting to pay off in terms of well architected products that did not overlap and were being rebuilt from the ground up.  Now I am not so sure,  I see the delays in the foundation layers, ie SQL Server and Longhorn Server, triggering panic in the Office tools and Collaboration space, who are probably starting to think more short term about customer …

Longhorn Search

Chris Sherman at SearchEngineWatch talks a bit about Longhorn search and links to a Channel 9 video clip where you get some glimpses of how search is going to be implemented in Longhorn.  What’s clear right now is that they are:   1.     Planning for a search experience that operates...