Monthly Archive for June, 2004

Project Looking Glass fallacy

Sun released a public version of their 3D desktop Project Looking Glass. There is a demo video with Jonathan Schwartz (weblog), Executive Vice President of Software at Sun Microsystems, who claims:

The dominant company that provides the desktop doesn’t want to show you that [innovation on the desktop] because they do not want to do the work that actually reinvents the way things have been done. They want to keep it to the way things have been done for that past ten years. We think there are some deficiencies there.

Before making that claim he ran through a demonstration of the interface. Besides of the fact that his claim about (obviously) Microsoft not research 3D at the desktop is untrue, Project Looking Glass in the current stage is 3D – but that’s all about it.

None of the shown features improve productivity of end users. The window placement features barely help to avoid screen clutter and real world metaphors (like browsing through a pile item per item) seems to be exactly the interaction style the inventors of the GUI wanted to get rid of. The only good thing about Project Looking Glass is that it seems to be open source and potentially will be adopted by people with better ideas. But without a truly killing application (and I haven’t seen one in the demo) Project Looking Glass may not seem to be attractive enough for end users.

OS X Tiger preview

I just had a look at the WWDC 2004 keynote (did I see Francis Ford Coppola in the audience a couple of times?). The upcoming release vo Mac OS X 10.4 Tiger comes with a collection of features that in general appear to be focussing on productivity and efficiency. Spotlight – the instant searching – and Automator (Screenshot)- an application to pipeline AppleScripts visually – will make a great pair. And I don’t even want to imagine the productivity leaps that are hidden in Core Image or the H.264 codec. iChats multiparty conferencing is great, but I’d have loved to see screen sharing and being able to give remote presentations with keynote.

I don’t know if I will ever be able to work on that 30″ inch display, but I am sure that such a screen will change the way layouts are done on a computer (I pass an Apple dealer once in a while I am will need to have a look at this beast…). Unfortunatly the 30″ inch version will never pair with PowerBooks, because a special graphic card is required to run a screen with 4.1 million pixels (and it can even drive two of these giant displays with weird cables).

What I am wondering is that Apple again integrates functionality that is currently making a living for some small developers: Dashboard is clearly a Konfabulator clone. It is like a deja-vu of Sherlock 3 becoming a Watson clone. Dashboard and Sherlock are “stolen ideas” and cause a threat to small developers that need to be fearful if Apple is going to steal their tool on the next OS release. This is especially amazing because neither Sherlock 3 nor Dashboard seem to be killer applications: they are more like fancy examples of interface add-ons. An insider comment claims Steve Jobs may not have seen Konfabulator (but in fact Jobs is claiming Konfabulator stole the idea from the older Apple MacOS in the first place).

Safari RSS (and it is not called “Safari ATOM”!) is different: while it may to some degree kill NetNewsWire Lite I do think that it could be more dangerous to OmniWeb & other commercial web browsers. Brent Simmons (author of NetNewsWire) comments on this. NetNewsWire Pro may even increase sales, because everybody will learn about RSS and Atom.

Interesting stuff also can be found in the sneak peek page for Tiger Server: there will be a weblog server integrated in Tiger based on Blojsom – apparently a JAVA based Bloxsom clone.

So we’ll see a new release of the Microsoft Windows in 2006. That’s two years from now. In contrast to Tiger, the hardware demands for Longhorn seem to be dramatic: for a full Longhorn experience you need hardware that has yet to be produced. But by 2006 I will probably already comment on the first releases of of Tiger’s successor which may still run OK on my 2003 17-inch PowerBook (as Panther does right now on my 2001 15-inch PowerBook).

EdMedia blog panel

Adrian Miles jotted down his experience of the blog panel at EdMedia 2004 in Lugano. He concludes:

Key outcomes: a high level of interest in the possible use of blogs, confusion about how or why you would use them, questions and problems about how to encourage, foster and nurture their use with disinterested or resistant students, confusion and a difficulty in showing the distributed nature of blogging (something that I have to add to my presentation). It is clear that outside of Mortenson and Walker’s original essay on blogs the literature is surprisingly thin (outside of blogs) on a pedaogical ‘plan’ for the use of blogs that a novice blogger might use. The specific problem with this is that blogs are very much like design education – you have to learn by doing it.

I would have to say a lot about the last part, because I feel like the “learning by doing” principle takes on everywhere.

