Thursday, November 4, 2010

Safe Fail

Regular readers will remember that in Spring 2010, I taught a Human-Computer Interaction class (CS345/545) in which students worked in teams to develop Android applications. The inspirational goal—stated at the start of the semester and mentioned many times during—was to release novel applications on the Android Market. Out of seven teams, none actually released their applications on the Market during the semester, and in fact, many did not exhibit core functionality by the end of the 15 weeks of development. One team did add some spit-and-polish over the Summer and has since published theirs: it's called Elemental: Periodic Table, and it has 1/2 star more than my own Connect the Dots. (I think there's a good reason for that, and it has to do with expectations management, but I'll write about it another day.)

There is a significant contrast between CS345/545 and the current CS315 course (game programming, a.k.a. 3:15 Studio). This has been kicking around the back of my head for a while, but I have not done any real rigorous reflection about it. However, this is all just set-up for the story, so let me carry on.

I was in the lab the other day with some of 3:15 Studio, and things were going well. I turned to one of my students who was also in CS345/545, and I mentioned that I wished that the Android development had been as productive. This particular fellow is a good student, but it's fair to say that his project tanked last Spring. His response to me was not one of regret or criticism, but rather, he observed that it was better to fail at a big team-based semester project last Spring than to fail at the Morgan's Raid project or his senior capstone.

What phenomenal wisdom! In my own idealistic and individual analysis, I had been thinking about the failure as being a problem that needed to be solved. This student recognized that the learning still happened. Specifically, it was learning from failure, which might be the only kind of learning that matters.

Wednesday, November 3, 2010

Students owning space


Let me tell you why this sign makes me happy.


A few weeks ago, we had a ScrumMasters Community of Practice meeting in 3:15 Studio (which consists of the students in my CS315 class). There are four teams within the studio, each with its own ScrumMaster. The goals of this CoP meeting were to facilitate the ScrumMastering process and identify any inter-team issues.


The student ScrumMasters mentioned that, especially towards the end of the sprint, the lab gets quite crowded. The University scheduled CS315 for 2–3PM MWF, and so this is the time that everyone in the studio is working on the project. About 1/4 work in the classroom where the course is official scheduled, and 3/4 move up to the lab, which is much more conducive to small-group work. At the CoP meeting, the students suggested putting up some signs claiming the priority is given to CS315 students at 2–3PM MWF. However, this is technically what some might call "unauthorized use of the lab as a teaching space," and so the students don't really have preference during this time slot, not in the letter of the law anyway. I recommended that the students come up with signs that convey what they want, and then work with the department chair to have them approved.


When I first brought up official signage with the department administration, they were not too keen on it, mostly because we don't really have an official lab usage policy. The machines are configured so that only our majors can sign on, but otherwise, there is no real regulation of the space. However, when I informed the administration that it was the students who wanted to put up signs—not me—they became more interested in the process.


One of the student ScrumMasters drafted a reasonable poster on Monday, and I gave him some feedback from my perspective as a faculty member. He made some edits and sent it to the chair, who made some further changes and then approved its posting. Today, the student posted the notice. Perhaps to him and the other students, it was a mundane occurence, but to me it was significant. It was a sign that the students took ownership of this collaborative work space, that they felt they are stakeholders in departmental resources, and that they can define how these resources are used for the betterment of their education.

Kudos to you, 3:15 Studio, for being exemplars of learning in the campus community!

Tuesday, November 2, 2010

A growing dissatisfaction with 222

There are plenty of things to keep me busy, but I find myself drawn mostly to the need to reflect on some recent activities in my CS222: Advanced Programming class. I have written a little about the course design previously, but as a refresher, it's a brand new course in the curriculum, designed as a bridge from the foundations courses to the project-oriented upper-division courses.

I have a growing dissatisfaction with the execution of CS222, and I think this is in stark contrast to my other course, CS315: Game Programming. 315 is based entirely on studio-based learning: it is project-oriented learning to the nth degree, with all 25 students collaborating with me and external stakeholders on a real project. Perhaps the best way for me to express the difference between these two courses is to show what I did in the last meetings of these two courses.

