NAWeb
Stephen Downes (with fellow participants) is blogging the NAWeb Conference...here is a sample post:
"What concerns me is that I often see the technology driving the delivery process. An example, somewhat exaggerated for effect: On the basis of an airplane conversation, a dean decides to use a particular online portfolio package and brings IT into the process $10-20k later. Then we all jump through hoops trying to force the package to meet the actual needs of the college, altering our environment to meet the parameters of the package, and trying to wheedle faculty and students into actually using the thing. Because the package only supports form-based text input, graphic communications students whose work includes varying file formats cannot include their work in their portfolios. Thought was not given ahead of time to the actual human needs that should be met. The focus is on the technology, its interface and requirements and limitations. Even in administrative applications we see developers picking a toolset based not on its appropriateness to the problem to be solved, but on its appeal to the developers in terms of personal interest, resume-building, et cetera."