Digital Civil Rights: a Guest Lecture

Today I had the pleasure of doing a guest lecture for Bits of Freedom at the University of Leiden in a course titled Anthropology of Information Society. I used many examples to try and drive home two points:

  1. Technology is not just a tool, it is not “neutral”
  2. You can help change technology for the better

One thing the students did, was write their own personal data policies (kind of like a reverse terms of service for using a webservice). This is something that I intend to explore further in this blog pretty soon.

[slideshare id=9790836&doc=111020digitalcivilrights-111020081332-phpapp02]

You can also download the presentation as a 12MB PDF file.

Looking forward to any comments that you might have.

Make Sure You Read This: Hackers by Steven Levy

Hackers
Hackers by Steven Levy

Wow! This is a masterful book.

Levy reports on three different eras that have shaped modern computing:

  • The group of hackers at MIT in the early sixties who were the first to use computers for anything other than computing things (the first computer game, the first chess computer, the first time that a computer is connected to a robot, etc.) and created a culture, the hacker ethic, in the process.
  • The people around the Homebrew Computer Club in California in the early seventies who were the first to create hardware at a scale that could work for hobbyists and in households
  • A group of Apple and Atari enthusiasts (fanatics?) who invented whole new genres of gaming and birthed the modern game industry in the early eighties.

Levy is an excellent writer (you have read In The Plex, haven’t you?) and through his writing I was immediately and completely awed by the brilliant playfulness of these geniuses.

The hacker ethic is something that still today has tremendous value. Levy teases out these principles from the MIT culture that he investigates:

  1. Access to computers—and anything that might teach you something about the way the world works—should be unlimited and total. Always yield to the Hands-On Imperative!
  2. All information should be free.
  3. Mistrust Authority—Promote Decentralization. (From the book: “Bureaucracies, whether corporate, government, or university, are flawed sys-tems, dangerous in that they cannot accommodate the exploratory impulse of true hackers.”)
  4. Hackers should be judged by their hacking, not bogus criteria such as degrees, age, race, or position.
  5. You can create art and beauty on a computer.
  6. Computers can change your life for the better.

Paragraphs like this:

As for royalties, wasn’t software more like a gift to the world, something that was reward in itself? The idea was to make a computer more usable, to make it more exciting to users, to make computers so interesting that people would be tempted to play with them, explore them, and eventually hack on them. When you wrote a fine program you were building a community, not churning out a product.

made me understand more fully why Richard Stallman is so pained thinking about what we lost. Greenblatt is also pretty vocal:

The real problem, Greenblatt says, is that business interests have intruded on a culture that was built on the ideals of openness and creativity. In Greenblatt’s heyday, he and his friends shared code freely, devoting themselves purely to the goal of building better products. “There’s a dynamic now that says, ‘Let’s format our web page so people have to push the button a lot so that they’ll see lots of ads,‘” Greenblatt says. “Basically, the people who win are the people who manage to make things the most inconvenient for you.”

Some things haven’t changed though. Go to places like Fosdem and you realize that the following is still the case:

It is telling, though, to note the things that the hackers did not talk about. They did not spend much time discussing the social and political implications of computers in society (except maybe to mention how utterly wrong and naive the popular conception of computers was). They did not talk sports. They generally kept their own emotional and personal lives—as far as they had any—to themselves. And for a group of healthy college-age males, there was remarkably little discussion of a topic, which commonly obsesses groups of that composition: females.

There is a lot of hacker wisdom:

[..] An important corollary of hackerism states that no system or program is ever completed. You can always make it better. Systems are organic, living creations: if people stop working on them and improving them, they die.

This book was written in the mid eighties and discusses some topics that are still relevant today. Read the following paragraph and think about the current battle between Android and iOS: hackers insist

[..] that when manuals and other “secrets” are freely disseminated the creators have more fun, the challenge is greater, the industry benefits, and the users get rewarded by much better products.

