One of the things we need to do in the next six months along with running workshops and updating our online content is to create some sort of badging to recognize people's skills and contributions. As we said in the proposal to the Sloan Foundation, "A badge program will provide near-term incentives for both learning and mentoring; a framework to support viral, peer-driven engagement with the program; and facilitate recognition by partner institutions and potential employers."
We're going to rely on Mozilla's Open Badges project to handle the mechanics of storing and validating badges, so we only have three questions to answer:
- What do we award badges for?
- How do we determine that someone has earned one?
- What do they look like?
The obvious answer to the first (and most important) question would be, "You get a badge for completing the core curriculum." However, one of the purposes of badging is to provide a finer-grained inventory of people's knowledge and skills, so there's an argument to be made for giving one badge per topic, e.g., a version control badge, a Unix shell badge, a basic imperative programming badge, and so on. The argument for is that their meaning will be clearer: if I say, "Jane knows the basics of Subversion," that's more immediately understandable than, "Jane has completed the core of Software Carpentry." The argument against is that if someone has collected two hundred small badges, we're going to aggregate them anyway ("Jane knows basic software development skills"), so why not just do that in the first place.
I've gone back and forth on this, but currently think that one badge for the core curriculum ("Basic Software Carpentry") will work best. We will offer two other badges as well: one for organizing a bootcamp, and one for contributing a medium-sized chunk of content (on the scale of one 5-minute video episode).
Having decided that, the next challenge is to determine when someone has earned a particular badge. The "Bootcamp Organizer" and "Content Contributor" badges are straightforward; telling when someone has mastered the core skills is not. We can tell that you've attended the bootcamp and viewed the videos, but how can we tell how much you've actually learned? "Solve this problem and email us the result" isn't good enough: you could get someone to do it for you , and even if you're honest, we can't tell how quickly you did it, how many blind alleys you went down, how often you did something in ten steps instead of one, and so on. In the short term, I think the solution is to do assessment in real time using desktop sharing, i.e., you share your desktop with me, I give you the problem to solve, and I watch you do it. This won't scale to hundreds or thousands of learners, but it'll get us through the next six months.
What will badges look like? A badge is just a small PNG file with a digital signature embedded in it (it's a neat little hack), so the graphic design is up to us. I like our current logo, but (a) it doesn't size down well, and (b) I've been wanting to redesign it anyway, since the blue-to-white fade in the background doesn't print well on t-shirts, coffee mugs, and other media. In keeping with our carpentry theme ("We're not teaching people how to build the Channel Tunnel, we're teaching them how to hang drywall"), I'd like an image that combines tools like hammers and saws with something like 1's and 0's to represent software, but I'm a lousy graphic designer—if any of our readers would like to take a crack at it, please let me know.
Finally, and most importantly, how can we get existing institutions—specifically universities—to recognize badges in some way? As much as we'd like people to value skills for their own sake, everyone is always busy, and always has more to do than time to do it. Can we persuade a few schools to list badges as non-credit items on students' transcripts (just as they might presently list a short course in presentation skills or entrepreneurship that doesn't count toward degree requirements, but required some work on the student's part)? If so, it would give people an extra incentive to complete the core curriculum, organize a workshop, or create some content for us, particularly in a tight job market where every small distinction counts.
 It's unlikely that someone would cheat on a Software Carpentry exercise, but in general, if badges take off and actually start to matter, the people who sell college students essays on Steinbeck at $30 a pop will start offering to write their online exams for $50 each.
Originally posted at Software Carpentry.