e-Literate

Present is Prologue

Author: Michael Feldstein

  • Cracking the Code

    I sometimes get frustrated with the strong allergic reaction that even many good educators have to the request for hard data as part of an educational decision-making process. This allergy shows up in all different ways in all different places. In elementary school, for many years (and this may still be true today, for all I know), you could predict a person’s position on reading education based on their political disposition. Liberals liked whole language and conservatives liked phonics. James Moffett wrote a riveting if ultimately one-sided account of the conservative attachment to phonics (among many other things), with the more extreme proponents making claims like, “Phonics cured my daughter’s asthma!” (No, I’m not joking.) I have seen no corresponding documentation of the liberal version of this bias, but I have known many teachers, invariably liberals, who have vehemently asserted the value of whole language, where the only evidence they had was that most of the (middle-class) kids (from educated families) in their classrooms learn to read just fine. Nowhere in these debates was a discussion about whether it might be a good idea to construct some empirically rigorous tests to indicate which approach might provide what kinds of benefits under which circumstances. There are some things in education that do not lend themselves to rigorous empirical study, but this is not one of them—especially these days with the improvements we have in brain imaging equipment.

    Another example: When I was a PhD student in English, I called a meeting of my fellow graduate students to discuss what we could do to improve the quality of our pedagogy. Mind you, this was at a department with a strong composition program that prided itself on its commitment to teaching. One suggestion I raised was that we could run a norming session for the English 101 final essays so that we could share best practices and ensure we were grading progress consistently across the program. This wasn’t a crazy suggestion from out of the blue; it was a successful practice that was already being employed in other universities. Yet you would have thought that I was asking everyone to get bar code tattoos on their foreheads. Somehow, taking such an step would violate their fundamental rights to individuality as professors, and besides, you can’t “norm” a thing like that. Teaching is an art, I was told.

    The same sort of tension frequently creeps into educational technology conversations when it comes to anything remotely smacking of assessment, grading, or analytics. Test engines and grade books are derided as mere “management” tools, while retention early warning systems are apparently the first wave in the Rise of the Machines. As with the cases of phonics and final exam norming, these conversations are immensely frustrating to me in large part because I often find myself arguing with some of the talented, creative teachers who I respect the most. And I don’t always handle these situations well. (See for example, my somewhat snippy response to my friend Joe Ugoretz regarding the value of grade books and test engines or my regrettably snarky swipe at Jim Groom regarding the death of the LMS.) I think it’s mostly because I’m trying to convince myself that I’m not crazy, that I’m not some kind of Cylon or Terminator sleeper bot. Why am I the only teacher who sees it this way? What’s wrong with me?

    It is therefore with great relief that I read Education Secretary Arne Duncan’s comment on the value of analytics:

    Using technology to improve student achievement makes teachers feel almost as if “they’re cracking a code,” he explained. With adequate student data, teachers come to realize that effective instruction is not based on “just a guess or an assumption or a hunch, and all that is being driven by technology.”

    Yes. That is how I feel.

    I think there is a fear—a legitimate fear, bourne out by history and experience—that the bureaucracy will take the raw data as a substitute for judgment of teachers and students. I get that. It’s something to be fought vehemently. And maybe the tools we have today have more bureaucratic influence on their design than they should. But this is no reason to reject the value of data, or the scrutiny of peer review, or the use of tools that provide visible and measurable data regarding student activities. Like doctors and engineers, teachers are professionals. Nobody seriously imagines that the existence of an fMRI machine makes a doctor’s judgment less important. To the contrary, the more data we have, the more we benefit from the judgment of a trained and experienced expert.

  • Sakai 3 As Mac OS X, Part Deux

    At the risk of sounding a little silly, I’m going to attempt to extend the analogy between Sakai 3 and Mac OS X that I made in my last post. The reason I think this exercise is worth trying is that the Mac OS X transition is a relatively clear and uncluttered example of a successful rearchitecture of a product with an installed base, and it provides us with a good model of what could happen with Sakai 3 if the initiative is executed well over a number of releases. Please understand that I am not predicting anything here. I’m just trying to model possibilities so that we can set a ceiling on expectations.

    (more…)

  • Sakai 3 Is Like Mac OS X

    There’s an important point about the the forthcoming Sakai 3 that probably has escaped most casual observers. It is close to a ground-up rewrite. Sakai 3 is to Sakai 2 as Mac OS X was to Mac OS 9, in the following ways:

    • The technological heart (or kernel) of the new version is completely different from the old version.
    • That kernel leapfrogs many current-generation architectures (which are really aging legacy architectures, for the most part) for software of its category.
    • Some of the applications that run on the old version will be able to run on the new version with some modest to moderate development.
    • Other applications on the old system will have to be completely re-implemented on the new system.
    • Still other applications could run on the new system with some tweaking (and probably will for a couple of versions), but they will seem awkward in the new environment until they are re-implemented.
    • Users who have lots of apps that they want to carry over in the old environment will probably want to run that old environment together with the new one in some sort of co-existence mode. New adoptees will care less about that and skip co-existence mode, provided that the new system has the apps that they need.
    • At some point, co-existence mode will go away and adoptees will have to migrate to the new system to stay current. How current adoptees respond to this transition will be largely a function of how well the migration path is done, but some users who are attached to the way the old system worked will have trouble letting go regardless.
    • The first release is likely to have some very impressive capabilities as well as some feature gaps and rough edges. It will be suitable for full replacement use by some, for piloting by others, while still others will want to wait for another release or two. (Whether the 2010 milestone release of Sakai 3 is more like OS X 10.0 or 10.1 in this respect remains to be seen.)
    • The new kernel will likely enable accelerated innovation and impressive progress from release to release, with feature gaps getting filled quickly and new capabilities that nobody has seen before coming too.

    I think there is a good chance that, within a few releases, Sakai 3 will be a trend-setter in its category much like Mac OS X is.

  • Blackboard Learn President Ray Henderson Starts a Blog

    This is good news. Former ANGELista and current Blackboard Learn President Ray Henderson has started a blog, where he says he will respond to conversations in the blogosphere and generally try to make Blackboard more transparent. He has also turned blog comments on, which he acknowledges is a small deal in the wider world but a non-trivial deal for a corporate blog. (This is true.) Maybe he’ll respond to my post on three tests for the”new” Blackboard.

    In marginally related news (under the heading of “openness”), I learned from Blackboard folks on Twitter that Blackboard’s API documentation is available without requiring a contract or login at their EduGarage site. FWIW.

  • EduPatent Updates

    On the one hand, Thomson Reuters’ lawsuit against Zotero has been dismissed. Details are scant at this point. We don’t yet know the grounds for dismissal or whether Thomson Reuters will pursue other legal action. On the other hand, the U.S. International Trade Commission has agreed to investigate whether Desire2Learn is violating trade laws with patent infringement on some of the claims in Blackboard’s original ‘138 patent.

  • Does Google Wave Mean the End of the LMS?

    Does Google Wave Mean the End of the LMS?

    I suppose it was inevitable. At a time when even The Chronicle is asking whether Blackboard can be replaced by WordPress, a slick demo of a super-cool product like Wave was bound to trigger breathless speculation about the demise of the LMS. Equally predictably, the most enthusiastic predictions that the LMS will be replaced are being made by people who have already replaced their LMS. It is not terribly shocking to read Jim Groom predicting that this time the LMS is REALLY doomed!!!! (I mean that to be taken affectionately.) If you are comfortable teaching a class using WordPress or PBWiki or [insert hip and free Web 2.0 technology du jour], then there is a good chance that you will be comfortable teaching a class with Wave.

    Me, I’m a live-and-let-live kind of guy. I think people who are comfortable using these flexible tools and who don’t want the traditional trappings of an LMS (e.g., grade book, assignments tool, test engine, etc.) should be able to have what they want,  while the people who want the full LMS toolset should also have what they want. That’s one reason why I think we need a Learning Management Operating System (LMOS) upon which flexible and individualized virtual learning environments can be instantiated. If you want a grade book and a test engine, great. We got those. If you don’t want ’em, that’s fine too. Let pedagogical needs and university policies drive these decisions rather than the technology.

    So the question I’m interested in is more nuanced than the one of whether the LMS is “dead.” What I want to know is where Wave could fit with the range of capabilities that somebody might want in a virtual learning environment. What is it not good for? What else does it need?

    (more…)

  • The Sakai Product Council

    I am delighted to announce that I have been selected to be a part of Sakai’s new Product Council. As Michael Korcuska explains,

    The Product Council has two important roles: determining which components will be included as part of each product release, and informally advising projects as they progress from R&D to production-ready maturity. As a community-developed open source project, components of each product release are contributed from many different institutions, companies and individuals. The Product Council is the coordinating body for each release, and will work to assure the product’s evolution continues to meet the needs of the educational community in terms of functionality, production worthiness, and usability.

    The group sports an all-star cast. I am honored to be in their company.