Monday, November 16, 2026

A benefit of kicking Canvas to the curb: A reconsideration of Alternative Grading

Regular readers may recall that, for this semester, I have kicked Canvas to the curb. I am using an edupunk collection of techniques to manage my courses. I would like to write more about the project, but for today, I want to focus on one particular and unexpected outcome.

I am using triage grading as usual in CS222 and parts of CS315. For the uninitiated, this is a model where an assignment (or part of an assignment) is graded on a four-point scale. Being essentially correct earns three points, being essentially incorrect earns one, and anything in between earns two, with zero points earned for unsubmitted work. These points can readily be added together and manipulated in order to determine composite grades such as final course grades. When my students access their grading record, they can see something like "2/3" or "3/3" for each assignment. However, it wasn't clear to me that everyone remembered or understood what these meant. That is, another way to read those grades would be "Try again" and "Good enough." It struck me that these descriptions are what a lot of Specifications Grading revolve around.

In triage grading, the numbers were always secondary anyway. The real meaning of a three-out-of-three is "essentially correct." The only reason it gets a number is to be able to do manipulations. Canvas makes it easy to enter the numbers and essentially impossible to do anything else: Canvas insists that grades are made up of points. But I don't have to follow that any more.

The spreadsheets I made to track student grades primarily store numbers, but they don't have to either. I could instead store rubrics directly and encode whatever transformation I want to spit out an A-F grade at the end. I don't have to abide by others' assumptions about how grades ought to work.

I am free to pursue specifications grading or other alternative grading techniques.

I have started working on Spring course plans in earnest, beginning with what may be the most complicated one: CS390 Game Studio Preproduction. My current draft embraces specifications grading wholeheartedly without my having to fuss over how I would represent the various assessments in Canvas. Radical that I am, now I am wondering how far I can take this inspiration.

Monday, November 2, 2026

Disabling comments

I have decided to disable comments on the blog. There's too much machine-generated noise. Every moderation request I get is a distraction. If you want to talk about my writings, feel free to reach out. I'm always glad to discuss these ideas, but the ROI on comment moderation is not good enough for my time.

Thursday, October 29, 2026

Only better is better

I found myself improvising a turn of phrase this semester that I quite like. I was trying to explain to my CS222 students that it doesn't matter how many user stories they complete but rather that they complete well the ones they attempt. That is,

More is not better. Only better is better.

This feels countercultural in formal education, where students sense that they get more points for more work. The popularity of AI-assisted programming actually gives me a good hook here to explain my meaning: generative AI can output more, so clearly that's not what we need students to be able to do. What we humans need to do is double down on understanding what "better" means.

I found this pithy phrase useful in my game programming class as well. As I wrote about earlier, I have provided students with a style guide that they are expected to follow. To enforce this, the grading scheme requires one to follow the style guide in order to earn higher than a D grade. In plain English, to violate the formal style guide is to do poor work. I fear many of my students haven't caught the meaning of this, and I suspect it is because of the institutional collapsing of "F" and "D," the systemic failure to account for successful but poor quality work.

Friday, September 25, 2026

Back Home Again in Indiana

On Wednesday, I stayed on campus later than usual so that I could attend a public presentation by Ben Vu, a successful and inspirational Ball State alumnus. It was a good opportunity for me to stop by the library to pick up some early sword and sorcery books that I learned about in my new copy of XNOO #1. As usual, I took the stairs.

The stairwells of Bracken Library are grey and stuffy. They are purely utilitarian, devoid of any attempt at beauty. Every time I take the stairs, I reflect on the many times I have encouraged my students to use those barren walls for guerilla artwork—who would even know?

Two books in hand, descending the stairs from the fourth floor, I was in high spirits, and so I began humming to myself. The acoustics astonished me. The slightest note rang grandly. The boxy stairwell is truly an echo chamber. A song spun up in my head, a somber ballad about a man singing alone in a stairwell. But I did not open my lips. I hummed my invented melody ever so softly, lest… lest what, exactly? I did not want to disturb any other evening stairwalker, even knowing there would be none. I think, mostly, I was afraid that someone would find me singing in the stairwell. My recent reading of Plutarch’s How to Resist Pressure came to mind, and I passed through the doors to the ground floor with a sincere sense of dysopia.

