Archive

Archive for the ‘education’ Category

Productive Collaboration: Team Fortress 2 Manual

May 18th, 2010

SomethingOne of the coolest games I’ve ever played is Team Fortress 2.   While it’s tons of fun to play, one issue with it is that it doesn’t come with a manual.  Just over a week ago, reddit user ‘lolard’ posted this to the new to tf2 subreddit, asking us to solve this problem.  The reddit community responded.  We fired up an etherpad clone and got to work.  Here’s what we accomplished:

  • In less than 24 hours, we had written nearly 8,000 words.
  • Today, we’re close 13,000 words.
  • More than 50 people have contributed in some way.
  • 28 people have contributed substantially.
  • Gone through at least two major transitions in the style of writing: from 2nd person to third person, and from the voice being used.
  • 4 different websites (3 etherpad clones and crocodoc.com)
  • My copy of the manual is 56 pages long, formatted.
  • There is now a website: http://tf2manual.net/
  • We were flexible enough to neutralize trolls who deleted all our work.

The list can go on.  The message is clear: this has been a massive collaborative work that has produced something amazing in a very short amount of time.  I’ve been involved throughout the whole process, stepping up soon after lolard made the first post.  From this perspective, I’ve learned several things.

  1. The future is live collaboration at the level etherpad (and it’s clones) tried to provide.  Wiki’s are last generation technology that only slow things down.
  2. None of the etherpad clones were able to fully function at our level of collaboration, including the new Google Documents.  We used ietherpad, openetherpad, sync.in, and I privately tested Google Documents.  All of them experienced difficulties dealing with both the number of collaborators and the size of the document.  Sync.in functioned the best of the bunch.
  3. Crocodoc is awesome, but does not scale up to groups of more than 2-3, especially for a 50 page document.  It’s flash driven, and was extremely slow.  It claims to be ‘live’ in the sense of etherpad, but it really isn’t at the levels we were using it.  I had to refresh the page to make sure I was viewing all of the changes.
  4. Do not use the time slider on any of the etherpad clones.  This basically made the document useless for everyone over the next 20 minutes as the website did who knows what.  This feature worked great in the original etherpad, so I’m not sure why these clones have trouble with it.  Even sync.in had this trouble.

I can’t emphasize enough how much this changed my view of collaboration.  This has been collaboration how it’s supposed to be done.  While reflecting upon this experience, I’ve identified several reasons I think this went so well.

  1. We’re passionate about the subject.  Of course this is important and must appear on the list.
  2. We’re passionate about the community.  This is not necessarily an extension of the first point.
  3. There was no barrier of entry.  Once the pad was created, we could simply spread the URL around, and once people arrived on that page, they could start editing.  There was no registration, no waiting.  They could immediately jump in and start writing.  This was true for all the etherpad clones as well as crocodoc, and I applaud all of those websites for that.
  4. The latest work was immediately available, down to the keystroke.  We could see exactly what others were typing as they were typing it.  Corrections could be done within seconds, and they were not always done by the person who made the mistake.
  5. Version control was transparent.  We didn’t have to think about keeping track of a history; the application did it for us.  Hypothetically, we could even playback that entire history as it played out, but that feature was broken on every website we tried.

The biggest theme is that while we were all very good with technology, the technology was completely transparent.  We didn’t have to think about it (except when it broke, like with the time slider).  We just focused on what we were trying to do, and then we did it.

It’s been an amazing experience so far, and while this project is far from over, our parts are winding down.  Soon, we’ll have a nice manual for team fortress 2 users to go with all this valuable experience we’ve gained.

education , , , ,

Fun Times with Remote Desktop

April 16th, 2010

The iPad has been making a splash in the gadget world, and I’ve been strongly tempted more than once to go ahead and purchase one.  For now, though, I’ve been able to resist, and I am hoping to hold out for a Notion Ink Adam.  Pixel Qi screen, Rotatable Camera capable of recording HD, HDMI out, Android with Multitouch?  I’m sold.  But this post isn’t about that.  It’s about one of the reasons I want a tablet so bad:  Being able to use it while teaching.

Currently there are a few tablets that are available for use in the classroom.  The problem is “Tablet” is used in a bit of a different sense.  The tablet I have available to me is the Airliner from Smartboard.  This piece of hardware is truly a piece of crap.  Half the time it won’t connect to the computer, and when it does connect, the software fails to function correctly.  There is a better way to handle this type of functionality, and I think I’ve found one.

One issue with using a tablet like this is usability.  You’re controlling the computer through the tablet, but you can’t look at it.  It would be better if you could get a copy of the screen on the tablet itself.  Well, with these new tablet computers, it’s possible to do that.  You just need to setup a VNC server on the computer you want to connect to, and a VNC client on the tablet.

Well, I had the opportunity to borrow one of our faculty member’s iPads and go ahead and try this out.  There’s a lot of idiocy in this institution about network security and such, but I was able to finagle (to use a technical term) the server installation such that I didn’t have to go through IT to enable this functionality.  However, the iPad was having trouble connecting.  So I decided to use another computer in to test the connection.

I didn’t have a VNC client on any of the student machines available, but I did have one on my desktop computer upstairs. So I logged into one of the student machines, and used the Microsoft Remote desktop software to connect to my workstation.  Then I was able to use the VNC client on my workstation to remote into the instructor machine at the front of the classroom.  Everything worked perfectly.