I was originally planning to join that panel, but I changed my mind. I really regret I could not make it to Lugano to meet those people, but as I explained to others in the panel via E-Mail before, as a contributing presenter to the conference, I was not willing to spent my free time on preparing a presentation, traveling at own expense and paying a high registration fee (exclusive events & prints). It’s arcane that there are places in the academic universe where this policy seems to go without saying.

Tinderbox improvements

Eastgate does inofficially keep development versions of Tinderbox on their public ftp server. The latest release is 2.2.1 d7. Tinderbox users that dare to run on a development release may find some very useful enhancements (like better map printing). Finally images won’t be rewritten at each HTML export. These images were uploaded anytime I synchronized this weblog. Now this overhead is gone.

How thinking goes wrong

Michael Shermer about twenty-five fallacies that lead us to believe weird things. What a great document about scientific thinking.

Platform vs. Strategy in E-Learning

I just heard an e-learning expert demonizing the platform discussion (e.g. “Which Learning Management System is best?”) while at the same time suggesting to evaluate Microsoft e-learning products.

Then I found this other quote someone called Björn from a discussion thread on Peter Baumgartners weblog:

… every system claimed to the-one. I find that boring more than ever… but the money still goes into projects which develop an more or less sophisticated e-learning-system as we could see during the discussion on thrusday afternoon. Germany, Austria and Switzerland still give money for the media-side of learning. And there is hardly any money for the “soft-side” of learning.

After anticipating the difference between non-tutored E-Learning (CBT) and tutored E-Learning (LMS) he seems to negate his own argument:

I think there are two things to do: 1. Develop tools – but not another learning-system or another cms. Develop tools that open new ways of learning and teaching, tools that enrich the distance education [...]. 2. Slowly change the way you teach.

The problem with this argument is twofold:

Firstly most decision makers don’t have a clear understanding of the difference between “Develop tools” and “not another LMS”. Most of them may know one LMS (if at all) and they would regard this system as being a “tool”. Secondly this “tool” appears to change the way someone teaches slowly, because while most may begin by digitizing their course materials 1:1 into the learning management system, they may learn from the application of that material in that context what might be particular strategies that need to be selected and changed to meet the expected “improvement”. So to start with inadequate material and learn from experience is better than to develop a theoretical E-Learning scenario from scratch.

So after reminding myself about some of the evaluation and decision making processes I witnessing I have to say that the platform discussion is a very good way to confront people with exactly the questions about what need to be changed in didactics and learning methods, because most people think that a change in their teaching methods is required only by the introduction by learning management systems. In other words: their teaching method was beforehand a result of the subject and their own learning experience – and now to some degree is supposed to be depend on the delivery format.

The platform discussion seems to be misleading, because it is often conducted with technically uninformed decision makers that need to decide on long term investments without being able to understand the full implications of any platform decision. So there is a tendency to cut short this discussion and rather just decide on a strategic framework and then leave the decision of the platform to the technicians or the IT department (or some enthusiasts among the faculty).

A platform discussion is part of the strategic decision making process. And the past years have crystalized some technical requirements for platforms to be systems for consecutive investments and growth of the economic effect of those investments:

  • Interoperability (strong import and export mechanisms; this also keeps up the pressure on the platform vendor to innovate)
  • Open standards support (a prerequisite of the above)
  • Customizability (a general way to integrate in a heterogenous environment as well as across institutions in regard to authentification, usage and access policies, storage and database systems at the backend as well as corporate design)
  • Cross-platform (so not depending on one OS or one client)
  • Modularity (any new system needs just to offer what is needed and not already there)
  • Scalability (necessary to be able cope with rising demand; but also: extensibile on demand)
  • Support (by external partners at reasonable cost while the platform should be capable to define a service market; but also means a wide and supportive community for issues)
  • Managability (minimal administrative overhead in relation to effect)
  • Variability (applicable for different didactic scenarios and assessment strategies)
  • Mandantors feature (allow generation of offsprings with acquisition from global contexts & objects and without setting up a complete new server)
  • Reusability of know-how (also means: learning curve for first time users and developers)
  • Repurposeability of editorial work (related to import/export mechanism and know-how alike)

There are a lot of implications to this list. But generally the shift of perspective is that “platform” should not be regarded as a collection of applications but rather as a framework of conventions manifestated in protocols, formats, services and methods on top of a plan about how to seed and grow knowledge about this framework and its facilitation among employees and faculty.

