I had the pleasure this month of attending my first SIGCSE conference, conveniently located in Portland, within walking distance of home. Now that a week's gone by, a couple of impressions stand out:
1. The tone, compared to a typical academic conference, was remarkably congenial. Technical conferences, in my experience, tend to be combative (everyone's chasing the same grant money, after all), a modern-day descendant of medieval jousts: bring a sharp lance (make clever points in your own talk), andlook for advantage(challenge the other speakers at theirs). In contrast, SIGCSE attendees were relaxed, cordial, and constructive -- demeanors all refreshing, even startling.
2. Manycore/concurrency concerns maybe on the curriculum radar, but only as adistant speck. You could count the number of concurrencytalks or workshopson a single hand, andI observedan alarming lack of urgency to adapt to the retirement of single-core architectures. One speaker talked of changing things when 32-core chips showed up "in about ten years". Sorry, some of these are already here (GPGPU); many more will enter the mainstream before current students graduate.
To this secondpoint, it was gratifying to see the crowded attendance at the manycore talk, where I worked on raising the anxiety level (manycore programming is here, be very afraid). Thisshift, serial to multicore to manycore,is going to be an interesting if bumpyride for all, and we'll want to keepsharing information in that congenial and open spirit of SIGCSE.