Bruce asked in a comment yesterday what I'd like a Design Theory conference to look like. That caused me to think, and, of course, that's always a bad thing.
For me, the primary criteria for any conference is people. I tend to spend 90% of my time out in the halls chatting with people, hammering out ideas, policies or plans (or just chatting). So I suppose most of this will be about who, rather than what.
So, who should be in attendence at a Design Theory conference?
Well, I suppose the obvious group would be the philosophers, epistomologists and the like who explore the rational side of design. We'd want the writer-architects (and writer-furniture-makers and writer-writers and writer-programmers) who tend to write poetic and emotional explorations of the process of design. We'd want the idealists and revolutionaries to spark fire and heated debate. We'd want the quiet researchers plumbing the depths of the quiet back-water pools for hidden gems to provide the sublime and the obscure.
But you can't just lump people together and hope things work (well, you can, and it can be the best type of conference with the right mix of people, but then you really need to work on the "who"). You want some unifying goal or vision that heads the assembled felines in the same general direction without trying to herd them through a given door. What is that vision for a Design Theory conference? Maybe something simple and bald:
Saving Design: Restoring the public's faith in designers
or
Beyond Games: Design as a search for meaning
Anyway, today I am a programmer, so I shall programme computers, (instead of a conference), and on Friday I will transform again into "Design Theory Man" for a few days of fun.


Comments
2010-08-31 12:04
That template db idea is prett y neat. I have to say it's get ting pretty annoying downloadi ng database backups and [...]
2010-08-23 20:57
Yeah, in a similar boat with t he code I write... upshot, I'v e got some pretty good compat code in snakeoil, just w [...]
2010-08-22 08:40
Yeah, that's what I started do ing (the function to convert t o bytes), as I support down to 2.4. Thing is this is [...]
2010-08-22 06:28
Your blog aparently likes does n't handle the less than char (<) conversion all that wel l.. everything following [...]
2010-08-22 06:24
The annoying thing about suppo rting both py2k and py3k is th at you wind up having to get r ather explicit about you [...]
2010-08-16 00:48
The measure of a man, I have a lways thought, was - that he l oved. And was loved.
2010-08-15 21:28
Hmm, hadn't realized that was what dpush was for. I guess I 'll have to make the trunk a b ranch rather than a chec [...]
2010-08-15 20:43
For what it's worth, newer ver sions of bzr-svn will not remo ve existing revisions from you r mainline unless you ex [...]
2010-08-15 20:40
bzr-svn supports not inserting any unusual revision properti es, it just means that pushing your bzr revisions into [...]
2010-08-15 18:21
Hmm, maybe I missed something there. Do you mean merge supp ort as in being able to pull f rom N branches into your [...]
2010-08-15 17:45
Lack of merge support kills th e main benefit of bzr-svn over just using svk I'd argue. Personally, I'm *extreme [...]
2010-08-15 11:46
You might want to check out hg subversion
2010-07-25 14:02
> and would have no Trac integ ration The trac-bzr plugin[ 1] seems to provide good integ ration between bzr and t [...]
2010-07-13 21:47
I've always been fascinated wi th the Asterisk AMI interface. So much so that I married tha t fascination with the [...]
2010-07-03 21:32
Yes, only references in dicti onaries are replaced, so hold ing references in lists, tuple s, etceteras keeps them alive.