I have learnt over the last few weeks exactly what research is really about. Sifting through mountains of articles and peer reviewed literature, with often very narrow focus, to find the relevant sections for mostly a highly technical research project is simply impossible.
The analysis of the literature is meant to be done using the crap or craap test. Basically you focus your analysis on broad categories to provide a repeatable, measurable comparison. I have found this doesn’t really help much for technical, prototype coding projects. As such I found the need to create experiments or prototypes is somewhat problematic in the confines of this capstone subject. This subject is about teaching researching methods and processes. Not really about seeing what students can actually build or create.
While my respect for researchers has increased I find the processes around research providing a high level of peer review and editorial oversight – actually hinder growth in developing new cutting edge, practical, functioning software. Where is the encouragement for taking risks with research, allowing for and accepting the likelihood of failure? The need to publish has overtaken the drive to push the boundaries of research.
It is a somewhat anti climatic end to a ‘programming’ based masters.