Archive for July, 2010

Nobody Puts Baby in a Pigeonhole!

Posted in Blog on July 30th, 2010 by David – Be the first to comment

Mother, friend, partner, coworker, best friend, housemate, boyfriend, patient, supervisor, boss, brother, doctor, client, the list goes on.

The number of names I have for people in my life is truly staggering.

Sometimes these names have power – for example, the patient/healthcare professional dynamic is important, in terms of trust, professionalism and the implicit knowledge gradient that it encapsulated.

Without the distinction between patient and healthcare professional, care is essentially impossible. I wouldn’t tell a guy on the street about the intimate details of my home life, but I expect it from my patients and clients, to a certain extent, every time I walk in through the doors of a clinic.

The name implies a pattern of interaction – pleasantries, history, evaluation, recommendation, implementation, farewell. Lather, rinse, repeat, for every monthly, yearly, n-ly appointment from here until the end of time.

Aside from the obvious benefits of expected patterns of interaction, the name also implies an obligation towards care. If I don’t want to be there, the name of ‘healthcare professional’ obliges me to be there, providing care and supporting my patient to the best of my ability.

However, this pattern of behaviour, while useful, has the fundamental drawback that it locks two people into a cycle that one of both may dislike or find unhelpful.

In healthcare, the advantages often seem to outweigh the disadvantages – and, indeed, a sizeable amount of research and development time has gone into ensuring that patient-healthcare worker interactions are useful and productive.

In more general interpersonal relationships, however, the question has to be asked – how much does this name reflect the relationship as it is, how much does it reflect the relationship as I’d like it to be, and how much difference is there between the two?

Particularly in complex, multicategorical relationships, are names or categories helpful or restrictive? Is it more useful to treat this person as my friend or my mother, particularly in a situation where different aspects of those two categories are coming to the fore? Is this person my coworker or my friend? What makes this person a boyfriend/girlfriend over a friend (besides the obvious physical aspects of an intimate relationship)?

Indeed, is the distinction necessary? I wonder whether we would be better off focussing not on what we should do, but on why we want to do – behaving in a manner that reflects that particular person, and the individual relationship that we have with them.

No rules. No labels. No holds barred.

No worries, mate!

The peril of standards

Posted in Blog on July 25th, 2010 by David – Be the first to comment

At first sight, it should be a simple problem – write a web services backend to a provided HTML5 frontend to handle OAuth logins to a couple of different services, intelligently storing the authentication information and allowing posting to those services via the integrated frontend.

Oh, $DEITY was I wrong.

Firstly, OAuth has a kind of triple handshake thing going on that means that I have to reengineer the front end to load the required login pages and then handle the callback. Okay, that’s fine. Doable, if nothing else.

Then turns out that the thing that’s passed back isn’t the actual string that needs to be stored. Okay, background call to get the actual string, that’ll be fine.

Then, apparently those strings expire. Oops, nobody mentioned that. So, when they’re not valid any more, you have to pass back the original string and get a new one. But you can’t just use that, that would be silly, so both have to get stored.

Is it any wonder I’m pulling my hair out right now?

I sometimes wonder whether the purpose of an open standard is just to make it so everything is equally annoying. Which is helpful, I’ll grant them that.

The problem arises when the web frameworks that will eventually have to function within that system either aren’t set up to handle them at all or try to do too much for you.

For example, Grails has a beautiful OAuth plugin, which I’m sure works great for websites written in Grails, but which continually throws weird redirects and stuff around when I try and modify it. Cue several hours of rolling my own. Several hours I don’t have, I should add.

Ah, well – at least I don’t have to write separate handlers for YouTube, Facebook and Twitter. If only flickr would get on the OAuth bandwagon, I’d be a happy man!

Welcome to the new ForsakenDAemon.net

Posted in Blog on July 22nd, 2010 by David – Be the first to comment

After wondering for a long time what to do with this blog, I’ve decided to rebrand. I’ll be bringing my articles and some of my old blog posts over over the coming weeks, so stay tuned!

In the meantime, check out some of my current projects, including An Awkward Pause, Creative Innovation 2010 or The Hub Melbourne.

- DAemon