Then I had a thought.  We run a piece of software called iTalc that enables us to view the screen of any of the students computers.  This piece of software is amazing, and I use it constantly while teaching, for diagnosing student problems, letting students demo different things from their computer, and proctoring tests, among other things.

So I opened up iTalc to open up the screen of the student’s computer I was on.

The circle was complete.  I was remoting in a complete circle using three different pieces of technology on three different computers.  I got a nice looking mirror effect on my computer, but I was also able to close it all down easily.  Here’s the final picture:

  1. Student Machine -> My Workstation (using RDP)
  2. My Workstation -> Instructor Machine (using VNC)
  3. Instructor machine -> Student Machine (using iTalc)
  4. The student machine was already connected to my Workstation.

Just a bit of fun.  Unfortunate the wireless bandwidth around here is so crappy the iPad was practically useless as a VNC client.  I’m going to have to figure out something else.

education , , ,

Lessons after a year Teaching

February 15th, 2010

I’m now in my second year teaching, and while I’ve learned quite a bit, I’ve still got a ways to go.  Here are a few things I’ve learned so far though.

  1. Students won’t do their readings if they’re not going to tested on it immediately.  Solution: require them to fill out worksheets concerning the readings as they do them.
  2. Test questions need to explicitly ask for details, otherwise students will not provide them.
  3. Nuances should sometimes be left unsaid, as they can confuse students.  There needs to be a balance between the basic required information, and the exceptions to the rule.
  4. As a general rule, accepting late work is a bad idea.  Students will abuse it.
  5. Bad class performance is most likely due to laziness and not inability to do the work.
  6. Sometimes you do have students that really can’t cut it.  I have yet to learn of a good way to deal with that.
  7. If you allow your students to be creative, they will blow your mind with their creations.
  8. Your actions have the biggest effect on morale.  You need to be able to make jokes and get them to laugh.
  9. You cannot be afraid to be wrong.
  10. Have discussion questions prepared ahead of time.  These need to be open ended, and force them to bring many different things together.

Lessons I’ve learned from observing other classes.

  1. Don’t treat your students as though they are lazy or stupid.
  2. A harsh word can completely ruin a semester, and force you to lose all credibility.
  3. If morale gets low, you better get creative, because low morale means low learning.
  4. If you find yourself ranting about your students more often that praising them, you probably need to reconsider your teaching strategies. And take a break.  Students aren’t actually that bad.
  5. Don’t treat your students as though they are lazy or stupid.

It’s an ongoing process, but I think things are progressing pretty well.  I hope to keeping experimenting to see what works best.

education

Strong Opinions, Lightly Held

December 14th, 2009

A few weeks ago, I listened to this great podcast episode from Hanselminutes with James Bach.  While the podcast is normally about programming topics, this particular episode was more about auto-didactic learning.  Near the end of the show, they talk about the concept of ‘Strong Opinions, Lightly Held.’

The idea behind this concept is that you have very strong opinions about something, but you’re not dedicated to it.  You can make a passionate defense of a topic, but when presented with contrary evidence, you simply switch over.  Imagine making a very strong argument and then going ‘Oh, you’re right. Nevermind.’

This is something I don’t think very many people understand, but as someone who’s philosophy is scientific in nature, I’m very familiar with it.  I’ve experienced this countless times where I’ve made what I think is a very good argument for something, then had someone completely destroy it with a simple counter argument.  At that point, I have no choice but to change my mind.  And that’s a good thing.  It means I’ve learned something new, and I’ve progressed in some way.  It’s something I strive for, and when I see it in others, it’s something that gains them immediate respect in my eyes.

Being ‘wrong’ about something has been unfairly stigmatized in our culture.  If you change your mind about something, many times you’re viewed as a ‘waffler,’ or someone who doesn’t know what they believe, or someone who lacks principles.  In reality, it’s just the opposite.  Changing your mind when faced with a better argument does not represent the lack of principles, but dedication to the pursuit of truth.  Is is the embodiment of the idea that truth is more important than the self and that any opinions, beliefs, and views one has must bend to reality, because to do anything else is delusion, by definition.

It doesn’t mean you won’t make mistakes, that you can’t be misled.  It’s easy to imagine a situation where you hear what you only perceive to be a better argument, and in reality, you’re missing some vital information that would clearly demonstrate its incorrectness.  The beauty of this philosophy of ‘strong opinions, lightly held,’ is not that it always leads directly to ‘truth,’ but that it’s self-correcting. If you take the wrong path at some point, it’s easily corrected once you do have the required information.  You never reach ‘absolute’ truth, but you do get closer to it with each iteration.

If there is a path towards wisdom, it surely must begin with the recognition of your own fallibility through self-examination, and this is exactly what is represented by ‘Strong Opinions, Lightly Held.’

education ,

Fact Checking the Alamo

May 26th, 2009

A New System of GovernmentFor part of my vacation this year, I visited my friend Tara, who lives in San Antonio.  It was a beautiful trip, and San Antonio was very nice.  Maybe I will write more about that later.  There was one quick thing I wanted to post about, however.  When I visited the Alamo, there was a short sentence that really jumped out at me.  There is a picture on the right.

The first sentence reads: “Republicanism, a new idea about government, became popular in the late 1700s.”

I realize this may be over pedantic, but I just couldn’t let this drop.  Republicanism was a new idea about government?  Perhaps the author of this short blurb should have read Plato.

That’s all for now.  I need to get back to catching up on email.

Philosophy, education , ,