Bracken Library recently installed self-checkout kiosks, but I handed my books to the lone librarian. I see him there regularly, and he is quick to join in friendly smalltalk. He agreed that sometime one needs early 20th century fantasy stories to balance out “work” readings.

Walking back to the Robert Bell Building, I tried to remember the last time I encountered anyone making music on campus besides at School of Music events. The day I was attacked by an enraged Canada goose last year, I sought solace under a tree where an undergraduate was plucking on his acoustic guitar. He had acknowledged, without emotion, that this particular goose attacked everyone who approached the pedestrian bridge. From where he sat, he could simply watch it happen. The fact that he asked if I was okay makes me think he was a detached creative type and not a schadenfreude junkie.

Besides that, I cannot remember encountering anyone making music together outside of rehearsals and concerts. Everyone has headphones or earbuds now—everyone is consuming music all the time. When I ask my students to go 24 hours without a screen, one of the first things they comment upon is the lack of prerecorded music. I don't remember anyone mentioning filling the void with sounds of their own.

Just over a hundred years ago, my great grandfather—my namesake—helped found a social club specifically for singing. Well, probably for drinking and singing, but definitely for singing. Legend has it that they founded the club after showing up tipsy for the Christmas Midnight Mass choir and being reprimanded by the pastor.

The world needs more drinking and singing.

All roads lead me back to G. K. Chesterton, who is at once my inspiration and my foil. There are days when this melancholic can almost understand his joy. Chesterton’s The Flying Inn is a veritable paean to the collective delight from which song spontaneously springs. Let me sit with him and Belloc and enjoy laughter and red wine.

Walking to Wednesday night's presentation, I noticed that there are no pianos between Robert Bell and the Ball Communications Building. I suppose one should not expect there to be any pianos. But if there were a piano, it would mean something. It would be a sign. It would be an invitation.

“Back Home Again In Indiana” was written in 1917 by James Hanley and Ballard MacDonald. I have been playing it on piano out of The Real Book Volume II. The Real Book has no lyrics, so I looked for a lead sheet with lyrics online. The search is representative of the state of things: despite the song’s being in the public domain, there are no free folios, but many people sell you one. Undeterred, I found my mup user guide and made my own song sheet.

Yesterday morning, I carried my spare six-string to the office and printed out twenty copies of the song. I distributed the song sheets at the beginning of each of my three classes, informing the students that we were going to start with a sing-along. And then we sang. Most were sotto voce, but a few really got into it, not because they were talented singers but because they were having a good time.

I forgot to ask for the song sheets back after the second class, and several students kept their copies. Good. It was easy enough to print some more, and I used that opportunity to bring my guitar into the main office. I told the staff there that I was starting each class with a sing-along, and I asked if they would like to do one as well.

“Yes.” Kim said.

“Then here’s your song sheet,” I replied, handing one over.

“Wait, now?”

“Yes.”

The department chair came out of her office, and we sang the song once through. There was a new student employee in the office yesterday. She pointed out that this was not in the job description.

Only one student asked why we sang. I told her it was because culture is not someone else. We are the culture. We make the culture. We make it the way we want it to be. We are the dreamers of dreams.

Friday, September 4, 2026

Fixing the student progress report system

It turns out that the approach I described in an earlier post simply does not work. I didn’t mention in that post that I developed it with the help of an interaction with ChatGPT. Turns out, trusting ChatGPT led me astray: it is technically impossible to use Google Sheets and Apps Script in the way I thought I could. Mea culpa.

Today, I stood up a new solution. Now, each student gets a UUID which is sent as a custom parameter to my script, and this returns for them a view of their row of the grading sheet. This variation was also developed in concert with ChatGPT, but one major difference is that this one verifiably works. The AI interaction was helpful in quickly identifying how to use Apps Script to generate UUIds and read http parameters.

In this post, I am going to try to reconstruct the steps I followed to get all the pieces working. It assumes I already have a grading spreadsheet set up that has all the students’ university emails in it.

  1. Create a function in the Apps Script to generate a UUID. It looks like this: function UUID() { return Utilities.getUuid(); }
  2. In the sheet, call this function for each student to give each a UUID. Then, copy and paste those values back in as plain text values.
  3. Create another column to construct the URL from that UUID. For example, have the stub URL in a cell, then concatenate “&code=” with the UUID after it.
  4. Export the sheet in .xlsx.
  5. From Word, start a new document, then from the “Mailings” menu, start a new mail merge. Note that this cannot be done in Office online: it requires running Word locally.
  6. Use “Select Recipients” to link the Excel file as a data source.
  7. Type the message, using the “Insert Merge Field” tool to put the student’s URL in place. “Preview results” is a toggle button (surprise!) that can be used to check that it is merging as expected.
  8. Choose “Finish and Merge” to generate all the emails, which will not actually send yet.
  9. Open Outlook, which will step through and send each email.

