13 years, 6 months ago

Time Part One – Posted Dec 31 2010

Link: http://businessanditarchitecture.blogspot.com/2010/12/time-part-one-posted-dec-31-2010.html

I fear that this is going to be a difficult post. But I feel so passionately about time that I will give it a go. What uses of Time do we need to think about. In some ways it’s pretty straightforward, there are instants and durations. But there is often complex interplay between people/systems regarding these.
For example, when I see a program on TV, and it covers something I haven’t seen before I make an assumption that it is new. But in reality it probably isn’t – others will likely have seen it. I still may tweet or otherwise notify a social group that I saw this “new” programme……. So I find it annoying not to know the time context in which something is published or made available. Of course this allows for jokes like Simon Wardley made at his excellent OSCON presentation.
“…Opens up exciting new prospects for the employment of computers in ways and on a scale that would have seemed pure fantasy only five years ago” Simon was applying the idea to the cloud, but actually the quotation stems from 1966. Without the time context we simply don’t know.

And that leads to another area of time complexity – relative time – relative time words. testerday, today, five minutes ago. Of course functions that use relative time are ont idempotent. I get a different answer to “yesterday()” today than I will tomorrow.

As an aside, in synchronous conversation we know what time we are talking about, but in asynch we don’t but we still use synch modes. So getting a bit more concrete.

Madame had a tennis game scheduled. I am absent minded. Madame needs reading glasses. On her phone there was a text message from Mary saying, “Are we playing tennis tomorrow?”   Madame asked me to read it to her on Tuesday morning. My assumption was that the tennis game was to be on Wednesday (tomorrow viewed from my contextual frame which was Tuesday morning).  Actually the game was Tuesday because Mary sent the message on Monday. Madame and Mary had had previous communication on the subject and so had further context. So there are lots of different times and interpretations lurking here. There’s the contextual time of each participant, there’s the actual time of the event, there’s the time the message was sent, there’s the time Madame’s phone received the message… Much scope for ambiguity.

Our command and control/standardization brethren might seek to impose unambiguous temporal semantics onto tennis scheduling, our family life, our friends…. However we can see that’s going nowhere. Standardizing the terms – yeah right.

However as thinkers about systems these things do matter. How do we understand the temporal frames of the various participants including those participants that are systems as well as those that are humans. When do we have to worry about these differences? How do we describe them internally (so that the things that care deal properly), but not to attempt to impose an external semantics onto every participant?

These are hard questions and get to the heart of interaction/integration and what happens in architecture.

In subsequent posts I will lay out some starting ideas around thinking about time (something delicious here – time from someone who is often late….)