Bit I think what this list shows is that the platform discussion is indeed a strategic discussion. To say that the platform discussion is boring and we need to have a discussion about educative scenarios does only suggest that the aspect of “variability” was not discussed deep enough in the past. It also might be regarded as a symptom of the fact that players in institutions don’t like to re-invent every “technique” they already found to be effective. The “old” platform discussion also allowed IT departments to control the process and limit the strategic discussion on personal taste. And finally decision makers were sometimes unable or unwilling to really get into the details of each of the points – or – were lost in the details of these aspects.

So without a good understanding of the strategic relevance of a platform for many players in the discourse about educative scenarios cannot be a symbiose between technology and user needs.

There has been a large trend to outsource skills from institutions into companies. Many of these institutions now have learned to in-source competence and knowledge again as they face the effect of the continuous experience loss: they simply underestimated the severity of the drain of flexibility due to inaccessible experience. In regard to E-Learning I am convinced that there will be the need for a constant revision of the didactical strategies and the enabling technologies involved. Beside of research capacities the “didactical strategies” are the core of what universities actually offer as market value. If universities try to outsource too much of the technology business they actually try to circumvent the need to control the technology involved with their core service as well. This will only postpone the recognition of this interdependence.

So the platform discussion is not of marginal relevance for the strategic decision making. But I can’t remember a case where this discussion was going beyond the question of this or that application and this or that tool. And in this sense “platform discussions” I witnessed actually have never been real platform discussions. The subtext of those discussion has always been if there should be an anti-cyclic investment into open source (insourcing) or a cyclic investment into commercial vendors and their services (outsourcing).

So really the question of investments into open source is not only a question of available support for a system. If that would be true, then I would have a hard time to explain how this open source phenomenon came to existence at all.

Wiki added!

So I managed to add a wiki space to this site. It will take some time to grow. You’re invited to add yourself to a list of guests or suggest topics.

Ruby on rails

It is actually the first time that I blog about Ruby. I had a look at Ruby on Rails – a web application framework based on the Ruby scripting language. Ruby appears to be a very well designed scripting language (see here) for anyone who loves “quick but not dirty” programming.

Ruby is very successful in Japan, where it has already taken over Python in popularity (see here). Quote: “Ruby puts the fun back into programming.”

Realtime Wiki

I am playing around with Wiki tools. Because Zope is the platform on my current development agenda I looked into ZWiki. It offers full Plone integration and support for the ExternalEditor Extension (which means that I can click on small pens to edit pages inside my favorite text editor instead of a textarea inside the browser).

But what I would like to use is a wiki-enabled editor that allows clicking CamelCase words right after they are typed (which would create a new wiki page or open an existing one for editing).

VoodooPad does this (even with remote wikis). But currently it uses a proprietary Vpwiki API that is only supported by VoodooPads own server tool, by TWiki (with this experimental extension) and by the FreeCard project (FreeCard is planned to be an open source HyperCard clone). I could not yet find anyone trying a Vpwiki API Extension for ZWiki.

There are several other RPC API designs for wiki servers, for example: XmlRpcToWiki by 0xDECAFBAD (who has collected some links to some other efforts).

PersonalWiki is a graphical Wiki editor like VoodooPad that has an experimental and rudimentaty HTTP-based implementation for remote editing. It comes with an example script for a ZWiki site. Unfortunatly the usability is not very good: unlike VoodooPad you need to toggle Browse and Edit (the example script also has a syntax error that prevents saving existing pages).

So what if Peer-2-peer networking (or Rendezvous maybe) would be paired with such an editor? Editors would see the remote wiki and any change would be probagated to all connected clients.

And frankly: this has been an idea first sighted at Ray Ozzie’s weblog almost a year ago. And Hugh Pyle from UK needed just five hours to hack a tool with the Groove Web Services framework. He called it “Hyki” (from “Hydra” + “Wiki”; Hydra was the original name of SubEthaEdit). Insipred by this Tim Knip implemented something similar for Groove based on Flash.

Design + Knowledge Destruction

Rosan Chow reflects on work by Alain Findeli. She wants to help characterize design activity by projecting a fringe view on the relation between design activity and knowledge, scientific or non-scientific.

