OU blog

Personal Blogs

Christopher Douce

New Technology Day - June 2014

Visible to anyone in the world
Edited by Christopher Douce, Tuesday, 8 Oct 2019, 17:42

This post is a quick summary of a New Technology Day event that took place at The Open University London regional centre on Saturday 14 June 2014.  I’ve written this post for a number of reasons: for my esteemed colleagues who came along to the day, so that I help to remember what happened on the day, so that I can share with my bosses what I’m getting up to on a day to day basis, and for anyone else who might be remotely interested.

One of the challenges that accompanies working in the area of technology, particularly information technology and computing, is that the pace of change is pretty relentless.  There are always new innovations, development and applications.  There are always new businesses doing new things, and using new techniques.  Keeping up with ‘the new stuff’ is a tough business.  If you spent all your time looking at what was ‘new’ out there, we simply wouldn’t get any work done – but we need to be understanding ‘the new’, so we can teach and relate to others who are using ‘all this new stuff’.

The idea for this day came from a really simple idea.  It was to ask colleagues the question, ‘have you heard of any new technology stuff recently?  If so, can you tell me about it?’  Rather than having a hard and fast ‘training’ agenda the idea was to create a space (perhaps a bit like an informal seminar) to allow us to have an opportunity to share views and chat, and to learn from each other.

Cloud computing

After a brief introduction, I kicked off with the first presentation, which was all about cloud computing.  A couple of weeks back, I went to a conference that was all about an open source ‘cloud operating system’ called OpenStack as a part of some work I was doing for a module team.  The key points from the presentation are described in a series of two blog posts (OU Blog)

Towards the end of the presentation, I mentioned a new term called Fog Computing.  This is where ‘the cloud’ is moved to the location where the data is consumed.  This is particularly useful in instances where fast access times are required.  It was interesting to hear that some companies might also be doing something similar.  One example might be companies that deliver pay-on-demand streaming video.  It obviously doesn’t make a lot of sense if the movies that you want to see are located on another continent; your viewing experience may well be compromised by unforeseen network problems and changes in traffic.

It was useful to present this since it helped to clarify some of my understandings, and I also hoped that others found it interesting too.  Whilst the concept of a ‘cloud’ isn’t new (I remember people talking about the magic of an X.25 cloud), the technologies that realise it are pretty new.   I also shared a new term that I had forgotten I had written on one of my slides: the concept of a devop – someone who is also a developer and an operator.

JuxtaLearn project

The second presentation was about the JuxtaLearn project, by Liz Hartnett, who was unable to attend.  Liz, however, still was able to make an impact on the event since she had gone the extra mile to make an MP3 recording of her entire presentation.  Her talk adopted the PechaKucha format.  This is where a presenter uses 20 slides which change every 20 seconds.  Since her slide deck was setup to change automatically, it worked really well.

We learnt about the concept of the threshold concept (which can be connected to the concept of computer programming) and saw how videos could be made with small project groups.  I (personally) connected this with activities that are performed on two different modules: TU100 My Digital Life, and T215 Communication and Information Technologies, which both ask students to make a presentation (or animation).

OU Live and pedagogy

The next talk of the day was by Mandy Honeyman, who also adopted the PechaKucha format.  Mandy talked about a perennial topic, which is the connection between OU Live and pedagogy.  I find this topic really interesting (for the main reason that I haven’t yet ‘nailed’ my OU Live practice within this format, but it’s something that I’m continuing to work on).  I can’t speak for other people, but it has taken me quite a bit of time to feel comfortable ‘teaching’ using OU Live, and I’m always interesting in learning further tips.

Mandy has taken the time and trouble to make a version of her presentation available on YouTube.  So, I’ve you’ve got the time (and you were not at the event), do give this a look.  (She prepared it using PowerPoint, and recorded it using her mobile phone).

The biggest tip that I’ve made a note of is the importance of ‘keeping yourself out of it’, or ‘taking yourself out of it [the OU Live session]’.  When confronted by silence it’s easy to feel compelled to fill it with our own chatter, especially in situations where students are choosing not to use the audio channel.

One really interesting point that came out during the discussion was how important it is to try to show how to use OU Live right at the start of their journey with the OU.  I don’t think this is done as it could be at the moment.  I feel that level 1 tutors are implicitly given the challenging task of getting students up to speed with OU Live, but they will already have a lot on their hands in terms of the academic side of things.  I can’t help think that we could be doing a bit better when it comes to helping students become familiar with what is increasingly become a really important part of OU teaching and learning.

It was also mentioned that application sharing can run quite slowly (especially if you do lots of scrolling) – and one related thought is that this might well impact on the teaching and learning of programming.