In CS315, where students are in their 10th week of the project:

  • Worked on research for 5-10 minutes while the students had their "daily" stand-up meetings.
  • Got new markers for the lab where many of the students work.
  • Found paper for the printer in the lab so that students could print up some signs on lab usage, which they proposed to the department chair as official statements.
  • Helped a student in the lab, who is in my other class, with his project and talked about D&D a little with him and some 315-ers.
  • Gave some tips on how to deal with in-game dialog box images and text, facilitating conversation between members of different teams.
  • Looked over a group's shoulders and recommended a refactoring to a monstrous method.

In CS222. where students are in the second week of a six-week project:
  • Talked for 5-10 minutes about the importance of voting, the history of public education and its role in forming an educated electorate, and the difference between indoctrinating patriotism and respecting freedom. (It is election day.)
  • Showed past and current examples of an MSF-style risk matrix and Scrum backlog, explaining that the teams may use either one--or something else--as long as they are deliberate in their decision and reflect on it, and they can write a reflection on it later. (5-10 minutes)
  • Gave a walkthrough of how I use Google's guava library. This took about 10-15 minutes, partially due to unexpected system problems with Eclipse, probably related to the distro change and multiple Eclipse installs I currently have on my netbook.
  • The remaining 35 minutes was used by teams to evaluate each others' physical prototypes. As teams evaluated each others' interface designs, I posted some links to the course Web site. Only one group asked me for feedback on their design, and then others came to ask about other things. The best of these was the question of whether I thought a specific project was even worth pursuing, and I explained (to the student's satisfaction) that it wasn't me they should ask, but their prospective users.
315 is a joy. It is by and large an amazing experience to watch students learn to work together and learn from each other in a wholly legitimate way, a sort of organized chaos.

In 222, by contrast, I keep finding myself talking much more than I want to. It's not usually until I'm done that I realize how long I have been talking. We can take the guava libraries as an example: when I first learned about them, I was floored, and I wished that someone had shown them to me ages ago. In my mind, it would have only taken someone's showing a minimal example for me to see why I should be using this in all my Java projects. Yet, when I showed the students what I do with it, I got very little excitement from them. Was it because they do not have the perspective I have to realize what a useful library it is, or was it a failure of my presentation? These two are hard for me to disassociate, but the fact remains that maybe the whole thing would have been better organized as a workshop than a lecture. This is not without its own complications, not the least of which is the amount of planning that's required for minimal payoff.

Since day one in 222, we've had assignments due twice a week, at each meeting. This idea was gleaned from the SIGCSE mailing list as a way of ensuring students are doing the reading and keeping up. I will be teaching the course next semester, and I need to re-evaluate this structure in light of the students' lack of programming prowess: I'm not sure they're seeing the forest for the trees on issues of design, since many still struggle with basic program structure. Be that as it may, right now, the students are working on a six week project, delivered in two three-week increments. I am continuing to have them read items from Effective Java, but now instead of relating them to old projects or other experiences, they are relating these to their current project. For example, they are currently reading about minimizing the scope of variables (Item 45), and I asked them to evaluate their current project--in its current state--in light of this design idea. It's too early to know if this is positively impacting student learning, but my fear is that I might be giving them too many diverse ideas for them to deeply learn from their project experience. As soon as a student sees the homework as busywork rather than a learning experience, it loses almost all value to the student.

Maybe writing this, then, has helped me to see the problem: some students are not seeing the tips in Effective Java as the brilliant ideas they are, and so the well-intentioned assignments become busywork instead of learning experiences, and so both the assignment and the project suffer, rather than the synergy I try to promote. If that's true, then it becomes a problem of motivation management, the perennial problem of education. I think that I will scheduled time in class, perhaps next Tuesday, in which to engage students in a discussion of this whole process. I get the feeling that many of them do not feel like they can give me an honest evaluation of the class in person, so I may have to find a way to get them brainstorming, maybe a SWOT analysis, and come up with communal ideas.

As always, no answers, but this blog is not a place for answers: it's a place to try to hunt down the questions, and the questions within questions. As always, I'm open to ideas from the community. My plan for now is to maximize the learning in the time we have left this semester (about four weeks), and then use Winter Break to do a more significant analysis of the structure, goals, and delivery of 222.

Tuesday, October 26, 2010

Future of Education Task Force

As you may have read in the Muncie Star Press, I am on the Future of Education task force here at Ball State University. Contrary to the headline, competition from online institutions is not the primary motivation for the task force. Rather, our mission—as articulated by the task force co-chair— is:
Students coming to Ball State now and in the future are more technologically inclined, how do we tap into their expectations and mindsets to create a more relevant and better learning community?
I suggested that this be edited into a more relevant form, to wit:

How do we create a learning community?
Be that as it may, we had a major meeting yesterday, running from 9am until 3pm. The meeting was expertly facilitated by task force member and Entrepreneurship Center director Michael Goldsby. I would like to share here some of the highlights from this meeting.

We began with a SWOT analysis. Michael referred to all of the strengths, weaknesses, opportunities, and threats explicitly as "facts," and he used continuous numbering over the facts. This strikes me as significant, since I would have naively numbered strengths differently from the weaknesses, but using continuous numbering—and even continuous pagination—emphasized the fact that the ideas are more important than their categories. Several times, a task force member would say a single word or phrase that is known on campus, such as "The Working Well Program." Michael challenged with the simple question, "Why?" That is, he raised the level of discourse by forcing us out of academically-comfortable buzzwords towards meaningful facts. (For example, "The Working Well Program promotes physical and mental health among faculty and staff," a strength of the institution.)

A critical part of effective SWOT, as with brainstorming in general, is supporting divergent thinking by postponing criticism. This can be challenging for any group, and we were no exception. At several points, we devolved into discussion over points rather than supporting the creative brainstorming process. The facilitator was not always able to pull us back out. I have to admit, there was one point where I challenged a fellow task force member on a cited weakness, and it was completely unproductive to the process. I guess it's OK, though, since I did it because of my circumstances and everyone else did it because of who they are.

One of the task force members is Michael O'Hara, whose opinions on higher education I greatly respect even though we don't completely agree. He has a propensity for expressing complex ideas using just the right words, perhaps an artifact of his being both an academic and an actor. During the SWOT analysis, he championed the perspective of higher education as a humanistic endeavor rather than a utilitarian one. This point—the conflict of utilitarianism and humanism in higher education—is a critical aspect of the current debates, and I hope to return to it in later writings.

Another theme of the SWOT was the "placeness" of Ball State University. It is important for us to leverage our brick-and-mortar nature, given that much of our competition is from purely digital institutions. Martha Hunt pointed out that sustainability plays well into this discussion, that having a physical place allows for serious and grounded academic discourse on respect for physical space. As a Computer Scientist, I tend to abstract space and work with intangibles, and so it was good to have a Landscape Architect to bring us down to a discussion of what space really means.

The most challenging and intellectual elements were contributed by Matthew Wilson, whose scholarship as a humanities-minded geographer is directly tied to both virtual and physical space. In my opinion, the most meaningful challenge of the whole SWOT analysis was Matt's call for post-disciplinary thinking. Like the utilitarian vs. humanistic dichotomy, the call for post-disciplinarity cuts to the heart of much of higher education's problems. When a fellow task force member asked for my thoughts on post-disciplinarity, I pointed out that we are in disciplines, but problems, by and large, are not.

After the divergent SWOT analysis, which generated 200 facts in about three hours, we moved to a convergent mode in which each task force member had to select at most five of the greatest importance. The highest vote-getters moved to the next round, which consisted of an articulation of challenge statements of the form,  "How might Ball State University...?" Similar to the divergent-then-convergent SWOT, we started with some 25 challenge statements, each selected three, and the highest vote-getters moved forward. The final step involved the creation of a "map" of challenge statements, connected to their antecendents. As one who is well-versed in graph theory, visual rhetoric, and graph drawing, I saw this last step as particularly subject to manipulation and misintepretation, since we assumed a planarity in the articulation of a wicked problem.

I have many notes on the SWOT analysis in my blue notebook, which could be attributed to the fact that it was in the morning and was done with free coffee on hand. Upon reflection, though, I did find the SWOT the most interesting step, and the rest logically followed. I am not completely convinced that I would not have come up with the same output without investing a full collaborative day into it, but that's not really the point: the point is that now the task force has a shared experience that forms a collectively-owned starting point for the prototyping process.

Speaking of which, prototyping is next. Task force members are being put into teams to iterate through prototypes on the Future of Education. I am eager to see who the task force chairs assemble into groups, though in any case, I plan on using some of my software development tools to assist, definitely user stories and possible risk matrices. Assuming time allows, I will share my prototypes here, for my continued exercise in reflective practice and to invite commentary from the community.

Tuesday, October 12, 2010

Screencasting in Mandriva

I spent too much time today making a short screencast in order to demonstrate a specific property of Eclipse and Java. I could not find any clear recommendations on what software to use on Mandriva, my preferred Linux distribution, at least not beyond what was given on Wikipedia's page comparing screencast software.

I ended up using recordMyDesktop with the qt frontend, both of which were in the standard Mandriva repositories. You can select an area of the screen to record via the main window, but there is also a tray icon. Initiating a recording from the tray icon seems to always grab the whole screen, regardless of what is selected.
Additionally, the selection only seems to work if you choose the box and then hit record on the main window. Stopping that recording and then clicking record a second time results in having a full-desktop recording, which is not what I wanted. These complications caused me to have to throw away three reasonable takes, because it was easier to recreate them then to figure out how to crop a whole video. (Although if someone knows how to do that on Mandriva, let me know.)

With an acceptable take--although I forgot one important point, but am not willing to try yet again--I uploaded the file to YouTube. RecordMyDeskop produces Ogg Theora video output with Ogg Vorbis audio, which I think is great as a supporter of open formats. YouTube happily accepted the upload, recognizing it as Theory+Vorbis, and did its magical processing. The end result, unfortunately, had completely garbled video, just some colored flecks on the screen, while the audio worked fine.

A little scouring of the Web, and I discovered a Devede, a Linux application for mastering DVDs that can also be used to convert to AVI video format. After installing the requisite codecs, I was able to convert the ogv into avi, and I uploaded that to YouTube. Somehow it got confused and thought I cancelled the upload, so I had to do this twice, but the final one stuck.

This worked for me, but if anyone knows of a simpler and more streamlined process, I'm open to ideas.

Angry Unicorns

As I sit in office hours with no students around, I will share with you, dear reader, a tale of higher education, motivation, and an angry unicorn.

My students in CS222 are working in pairs on a two-week project, a little RSS analyzer. This was the halfway point, and we used our meeting today for each team to give a status report. After giving my introduction, I sat down so that student teams could, at their pace and discretion, come up and give their status reports. The first team came up rather quickly and did a fine job. After they collected their peer evaluation forms and sat down, there was a delay while the rest of the students considered whether or not to go next. I started a doodle, which turned out into a nearly-complete rendition of Strong Bad:
As the second group of presenters finally came to the front, I informed the class that I was one leg away from completing a sketch of Strong Bad, and that I didn't know what would happen if I had completed Strong Bad, but I'm sure it wouldn't be good.

We spent the next 50 minutes or so hearing status reports, at which time there was another lull, although by my estimation, about 20% of the class had not yet presented. So I started sketching again...
Once complete, I informed the class that I had completed my angry unicorn, and so I assumed that no one else wanted credit for presenting today. This was the first time I made any statement about the presentations being "worth credit," although the students knew that I was jotting down evaluations using the same rubric as their peers, and that I would email these later.

Immediately upon mentioning credit, there was hubbub and three more groups got up to give status reports. One of the groups had very little done, but they gave a great honest report. Another "group" was missing half, but the sole attendee gave a great synopsis of the team's status.

Most likely, it was mention of credit that made these last few get up and present, but I like to think it was the threat of angry unicorns.

Friday, October 8, 2010

All my thoughts, or, three-in-one

This morning, I attended a meeting where one of the agenda items was for each attendee to take five minutes to share:
  • The present state of higher education
  • The various responses to this state
  • How these responses point to a new vision for higher education
  • Readings to support this
Turns out, we didn't do this part of the agenda.

I'd hate for my hastily scribbled notes from before 8AM this morning to be wasted, so for you, dear reader: all of my ideas.