Incidentally, this is my first blog post that I have written in Markdown and then turned into HTML with pandoc ( pandoc post.md -o post.html). It has worked great and is a much better writing experience for this kind of post.

Friday, July 31, 2026

Notes from Spring 2026 CS390 "Final Exam" meeting

Back in April, I mentioned that the "final exam" for my game preproduction class was primarily a discussion. Cleaning up my office, I found my voluminous notes from that meeting. The four questions I asked of the students were, in order, the following:

  1. What do you think is missing from your preproduction work?
  2. What is something you know now about preproduction that was unclear before?
  3. What advice would you give yourself or to someone starting preproduction?
  4. What questions do you have?
One of the major themes in my notes is that the students recognized, maybe only in retrospect, that they had lost sight of the players. They were building things they wanted to build but not conceptualizing the player experience. Curiously, a student pointed to the final presentation as the first time he recognized and understood the omission. One of the students made a clever suggestion: early in the semester, when experimenting with different constraints around ideation and prototyping, I should challenge the students to make something for someone else. 

Another theme was how challenging it was for them to understand and articulate design goals. After having struggled to maintain a vision and a direction, they came to understand why these are necessary, and all wished they had spent more time agreeing on such goals at the start of the project.

When it comes to the second question, the students came to much better understand the role of playtesting, what it means to answer questions with prototypes, the dangers of analysis paralysis, and the importance of planning in order to understand scope. 

These are my notes about the advice that they would give to new students. I am leaving out a few that were very specific to this group or repetitive. I don't know yet if I will share these verbatim with my next cohort, but I also didn't want to lose them.
  • Think of game design as gift-giving, not as tinkering
  • Fast prototypes to articulate ideas are good
  • Don't spend too long trying to solve a problem
  • Take prototyping and playtesting seriously—don't make something just to have it
  • Set deadlines, use a calendar
  • Write game ideas down
  • Take feedback and write it down
  • Prototype instead of just thinking it will be fun
  • Mess it up
  • Don't be afraid to fail
  • Learn your scope (explore, but know strengths) and know when to move on

Sunday, July 19, 2026

Some ways to get a McGuffin from the Goblin King

Cleaning my office this morning, I came across some design notes that struck me as too interesting to throw directly into the recycling bin. I don't quite remember the context, but I must have been thinking about Apocalypse World style "moves" (in-game action types) and generative storytelling. It's probably from when I first learned about Viv, which I still have yet to play with. The paper itself contains a list of the moves that will be included in the third edition of Apocalypse World, a few notes about what it would mean to randomize locations and their denizens, and then an exploration of the different ways one could get a McGuffin from a Goblin King. These are what I came up with as possible stories:

  • Find him, kill him, take it
  • Find him, convince him to give it to you
  • Find him, steal it, escape
  • Find someone else, convince them to steal it
  • Find him, threaten him, he attacks (jump to another case)
  • Find him, threaten him, he gives it
  • Find him, beat him up, demand he gives it, get it
  • Find him, offer something else in trade, trade for it
  • Find him, observe him for leverage, deploy leverage as part of demand, receive it
There are certainly more, and clearly, some of these weave into each other. For example, convincing someone else to do it for you still requires that that character end up having to go through some other matrix of options.

Reading these simple statements starts stories forming in my mind. Each is a seed that could grow into something compelling, but they could also turn into something rather dull. Paying someone else to go questing is economically efficient but narratively unfulfilling.

It stands in contrast to my current project, which involves writing a lot of interactive fiction. This current work requires me to be very careful about branching since each alternative increases production costs. I am playing with the idea that you are a particular character, and so I do not feel like I have to expose all possible options to the player--only those that are reasonable to the character's situation and demeanor. 

I do hope to get back to exploring the kinds of narrative systems analysis that the McGuffin Acquisition represents, but in the mean time, I am finding more traditional gamebook-style interactive fiction to be a rewarding creative experience.

Now I can recycle this paper and get back to cleaning.