A final point that I’ll add is that OU Live can be used in a variety of different way.  One way is to use it to record a mini-lecture, which students can see during their own time.  After they’ve seen them, they can then attend a non-recorded discussion seminar.  I’ve also heard of it being used to facilitate ‘drop in sessions’ over a period of a couple of hours (which I’ve heard is an approach that can work really well).

Two personal reflections that connect to this session include: we always need good clear guidance from the module team about how they expect tutors to use OU Live, and secondly, we should always remember to give tutors permission to use the tool in the ways that make the best use of their skills and abilities, i.e. to say, ‘it’s okay to go ahead and try stuff; this is the only way you can develop your skills’.

The March of the MOOCs

Rodney Buckland, a self-confessed MOOCaholic, gave the final presentation of the morning.  The term MOOC is an abbreviation for Massive Open Online Course.  From the sound of it, Rodney has taken loads.  (Did he really say ‘forty’?  I think he probably did!)

He mentioned some of the most popular platforms.  These include: Coursera, Udacity and FutureLearn (which is a collaboration between the OU and other universities).  Rodney also mentioned a swathe of less well known MOOC platforms, such as NovoEd.   A really interesting link that Rodney mentioned was a site called MOOCList which is described as ‘an aggregator (directory) of Massive Open Online Courses (MOOCs) from different providers’. 

Rodney spoke about his experience of taking a module entitled, ‘Science of the solar system’.  He said that the lecturer had really pushed his students. ‘This was a real surprise to me; this was a real third level physics module’.

A really important point was that MOOCs represented an area that was moving phenomenally quickly.  After his talk had finished there was quite a lot of discussion about a wide range of issues, ranging from the completion rates (which were very low), to the people who studied MOOCs (a good number of them already had degrees), and to the extent to which they can complement university study.  It was certainly thought provoking stuff.

Assistive technology for the visually impaired: past, present and future

The first presentation after lunch was by my colleague Richard Walker.  Richard is a visually impaired tutor who has worked with visually impaired students.  He made the really important point that if an associate lecturer works for an average of about ten years, there is a very significant chance that a tutor will encounter a student who has a visual impairment.  Drawing on his previous presentation, there is an important point that it is fundamentally important to be aware of some of the challenges that visually impaired students can face.

Richard recently interviewed a student who has a visual impairment by email.  Being a persuasive chap, Richard asked me to help out: I read out the role of his student from an interview transcript.  The point (to me) was very clear: students can be faced with a whole range of different issues that we may not be aware of, and everything can take quite a lot longer.

Another part of Richard’s presentation (which connects the present and the future) was all mobile apps.  We were introduced to the colour recogniser app, and another app called EyeMusic (iTunes) which converts a scene to sound.   Another really interesting idea is the concept of the Finger Reader from the Fluid Interface group at MIT.

A really enjoyable part of Richard’s session was when he encouraged everyone to explore the accessibility sessions of their smartphones.  Whilst it was easy to turn the accessibility settings on (so your iPhone spoke to you), it proved to be a lot more difficult to turn the settings off.  For a few minutes, our meeting room was filled with a cacophony of robotic voices that proved to be difficult to silence.

Towards utopia or back to 1984

The penultimate session of the day was facilitated by Jonathan Jewell. Jonathan’s session had a more philosophical tone to it.  I’ve made a note of an opening question which was ‘how right or wrong were we when predicting the future?’

Jonathan referenced the works of Orwell, Thomas More (Wikipedia) and a vision of a dystopian future depicted in THX 1138, George Lucas’s first film.  Other subjects included economic geography (a term that I hadn’t heard before), and the question of whether Moore’s Law (that the number of transistors in a microprocessor doubles every two years) would continue.  On this subject, I have sometimes wondered about what the effect of software design may be if and when Moore’s law fails to continue to hold.

Other interesting points included the concept of the technological singularity and a connection to a recent news item (BBC) where a computer was claimed to have passed the Turing test.

A great phrase was infobesity – that we’re all overloaded with too much information.  This connects to a related phrase that I have heard of before, which is the ‘attention economy’.  Jonathan made a similar point that information is not to much a scare resource.  Instead, we’re limited in terms of what information we can attend to.

We were also given some interesting thoughts which point towards the future.  Everything seems to have become an app: computing is now undeniably mobile.  A final thought I’ve noted down is Jonathan’s quote from security expert, Bruce Schneider: ‘surveillance is the business model of the internet’.  This links to the theme of Big Data (Wikipedia).  Thought provoking stuff!

Limits of Computing

The final talk of the day was by Paul Piwek.  Paul works as a Senior Lecturer in the Department of Computing and Communications at The Open University.  Paul works on a number of module teams, and has played an important role in the development of a new module: M269 Algorithms, Data Structures and Computability.  It is a course that allows students to learn about some of the important fundamentals of computer science.