We also encounter Bill Gates and Steve Jobs right at the start of their companies. I thought it very was very funny how already then they showed something of their later self: Gates was complaining publicly in 1976 how everybody was just copying his version of Altair Basic without paying for it and Jobs was already purely focused on marketing, the user experience and what the actual hardware would look like (even when you opened the Apple 2, it had to look neat and accessible).

We absolutely have to thank O’Reilly for republishing this classic!

Reflecting on Lift France 2011: Key Themes

A couple of weeks ago I attended the Lift France 2011 conference. For me this was different than my usual conference experience. I have written before how Anglo-Saxon my perspective is, so to be at a conference where the majority of the audience is French was refreshing.

Although there was a track about learning, most of the conference approached the effects of digital technology on society from angles that were relatively new to me. In a pure learning conference, I am usually able to contextualize what I see immediately and do some real time reflecting. This time I had to stick to reporting on what I saw (all my #lift11 posts are listed here) and was forced to take a few days and reflect on what I had seen.

Below, in random order, an overview of what I would consider to be the big themes of the conference. Occasionally I will try to speculate on what these themes might mean for learning and for innovation.

Utilization of excess capacity empowered by collaborative platforms

Robin Chase gave the clearest explanation of this theme that many speakers kept referring back to:

Economic Logic of Using Access Capacity by Robin Chase
Economic Logic of Using Access Capacity by Robin Chase

This world has large amounts of excess capacity that isn’t used. In the past, the transaction costs of sharing (or renting out) this capacity was too high to make it worthwhile. The Internet has facilitated the creation of collaborative platforms that lower these transaction costs and make trust explicit. Chase’s most simple example is the couch surfing idea and her Zipcar and Buzzcar businesses are examples of this too.

Entangled with the idea of sharing capacity is the idea of access being more important than ownership. This will likely come with a change in the models for consumption: from owning a product to consuming a service. The importance of access shows why it is important to pay attention to the (legal) battles being fought on patents, copyrights, trademarks and licenses.

I had some good discussions with colleagues about this topic. Many facilities, like desks in offices, are underused and it would be good to try and find ways of getting the percentage of utilization up. One problem we saw is how to deal with peak demand. Rick Marriner made the valid suggestion that transparency about the demand (e.g. knowing how many cars are booked in the near future) will actually feed back into the demand and thus flatten the peaks.

A quick question that any (part of an) organization should ask itself is which assets and resources have excess capacity because in the past transaction costs for sharing them across the organization were too high. Would it now be possible to create platforms that allow the use of this extra capacity?

Another question to which I currently do not have an answer is whether we can translate this story to cognitive capacity. Do we have excess cognitive capacity and would there be a way of sharing this? Shirky’s Cognitive Surplus and the Wikipedia project seem to suggest we do. Can organizations capture this value?

Disintermediation

The idea of the Internet getting rid of intermediaries is very much related to the point above. Intermediaries were a big part of the transaction costs and they are disappearing everywhere. Travel agents are the canonical example, but at the conference, Paul Wicks talked about PatientsLikeMe, a site that partially tries to disintermediate doctors out of the patient-medicine relationship.

What candidates for disintermediation exist in learning? Is the Learning Management System the intermediary or the disintermediator? I think the former. What about the learning function itself? In the last years I have seen a shift where the learning function is moving away from designing learning programs into becoming a curator of content and service providers and a manager of logistics. These are exactly the type of activities that are not needed anymore in the networked world. Is this why the learning profession is in crisis? I certainly think so.

The primacy (and urgency) of design

Maybe it was the fact that the conference was full of French designeurs (with the characteristic Philippe Starck-ish eccentricities that I enjoy so much), but it really did put the urgency of design to the forefront once again for me. I would argue that design means you think about the effects that you would like to have in this world. As a creator it is your responsibility to think deeply and holistically. I will not say that you can always know the results of your design (product, service, building, city, organization, etc.), there will be externalities, but it is important that you leave nothing to chance (accident) or to convenience (laziness).

There is a wealth of productivity to be gained here. I am bombarded by bad (non-)design every single day. Large corporations are the worst offenders. The only design parameter that seems to be relevant for processes is whether they reduce risk enough, not whether they are usable for somebody trying to get something done. Most templates focus on completeness and not on aesthetics or ease of use. When last did you receive a PowerPoint deck that wasn’t full of superfluous elements that the author couldn’t be bothered to remove?

Ivo Wenzler reminded me of Checkhov’s gun (no unnecessary elements in a story). What percentage of the learning events that you have attended in the last couple of years adhered to this?

We can’t afford not to design. The company I work for is full of brilliant engineers. Where are the brilliant designers?

Distributed, federated and networked systems

Robin Chase used the image below and explicitly said that we now finally realize that distributed networks are the right model to overcome the problems of centralized and decentralized systems.

From "On Distributed Communication Networks", Baran, 1962
From "On Distributed Communication Networks", Baran, 1962

I have to admit that the distinction between decentralized and distributed eludes me for now (I guess I should read Baran’s paper), but I did notice at Fosdem earlier this year that the open source world is urgently trying to create alternatives to big centralized services like Twitter and Facebook. Moglen talked about the Freedombox as a small local computer that would do all the tasks that the cloud would normally do, there is StatusNet, unhosted and even talk of distributed redundant file systems and wireless mesh networking.

Can large organizations learn from this? I always see a tension between the need for central governance, standardization and uniformity on the one hand and the local and specific requirements on the other hand. More and more systems are now designed to allow for central governance and the advantages of interoperability and integration, while at the same time providing configurability away from the center. Call it organized customization or maybe even federation. I truly believe you should think deeply about this whenever you are implementing (or designing!) large scale information systems.

Blurring the distinction between the real and the virtual worlds

Lift also had an exhibitors section titled “the lift experience“, mostly a place for multimedia art (imagine a goldfish in a bowl sat atop an electric wheelchair, a camera captured the direction the fish swam in and the wheelchair would then move in the same direction). There were quite a few projects using the Arduino and even more that used “hacked” Kinects to enable new types of interaction languages.

Photo by Rick Marriner
Photo by Rick Marriner

Most projects tried, in some way, to negotiate a new way of working between the virtual and the real (or should I call it the visceral). As soon as those boundaries disappear designers will have an increased ability to shape reality. One of the projects that I engaged with the most was the UrbanMusicalGame: a set of gyroscopes and accelerometers hidden in soft balls. By playing with these balls you could make beautiful music while using an iPhone app to change the settings (unfortunately the algorithms were not yet optimized for my juggling). This type of project is the vanguard of what we will see in the near term.

Discomfort with the dehumanizing aspects of technology

A surprising theme for me was the well articulated discomfort with the dehumanizing aspects of some of the emerging digital technologies. As Benkler says: technology creates feasibility spaces for social practice and not all practices that are becoming feasible now have positive societal impact.

One artist, Emmanuel Germond, seemed to be very much in touch with these feeling. His project, Exposition au Danger Psychologique, made fun of people’s inability to deal with all this information and provided some coy solutions. Alex Peng talked about contemplative computing, Chris de Decker showed examples of low-tech solutions from the past that can help solve our current problems and projects in the Lift Experience showed things like analog wooden interfaces for manipulating digital music.

This leads me to believe that both physical reality and being disconnected will come at a premium in the near future. People will be willing to pay for having real experiences versus the ubiquitous virtual experiences. Not being connected to the virtual world will become more expensive as it becomes more difficult. Imagine a retreat which markets itself as having no wifi and a giving you a free physical newspaper in the morning (places like this are starting to pop up, see this unplugged conference or this reporter’s unconnected weekend).

There will be consequences for Learning and HR at large. For the last couple of years we have been moving more and more of our learning interventions into the virtual space. Companies have set up virtual universities with virtual classrooms, thousands and thousands of hours of e-learning are produced every year and the virtual worlds that are used in serious games are getting more like reality every month.

Thinking about the premium of reality it is then only logical that allowing your staff to connect with each other in the real world and collaborate in face to face meetings will be a differentiator for acquiring and retaining talent.

Big data for innovation

I’ve done a lot of thinking about big data this year (see for example these learning analytics posts) and this was a tangential topic at the conference. The clearest example came from a carpool site which can use it’s data about future reservation to clearly predict how busy traffic will be on a particular day. PatientsLikeMe is of course another example of a company that uses data as a valuable asset.

Supercrunchers is full of examples of data-driven solutions to business problems. The ease of capturing data, combined with the increase in computing power and data storage has made doing randomized trials and regression analysis feasible where before it was impossible.

This means that the following question is now relevant for any business: How can we use the data that we capture to make our products, services and processes better? Any answers?

The need to overcome the open/closed dichotomy

In my circles, I usually only encounter people who believe that most things should be open. Geoff Mulgan spoke of ways to synthesize the open/closed dichotomy. I am not completely sure how he foresees doing this, but I do know that both sides have a lot to learn from each other.

Disruptive software innovations currently don’t seem to happen int the open source world, but open source does manage to innovate when it comes to their own processes. They manage to scale projects to thousands of participants, have figured out ways of pragmatically dealing with issues of intellectual property (in a way that doesn’t inhibit development) and have created their own tool sets to make them successful at working in dispersed teams (Git being my favorite example).

When we want to change the way we do innovation in a networked world, then we shouldn’t look at the open source world for the content of innovation or the thought leadership, instead we should look at their process.

Your thoughts

A lot of the above is still very immature and incoherent thinking. I would therefore love to have a dialog with anybody who could help me deepen my thoughts on these topics.

Finally, to give a quick flavour of all my other posts about Lift 11, the following word cloud based on those posts:

Lift11 Word Cloud
My Lift 11 wordcloud, made with Wordle

Quick Lessons From Losing an iPad

A couple of weeks ago I forgot my iPad on the train.

After getting over the initial overwhelming feelings of idiocy on my part, I started thinking a bit deeper about the consequences and whether I had taken sensible precautions to mitigate those consequences.

The Problems

A couple of problems dawned on me:

  1. I had lost something that is quite valuable (one colleague told me with some measure of sincerity: “Nice gift for somebody else”). I don’t spend €700 casually and was distressed about losing something that is worth that much.
  2. More important than the device is the data that is on it. There are two potential problems here. The first is that you might have lost access to data that is important to you. The second is that somebody else suddenly might have gained access to your data. Both of these made me feel very uncomfortable.
  3. Finally, losing the device made it clear to me that all iPads look alike, especially in their locked state, and that there is no way for an honest finder to know who the rightful owner of the device is.

The Solutions

So here is my advice on how to minimize these problems. I recommend for you to apply these immediately if you haven’t done so already.

  • Fully insure your device (I had actually done this). Even though this is prohibitively expensive and even though you really shouldn’t insure devices if you can afford to replace them yourself (those insurance companies have to live of something), I still think it is a good idea as there are so many things that can go wrong with it, just through bad luck. I take the cost of the insurance into account when buying the tablet and amortize that over two to three years.
  • Ask yourself this question: Could I throw my current device in the water, walk over to any random computer with a browser and an Internet connection and access all the data that matters to me from there? If next, you would get a new device, would you be able to easily get that data back on the device? If your answer is no to either of these questions you should change your strategy. Some people might think I ask for too much as they are happy to backup to iTunes. I prefer to be as independent from iTunes as possible (I only use it for updates) and think most people would still lose a couple of days of data if all they had was an iTunes backup. Even before I lost my iPad, I was ok in this area. Here are some of the things that I have done: I like to have all my data in apps that keep both a local copy (for when I am offline) and transparently sync to the cloud. For email, contacts and my calendar that is easy: I use Google Apps for my domain and set it up to sync (you have your own domain right?). My task are managed with ToodleDo. My news reader of choice is Google Reader. All my notes are done with Momo. I have copies of my most important documents synced in a Dropbox folder. Dropbox also provides the syncing architecture for my iThoughts mindmaps and for the large collection of PDFs I have sitting the Goodreader app. I buy my ebooks DRM free and read them with Goodreader or I get books as a service through the Amazon Kindle bookstore. Apple now allows easy redownload of the apps you have purchased in the past.
  • Make sure you set a passcode on your iPad (this I had done too). I’ve set it up so that it only comes on after a couple of minutes of being in standby mode. This why I get to keep some of the instant on and off convenience, but also know that if somebody steals it from my bag they won’t just be able to access my data. One thing I am still not sure about is how secure the passcode lock is. What happens when people try to connect a stolen iPad to their iTunes? Is there access to the data?
  • Find my iPad
    Find my iPad

    Apple provides a free Find my iPad service. I had never bothered to set it up, but have since found out that it literally only takes two minutes to do. Once you have it installed you will be able to see where your iPad is, send a message to the iPad and even wipe its contents remotely. All of this can only work once your iPad has an Internet connection though.

  • Finally, I have downloaded a free iPad wallpaper and have used GIMP to add my contact information on top of the wallpaper file (making sure not to put the info underneath the dialog that asks for the passcode. This way, when somebody with good intentions finds the iPad they will have an easy way to find out who the rightful owner is.

To finish the story: a couple of days after I lost my iPad I called the railway company to see if they had some news for me (I had asked them to try and locate it as soon as I realized it was missing). They told me a fellow traveler had brought in my iPad to the service desk and that I could pick it up. Unfortunately, I have no way of thanking this honest person, other than by writing this post.

A Review of the “Moodle 2.0 for Business” Book

 

Moodle 2.0 for Business
Moodle 2.0 for Business

Packt is a new type of publisher. They have found a model that allows them to publish books (likely on demand) in what other publishers might call niche markets. They are usually the first publisher to have a book out about a particular open source product. They leverage the enthusiasm that exists in these communities in how they recruit writers, they stroke people’s egos by asking them to become (technical) reviewers of the books and they do most of the hard work that is necessary to create a book in countries that have lower wages than (Western) Europe and the United States. All of this means that the quality of the books is a bit hit or miss.

Another trick up their sleeves is the way they promote their books. They seem to understand the Internet well and offer bloggers review copies of books. I was offered a free copy of Moodle 2.0 for Business, Implement Moodle in your business to streamline your interview, training and internal communication processes by Jason Cole, Jeanne Cole and Gavin Henrick in return for a review. So here goes!

Most books about Moodle assume an educational setting. As I know a lot about Moodle and am starting to understanding corporate HR more and more every day, I was curious to see what I could learn from this title. The authors of the book have a very deep understanding about Moodle and have all used it for years (as they write “The authors of this book have collectively spent more than 5,000 hours experimenting, building, and messing about with Moodle”). They are active members of the Moodle community and work for a Moodle partner. In many places their hard-earned experience comes through like when they point out a fundamental flaw in Moodle richly complicated roles and permissions system on page 194. The books contains a few suggestions and warnings and I would recommend any reader to heed to them.

The books kick of by trying to to answer the “Why Moodle?” question. It nicely lists five learning ideas that form the core of Moodle’s educational philosophy (I must have mentioned them before many times, but they are worth repeating):

  • All of use are potential teachers as well as learners – in a true collaborative environment we are both
  • We learn particularly well from the act of creating or expressing for others to see
  • We learn a lot by just observing the activity of our peers
  • By understanding the context of others, we can teach in a more transformational way
  • A learning environment needs to be flexible and adaptable, so that it can quickly respond to the needs of the participants within

The authors also mentioned the 2008 eLearning Guild survey about Learning Management Systems: “Moodle’s initial costs to acquire, install and customise was $16.77 per learner. The initial cost per learner for SAP was $274.36, while Saba was $79.20, and Blackboard $39.06”. Even though I think the survey is comparing apples with pears, I still think it says something: Moodle could be a way to get more functionality out of the same budget. Another good reason to choose Moodle is is that it “makes it easy to try things, figure out what works, change what doesn’t and move on”.

The meat of the book is a set of chapters which look at different parts of the HR process finished with a case study of a company or organization which has done something similar (see here for an overview of all the chapters in the book). Through these chapters a lot of the different Moodle functionalities are explained in very concrete terms. Many of the examples make quite creative use of Moodle. One of the first chapters for example deals with the hiring and recruitment process. Moodle is used to capture people’s resumes, rate the resumes, let people choose an interview slot and assess people with a simple online test. The authors have a pleasant tone and are not afraid to share their own failures to make the reader learn (like when they set up quiz questions in the wrong way, page 47).

Some of the case studies give real insight into the path that these organizations have travelled. I particular like the enlightening example from the Gulf Agency Company (GAC) corporate academy starting on page 164:

After a less than successful strategy of purchasing off-the-shelf SCORM content, GAC has now move to developing courses with a combination of internal subject specialists, HRD e-learning consultants, and facilitators. The course content is uploaded into Moodle course page with GAC-specific assignments and discussion forums added. There is a clear strategy to ensure that the learner does not simply click through a series of screens without context or interaction. Interaction and collaboration in courses is now a fundamental part of the learning process, with the courses tightly integrating content, tasks, and collaboration.

Through these chapters we get some good explanations of functionality that gets glossed over in many of the other books on Moodle. There is a good explanation of the database module, outcomes (a Moodle word for competences) are explained, the new way of setting conditions for accessing particular parts of the course and for considering a course complete get good attention and they have found some useful examples for relatively advanced role configurations. On the slightly more technical side they give sensible advice on how to install modules (page 209) and I love the fact that they explain how you create your own language for the interface (something that is usually very hard to do in other systems) on page 285.

The book ends with a few chapters that show you how you can integrate Moodle into application landscape. There are some good explanations about using webconferencing/virtual classrooms, the portfolio and repository APIs are used and they show you the first steps towards integrating authentication and enrollment.

The book has some minor areas that could be improved. It is written by three authors and seems to keep switching perspectives between the author as “we” and the author as “I”. Also, ocassionally the case studies become too much of an advertisement for a Moodle partner: “The uniqueness, and in some ways, complexity of the project meant that A&L were keen to engage with a service partner that had extensive knowledge of Moodle to enable them to bring the project to a succesful completion. Ennovation not only had the Moodle knowledge and experience that A&L were looking for, but also a proven reputation in the legal sector with their long term customer, the Law Society of Ireland.”

There are also a few things missing that I was hoping to read more about:

  • The explanation of the portfolio and repository APIs wasn’t conceptual enough. I am not just sure that the average reader will be able to generalize from the exampls and see what a gamechanger this type of technology can be when it is embedded correctly in the organization.
  • There is small battle going on in corporate Moodle land. Multiple service providers are creating their own more commercial “distributions” of Moodle with extra functionality that is relevant for enterprises: Remote Learner publishes ELIS, Moodlerooms has joule and Kineo and Catalyst have come together to create the aggresively marketed Totara LMS. The book never mentions this (I can think of good reasons why this is the case), but it is highly relevant to know more about these systems if you are considering using Moodle in your organization.
  • Related to the previous point is reporting. Moodle is not known for its strong enterprise reports and this is something that many organizations commission some functionality for. It would have been nice if reporting had gotten a similar treatment as web conferencing. Maybe we can get that in the next updated version?

All in all this is strongly recommended reading for any curious person who uses Moodle professionally in an organization, no matter the level of their expertise.

Get it here if you want to let Packt know that you’ve read the review, they use this link to monitor which blogs give them the highest amount of traffic and might ask me to review another book if this link gets clicked on often. Get it here if you don’t want to pay any shipping costs and don’t mind me getting a 5% percent commission. Get it here if you like Amazon and don’t mind me getting a neglible commission. Get it here if you don’t like be tracked, live near London, love bookstores and are willing to call first to see if they have it in stock. Seriously, Foyles is a treasure.