An alternative way to program a SwanCon

[tommo]

I was going to post this as a reply on someone else's journal, but I think it's an interesting enough point to be a post of it's own.

I've been wondering whether the job of programmer should really be divided up further than it currently is. Have a head programmer to run and timetable the whole thing and generally be in charge, but then have sub-programmers responsible for different streams. You could have a media fan organising some TV and movie panels, a lit fan organising some book panels, avid gamer for gaming panels, anime buff for anime panels, and so on. And the head programmer gives them each a certain number of panel slots they have to fill up. I think that could result in a much more well-balanced programme.

What do people think? It'd swell the numbers in a committee somewhat, but I think if it was done well and everyone involved put in the required effort, you'd probably end up with a stellar programme. And it'd take some of the burden away from the head programmer, who tends to do a hell of a lot of work putting it all together.

Comments

[utopos.livejournal.com]

The role of programmer as I've always seen it (and seen it done effectively over the years) is to:
1. Cater to as many broad categories as possible without personal bias (aesthetic bias is theoretically ok) and
2. Allow for the study, expression and promotion of SF culture in as many ways as possible within the 100-150 slots available over the duration of the con.

Essential for the former is the willingness to outsource development on items on topics out of the programmer's (presumably formidable) range of knowledge - and the willingness to recognise when something may be awry in the balance of the program (says someone who fell into programming as a result of the latter).

Fortunately open programming meetings have been relatively regular in the past - and now shrydar's wonderful work on the website has taken the community collaboration aspect of running the con that extra step further I believe we're seeing significant improvements.

For management purposes I'd prefer multiple programmers (maybe two) with the Convenor (or maybe the Vice - someone senior and logisticy) having final say on what goes on where and when.