Paul’s brief was to talk about new technologies – and chose to explore this by considering the important question of ‘what are the limits of computability?’  This question is really important in computer science, since it connects to the related questions: ‘what exactly can we do with computers?’ and ‘what can they actually be used to calculate?’

Paul linked the title of his talk to the work of Alan Turing, specifically an important paper entitled, ‘on computable numbers’.  Paul then went onto talk about the differences between problems and algorithms, introduced the concept of the Turing Machine and spoke about a technique called proof by contradiction.

Some problems can take a long time to be solved.  When it comes to computing, speed is (obviously) really important.  An interesting question is: how might we go faster?  One thought is to look towards the subject of quantum computing (an area that I know nothing about; the page that I’ve linked to causes a bit of intellectual panic!)

Finally, Paul directed us to a Canadian company called DWave that is performing research into the area.

Reflections

After all the presentations had come to an end we all had a brief opportunity to chat.  Topics included location awareness and security, digital forensics, social media, the question of equality and access to the internet.  We could have chatted for a whole lot longer than we did.

It was a fun day, and I really would like to run another ‘new technology day’ at some point (I’ve just got to put my thinking hat on regarding the best dates and times).  I felt that there was a great mix of presentations and I personally really liked the mix of talks about technology and education.  It was a great opportunity to learn about new stuff.

By way of additional information, there is also going to be a London regional ‘research day’ for associate lecturers.  This event is going to take place during the day time on Tuesday 9 September 2014.  This event will be cross-faculty, cross-disciplinary event, so it’s likely that there might be a wide range of different events.  If you would like some more information about all this, don’t hesitate to get in touch, and I’ll point you towards my colleague Katy who is planning this event.

Permalink 1 comment (latest comment by Mandy Honeyman, Tuesday, 17 June 2014, 15:40)
Share post
Christopher Douce

MOOCs - What the research says

Visible to anyone in the world
Edited by Christopher Douce, Friday, 3 Jan 2014, 10:23

On 29 November 2013 I bailed out of the office and went to an event a place called  the London Knowledge Lab to attend a dissemination event about MOOCs.  Just in case you’re not familiar with the term, a MOOC (Wikipedia) is an abbreviation for Massively Open On-line Courses. The London Knowledge Lab was a place that I had visited a few years ago to attend an event about e-assessment (blog post).

This post is a quick, overdue, summary of the event.  For those who are interested, the London Knowledge Lab has provided a link to a number of pages (Institute of Education) that summarises some of the presentations in a lot more detail.  

Introductions

The event started with a brief presentation by Diana Laurillard, entitled The future potential of the MOOC.  During Diana’s presentation, I noted down a number of points that jumped out at me.

An important question to ask is what problems is a MOOC going to solve?  Diana mentioned a UNESCO goal (UNESCO website) that states that every child should have access to compulsory education by 2015.  It’s also important to note that there is an increasing demand for higher education but in the sector, the current model is that there is 1 member of staff for every 25 students.  If the objective is to reach as many people as possible, we’re immediately faced with some fundamental challenges. One thought is that perhaps MOOCs might be able to help with the demand for education.

But why should an institution create a MOOC in the first place?  There are a number of reasons.  Firstly, a MOOC offers a taster of what you might expect as a particular course of study, it has the potential to enhance or sustain the reputation of an institution that provides (or supports) a MOOC, offers an opportunity to carry out research and development within the intersection between information technology and education.  One of the fundamental challenges include how to best create a sustainable business model.

A point to bear in mind is that there hasn’t (yet) been a lot of research about MOOCs.   Some MOOCs clearly attract a certain demographic, i.e. professionals who already have degrees; this was a point that was echoed a number of times throughout the day.

Presentations

The first presentation of the day was by Martin Hawksey who talked about a MOOC ran by the Association of Learning Technology (ALT website).  I made a note that it adopting a ‘connectivist’ model (but I’m not quite sure I know what this means), but it was clear that different types of technology were used within this MOOC, such as something called FeedWordPress (which appears to be a content aggregator).

Yishay Mor, from the Open University Institute of Educational Technology spoke about a MOOC that was all about learning design.  I’ve made a note that his MOOC adopted a constructionist (Wikipedia) approach.  This MOOC used a Google site as a spine for the course, and also use an OU developed tool called CloudWorks (OU website) to facilitate discussions.

Yishay’s tips about what not to do include: don’t use homebrew technology (since scaling is iimportant), don’t assume that classroom experiences work on a MOOC, from the facilitators perspective the amount of interactions can be overwhelming.  An important note is that scaling might mean (in some instances), moving from a mechanical system to a dynamic system.

