My Intent...

Both Jorgen Thelin and Mark Baker referenced a recent posting of mine Glad to hear... They both brought up some good points that make it worth a revisit. To help Mark I will tie it back to an aspect of web services and/or REST depending on which side of the debate you fall on.

I feel architecture by intent is best applied to system level problems rather than individual components. An ideal place to apply it is considering the intent of a service in a service orientated architecture. A major issue in designing services is the appropriate level of granularity to expose, one rule of thumb is that it should be explainable in business objectives rather than technology. A good measure of the business objectives are the intent of the service.

Semantic Web....

The Semantic Web has been getting discussion again - one of the more interesting is Spontaneous intelligence and the Semantic Web by Phil Wainewright where he calls into question the AI aspect of the semantic web. The semantic web, like many other approaches before it, will not create intelligence but will organization information better to enable us to draw more intelligent conclusions. Though if we do not have the good analytical thinkers to use the information....

Glad to hear...

One of my favorite topics merged with one of my favorite sites today. Slashdot has an article about how the 2.6 Linux kernel is going to be faster than the 2.4 kernel. Am I too optimistic or might this reverse the current trend. I think both the major Linux and the other major non unix operating system vendor are guilty of requiring hardware upgrades to support software upgrades.

This is a design problem - throwing features into a product without considering the implications is just being lazy. We are at the point where we do not need to upgrade hardware platforms every 12-18 months unless poor software forces the issue.

We are not considering architecture by intent rather we are developing architecture by accidental consequences. Architecture by intent is the process of deciding what you wish to expose to users and how you want to expose it. Deciding to throw in a more features and not considering the impact is not an intent - it is unintended consequences.

Is it not about time we consider architecture by intent ?

Changing the landscape rather than following the established path

There was a recent article in the New York Times and then Slashdot Operating Systems are Irrelevant, the article is part advertisement part call to action. I agree to some of the key points summarized in the Slashdot article.

1. Operating systems should be irrelevant
2. We should be able to access our data anytime, anywhere.

I installed the software mentioned in the article and played a little with it - the basic idea I get but I am still trying to see how to use it effectively (RTFM?). What I think is more relevant is that the software runs on Windows only. If you are trying to create a revolution you need to associate with revolutionaries.

Where are the revolutionaries though? One problem with the whole Linux desktop approach is that it is trying to copy Windows and emulate it. OpenOffice is great but apart from a few nice features its main advantage is cost; which I think is an advantage, but to change the world there has to be more than dollars involved.

Instead of arguing over the merits of KDE and GNOME the open source community should be trying to revolutionize the environment and make the operating system irrelevant. Removing the need to understand c:\ or /usr/local for most users would change the computing landscape. KDE versus GNOME will only slow down adoption, remember OpenWindows versus Motif.

If the open source community wants to change the world the operating system should be irrelevant and the user experience should be dramatically better rather than a copy of a copy(Windows) of a copy(Macintosh) of the Xerox Star. In this the author, David Gelernter and I agree, we are working with a metaphor that has its roots in the early part of the last century, the file cabinet.

There is an incredible amount of energy and talent in the open source community, could it not be focused better than creating another file folder metaphor?

Print media and Blogs

A while ago I posted an entry suggesting that blogs may be the death of the technical trade journals Where is the information. I subsequently had an email exchange with Jon Udell where he disagreed and stated that he was going to try to change my mind. Well I would like to congratulate Jon and his colleagues at Infoworld for starting to change my mind. They are starting to blend blogs and print in an useful way and I see a synergy among the blog world and Infoworld. Anyone seen other trade magazines doing this or is this unique to Infoworld?