Ouch!
(link) [del.icio.us/distobj]
Nailed. Shades of my fight with “workflow” 10 years ago.
(link) [del.icio.us/distobj]
“Of course SOA deployments are failing when SOA hasn’t actually provided any industry progress from earlier distributed computing technologies applied to IT problems”. Well, yes and no. If only the progress made was recognized as such.
(link) [del.icio.us/distobj]
“it was a joy to type and my colleagues looked at me like I was a superhero!” OMG! (via Jan)
(link) [del.icio.us/distobj]
Plus/minus is a sucky stat for measuring individual performance, but much less sucky for a line .. or, this case, for all the guys (minus the goalie) on the ice together. Go Sens!
(link) [del.icio.us/distobj]
“It’s going to take time to work out the bugs and establish best practices.” 8-)
(link) [del.icio.us/distobj]
“After all, if it doesn’t change, we can’t sell….”. Brilliant.
(link) [del.icio.us/distobj]
A dissappointing story by the normally sure-footed Jon Udell. Publishing interfaces is a necessary but insufficient condition for “swapability” (aka substitution); having the *same* interface is also required.
(link) [del.icio.us/distobj]

Speaking of tuple space based systems

Google Base is a place where you can easily submit all types of online and offline content that we’ll host and make searchable online.

Contrast that with this ( snippet);

The tuples have just a few key properties: […] (2) They are persistent, remaining available long after the application that created them has gone on to other tasks. (3) They do not have names or other external identifiers and are stored in no particular order. Instead, they are located by querying their content…

Of course, nothing says they can’t also have identifiers.

Now, if Google Base would just support RDF – which is as sloppily extensible as Adam requires – we’d even get the “tuple” (read; triple) part of tuple spaces. Or, failing that, at least microformats.

A very good move for the W3C
(link) [del.icio.us/distobj]