To me, the essence of design activity lies in the ontological realm and how it affects the way we are that is different than how science or for that matter other activities do. To assert that design activity destroys knowledge redirects our attention to the important and unique role design activity plays in this world in relation to science and other creative human activities. It pushes us to think hard about the contributions that design activity should be able of making.

There is a german translation available by Wolfgang Jonas.

Introduction to Apple Software Design Guidelines

Apple posts some notes on developing software for Macs. Brent Simmons recommends it not only for other developers but also for anybody who enjoys thinking about software.

How children can learn cognition science

Through a posting on the simplicity weblog I came across Edward De Bonos site. He started to collect bedtime stories for children that incorporate his theories. The first (and only) one by Lorna Santín tells about De Bonos concept named “Six thinking hats” and it’s called “The Magic Hats”.

Computer boosts cognitive agility of pre-school children?

CNN reports that computer use of children aged 3 to 5 scored higher on tests that gauge school readiness and cognitive development.

Some earlier studies have found computer use improves children’s fine motor skills and improves recognition of numbers and letters.

Is there a study that shows how extensive computer use in early childhood influences the social skills and empathy?

Patents can allow BigCos to annihilate open source?

This german news item (heise.de) speculates that software patents in Europe will allow big companies like Microsoft to kill the open source movement. It forces open source projects to play according to the rules of capital. Patents are nothing more than land mines in a economic war. I can’t see why Microsoft wouldn’t use patents like these against any open source project that Microsoft does not want to exist. Open Source will be what Microsofts wants it to be.

The problem is that open source projects are not designed to be profitable. Most projects I can think of would die if the software developers are forced to become lawyers and patent hunters.

Dave Winer today reminds his readers that he was aware of the problem while ago:

Five years ago I said here that it was time to do something about patents, if we wait, there will be a meltdown. I don’t think too many paid attention. Today patents are central to every software strategy, not because we’re all going to be defensive with them, as so many say.

Obviously software patents are here to stay. So what to do about it?

The European Union could offer free patents and consulting for any project that has been OSI certified and support initiatives that create ideas to patent these. These “free patents” could be used for at no cost by any OSI project. It could demand commercial projects to licence the patents while the licence fees could be determined to refund the free patent system and the open source project. So the price for free patents would be to have no 100% revenue of fees into the project itself.

The economic value would be that even the BigCos can use the enormous resource of free patents to improve their products.

Former Microsoft employee switched

Here is a little story of a former Microsoft employee that switched to MacOS X:

I worked for Microsoft for eight years. I’m a long time Windows loyalist. [...] Now that I can see them side by side, it’s obvious that the Macintosh provides a brighter display experience than the PC. It’s a more aesthetically pleasing visual experience. It’s less cluttered, and feels less stressful to use than Windows. The Mac just doesn’t get in your way the way that Windows does. [...] Apple’s innovation will be an inspiration and guide to Microsoft employees for some time to come.

Pros and Cons of Wikis in education

Here is a summary of experiences with using a Wiki in a educational project. Obviosly a Wiki structure has some advantages over a weblog system (more focussed on content creation and hypertext structure). A Wiki is better suited to generate a set of encyclopedic pages, while a weblog works better as a messaging and news hub in a group.

What I’d like to do is this: I’d start with a modest number of pages in a Wiki and then relate this to news items we collected over the last years. I really can see this being two sides of a medal: one for the activity related to particular courses – and one for glueing this all together with a number of short memos about particular keywords. The Wiki would be more result oriented with a long term vision – the weblogging would be work and task oriented with narrowed perspectives. The Wiki would offer orientation in the chaos – the weblogs would generate the buzz and the dynamics.

Designing success and small companies

Maish R Nichani on elearningpost.com:

Yet another article on the importance of design. This one from Inc. magazine reports that even small companies are using the design factor to gain a competitive advantage. (The May 17 issue of Business Week featured The Power of Design and the June issue of Fast Company featured Masters of Design.)

Simplicity (cont.)

Finally there is some movement on the weblog of the “simplicity” seminar. And some very good items popped up already.

For instance some explanatory animations by Nigel Holmes which look pretty much like the things we did in the “density” seminar. And also I learned that John Maeda at MIT started an experimental research project called “Simplicity” (I wonder who will fund such research here in Germany). Interesting as well: “Simplicity – Nine Theses” that have been presented at the equally named forum in September 1994 of the International Design Forum Ulm and Ulm School of Design Foundation.