"Badges seem to be gaining the most traction in career readiness, particular for so-called 'middle skills' jobs that require more than high school degree but less than four-year college degree," writes Michael Feldstein. "Increasingly, these jobs need an associate’s degree plus something extra." As well, he's "beginning to hear anecdotes of colleges and universities working with area high schools to create badges around college readiness and earning AP-style credit." Think of it as high-school-plus.
Martha Burtis discusses the use of "the Trojan Horse approach" to implementing Domain of One's Own (DoOO) at a college or university. "Jim Groom has talked periodically about ePortfolios being a Trojan Horse that allowed us to pilot Domain of One’s Own at UMW," she says in this speech transcript. "[It] represents a kind of pragmatism that I think we need to consider and unpack." It forces us to think about the naming of things, the building of things, and even the breaking of things. "When we start down these paths — these more complex paths and conversations about what it means to name and to build and to break and to fix, we come to a far richer place than just a space where students can build beautiful, rich, powerful Web sites. We are in the territory now of not just naming or building or even breaking but the territory of knowing the Web."
This is a list of a bunch of things we expect next-generation learning technology to be, most of which existing LMSs are already in the process of implementing: social network services, knowledge aggregation, mobile learning support, performance management, internal recruitment, and so on. It just seems to me that every one of these things is so much better outside the enterprise or institutional context. But one thing that did not make the list was 'open'.
Ignore for the moment the fact that this article is about open source code, and pretend it's about open educational resources or something similar. The advice it give becomes spot-on. For example, is it readable? "Readability can be good naming conventions for identifiers, good spacing, clear readable logic, well-understood scopes." Exactly. Is the resource actively maintained? Is it well-tested? Are other people using it? And is it documented? "Documentation makes [resources] much easier to understand, use and modify. It’s also a great indication for the thought and carefulness the developer who wrote the [resource] put into it."
This newsletter is sent only at the request of subscribers. If you would like to unsubscribe, Click here.
Know a friend who might enjoy this newsletter? Feel free to forward OLDaily to your colleagues. If you received this issue from a friend and would like a free subscription of your own, you can join our mailing list. Click here to subscribe.
Copyright 2017 Stephen Downes Contact: email@example.comThis work is licensed under a Creative Commons License.