(Okay, I admit it… this post is WAY overdue.) Let me begin by saying this is not a rant, but rather an honest account of my impressions regarding this year’s DevLearn. Nearly two months have passed, and when I think of DevLearn I think of two things: Social media gone wild, and hallway conversations. Social Media Gone Wild DevLearn 2009 was absolutely wonderful if you’re into incorporating social media into e-learning. Or should I say “using social media for learning,” without the “e.” Unfortunately for me, I’m not really interested in using social media for learning. I mean, I learn …
Someone recently posted a blog entry ranting about the use of the term “best practices” in our industry. I understand the frustration with thoughtless pronouncements about best practices, especially coming from people who may not know any better; it will often sound a lot like how like mom used to say “eat this, it’s good for you” without really knowing whether it’s true. However, there is a big difference between best practices in terms of learning theory — something that’s difficult to quantify and/or prove — and technology.
Kurt Melander was kind enough to clean up my Captivate 4 variable list and convert it to PDF format for those who’d like to print it out. Get it here. Thanks, Kurt!
It took me much much longer than I anticipated, but I am happy to announce the new CaptivateController utility.
This controller is not a simple rehash of the original pipwerks.captivate.control utility; it is a complete re-write that adds a number of extra features.
I’ve had a flurry of emails and messages regarding my SCORM cheat the past few days, and have received feedback from a number of well-regarded SCORM aficionados, some of whom contributed to the standard and helped make SCORM what it is today. This is wonderful, I’m very happy to hear from everyone, especially regarding such an engaging topic.
But as I hear more from these seasoned SCORM pros, I’ve made (what I believe to be) an interesting observation: there is a sharp division between die-hard SCORM developers and casual users. I suppose I’ve felt this way for a long time, but it’s really coming into focus this week. Let me try to define the camps.
I’m always surprised how little people talk about cheating in e-learning; maybe it’s a fear of revealing just how easy it can be. The fact is, SCORM — the most common communication standard in e-learning — is fairly easy to hack. I’ve whipped up a proof-of-concept bookmarklet that when clicked will set your SCORM course to complete with a score of 100 (works with both SCORM 1.2 and 2004).
I’d like to say thank you to all the people who posted in the pipwerks forum, and invite you to join me in the new eLearning Technology and Development group.
I’d also like to ask anyone and everyone who develops e-learning to drop by and sign up for the eLearning Technology and Development group. Ask questions — lots of questions — and let’s see if we can get a good community going!