The third presentation of the day was by Mike Sharples who was also from the Open University.   Mike also works as an academic lead for FutureLearn, a UK based MOOC that was set up as a partnership between the Open University and other institutions.  At the time of his presentation, FutureLearn had approximately 50 courses (or MOOCs?) running.

I’ve noted that the pedagogy is described as ‘a social approach to online learning’ and Mike mentioned the term social constructivism.  I’ve also made a note that Laurillard’s conversational framework was mentioned, and ‘tight cycles’ of feedback are offered.  Other phrases used to describe the FutureLearn approach include vicarious learning, conversational learning and orchestrated collaboration. 

In terms of technology, Moodle was not used due to the sheer number of potential users.  The architecture of Moodle, it was argued, just wouldn’t be able to cope or scale.  Another interesting point was that the software platform was developed using an agile process and has been designed for desktop computers, tablets and smartphones. 

Barney Graner, from the University of London, described a MOOC that was delivered within Coursera (Coursera website).  I have to confess to taking two different Coursera courses, so this presentation was of immediate interest (although I found that the content was very good, I didn’t manage to complete either of them due to time pressures).  The course that Barney spoke of was 6 weeks long, and required between 5 and 10 hours of study per week.  All in all, there were 212 thousand students registered and 9% of those completed.  Interestingly, 70% were said to hold a higher degree and the majority were employed.  Another interesting point was that if the students paid a small fee to permit them to take something called a ‘signature track’, this apparently had a significant impact on retention statistics.

Matthew Yee-King from Goldsmiths gave a presentation entitled ‘metrics and systems for peer learning’.  In essence, Matthew spoke about how metrics can be used on different systems.  An important question that I’ve noted is, ‘how do we measure difference between systems?’ and ‘how do we measure if peer learning is working?’

The final presentation of the day, entitled ‘exploring and interacting with history on-line’ was by Andrew Payne, who was from the National Archive (National Archive education).  Andrew described a MOOC that focused on the use of archive materials in the classroom.  A tool called Blackboard Collaborate (Blackboard website) was used for on-line voice sessions, the same tool used by the Open University for many of their modules.

Towards the end of the day, during the start of a discussion period, I noted of a number of key issues for further investigation.  These included: pedagogy, strategy and technology.

Reflections

In some respects, this day was less about sharing hard research findings (since the MOOC is such a new phenomenon) but more about the sharing of practice and ‘war stories’.

Some messages were simple, such as, ‘it’s important to engineer for scale’.  Other points certainly require further investigation, such as, how best MOOCs might potentially help to reach those groups of people who could potentially benefit most from participating in study.  It’s interesting that such a large number of participants already have degree level qualifications.  You might argue that these participants are already experienced learners.

It was really interesting to hear that different MOOCs made use of different tools.  Although I’m more of an expert in technology than pedagogy, I feel that there is continuum between MOOCs (or on-line courses, in general) that offer an instructivist (or didactic) approach on one hand, and those that offer a constructivist approach on the other. Different software tools, of course, permit different pedagogies.   

Another (related) thought is that learners not only have to learn the subject that is the focus of a MOOC, but also learn the tool (or tools) through which the learning can be acquired.  When it comes to software (and those MOOCs that offer learners a range of different tools) my own view is that people use tools if they are sure that there is something in it for them, or the benefit of use outweighs the amount of investment that is extended in learning something.

In some respects, the evolution of a MOOC is an exercise in engineering as much as it is an exercise in mass education.  What I mean is that we’re creating tools that tell us about what is possible in terms of large scale on-line education.  Some tools and approaches will work, whereas other tools and approaches will not.  By collecting war stories and case studies (and speaking with the learners) we can begin to understand how to best create systems that work for the widest number of people, and how MOOCs can be used to augment and add to more ‘traditional’ forms of education.

One aspect that developers and designers of MOOCs need to be mindful of is the need for accessibility.  Designers of MOOCs need to consider this issue from the outset.  It’s important to provide media in different formats and create simple interfaces that enable all users to participate in on-line courses.  None of the presenters, as far as I recall, spoke about the importance of accessibility.  A high level of accessibility is connected to high levels of usability.

Just as I was finishing writing up this quick summary, I received an email, which was my daily ‘geek news’ summary.  I noticed an article which had an accompanying discussion.  It was entitled: Are High MOOC Failure Rates a Bug Or a Feature? (Slashdot).  For those who are interested in MOOCs, it’s worth a quick look.

Permalink Add your comment
Share post

This blog might contain posts that are only visible to logged-in users, or where only logged-in users can comment. If you have an account on the system, please log in for full access.

Total visits to this blog: 2372566