See also: Archives
The following is the first attempt to expand upon an idea that's been bubbling along for the last few weeks. It arises from a combination of recent experiences, including...more...
Over recent weeks I've been so busy that I've largely ignored Twitter. To my detriment. A quick return to it this afternoon found me following two links via tweets from @palbion. The two links were...more...
Have to give a 10 minute spiel to the USQ L&T Systems Advisory group soon to support a request to get BIM installed in the institutional Moodle instance. The slide set is below....more...
The following describes the process and results of using Gephi to generate some visualisations of the inter-connections between the blogs of students in the course I'm teaching. The process is heavily informed by the work of Tony Hirst....more...
Yesterday I attended a session with three different presentations focused around "student voices and their current use of technologies at USQ". There was some very interesting information presented. However, I have a few reservations with aspects of the research and especially with some of the conclusions that have been drawn. I'm hoping to reflect upon and post more about this when I have some time. But an experience just now reinforced one of my reservations and is worth a short sidetrack....more...
Consider this a plea for suggestions. In particular, consider it a plea for workarounds that I can implement quickly (and painlessly)....more...
Just how much of a cage should I make my course into? How far should I take the constraints? The following sets the scene and asks the questions. Would love to hear alternate views....more...
The lack of interaction/feedback between student and teacher in large, contemporary, Australian university courses has always frustrated me. With 350+ students currently enrolled in the course I'm teaching, I'm keen to address this problem. Enter the weekly "course barometer", a simple practice I'm hoping we can keep up for the current semester. The following is a quick summary of the results for the first week and a description of how it works....more...
As a developer, you have to love it when someone using your code diagnoses and identifies their own problem with your code. Especially if they give you a clear and concise explanation you can use. That's what happened with the BIM2 problem I blogged about recently. It appears I was using Moodle 2.3.4 the problem was found on Moodle 2.3.2+ and there was a change in the Moodle code in-between. The following describes the bug and hopefully the fix/change I've made to the BIM code....more...