The program went through dozens and dozens of iterations, mainly over the summer after we graduated. I didn't have any disk space allocation, so I had to punch a paper tape each day when I finished and load it back in again the next day... The best way to put the assertion (and this is all it is at this point; and again, please keep in mind that there are a number of familiar exceptions) is that the practice of game software development generates a way of seeing and defining problems (as essentially precise, logical, and algorithmic), and creating solutions (through linear, text-defined code) that makes other ways of accounting for what happens in VWs seem at worst nonsensical and at best irrelevant or quixotic. They looked friendly enough--at least, no one had fruit ready to throw at us. It was simply kind of surreal, after reading the comments on TN this past week and hearing other things at the conference about the problems with game studies and developer/academic relations.

After our "high energy" presentation, the questions were even stranger. Someone asked why humanities research got left out, and we had to say that we couldn't find it to be directly relevant on our top 10 list of bulleted points. Ian made the point, and I agreed, that doing the research for this panel made us think differently about academic research. While I'm not going to say that what we've done personally has no value, it was a definite challenge to try and make it *directly relevant* in a BULLETED POINT for developers. And there are huge gaps in what we don't know. Where is the research about sports games, to take just one example? Anyway, the point is, I enjoyed the exercise, and learned a lot from it. I hope the audience did as well.

But overall, I like to think that the attendance demonstrates that developers are interested in what academics might be able to tell them (again I will point out: no fruit was thrown). And all week, I talked with developers who were interested in what was going on with research, from the smallest to the largest companies. Maybe the issue is the "larger" community. It's always easy to abstract and oversimplify at that level. But I know that on an individual level, there are real conversations and collaborations going on. I don't want this to turn into some rosy "it's better than we think" or "can't we all just get along" thing, but I do think that perhaps the situation is not as dire as it's hyped to be. But then again, I haven't gotte my evals back yet.No doubt Cheap SWG Creditsis the best choice, for spending less gain more. Trust the effect of us as well as to show you excellent feeling. Buy SWG Creditskeep you well. In this case a TreeMap. We have huge quantity of SWG Creditsfor sale!

Here is just one quick example of this kind of disposition in action: Billmonk, which Constance posted about here. The site promises to help you keep track of your obligations throughout your social network precisely (using any of a number of imaginable currencies). It is double-entry bookeeping for your friendships, and thereby prompts you to conceive of these obligations in exact terms. This is a perfect example of a code-based solution to a code-defined problem: People's moral obligations are essentially precise and monetary, and they therefore need a precise tool to manage them. (And this approach is not just applied externally; within software companies one frequently sees similar efforts to address organizational issues with precise and enumerated systems that can be, above all, measured.) Heather Kelly, one of the developers on a panel on Monday asked a great question about game development that she hoped researchers could help answer: Why does money trump everything? The answer lies in the remarkably good 'fit' between the market and code, and in the existence of a lot of well-trained people who can find ways to exploit it.

In my freshman and sophomore years in high school, 1975-76, I played Mike Mayfield's creation. For me it was a dicey entertainment proposition. Forget about "game content" - the game, or at least its instantiation in a computer, was a scarce resource: a conspiracy of teletypes, timeshare, and that crowded room. Because of the scarcity, there were always plenty of campers willing to arm-wrestle you for the drops.