Skip to main content

Teaching Aspirations

When I consider what I hope to teach and research, I begin with the question how online collaborative tools shape the composition process. How does technology restrict or expand the choices available? Is composing enhanced or degraded for those with special needs or language limitations?

Because I am a creative writer, I view "team" compositions of interactive fiction with the same curiosity I have for non-fiction projects. Composition, in my mind, includes a mix of what we often label as creative and academic genres. What matters to me is the writing process, regardless of how we might categorize the product at a specific moment.

"Composition and rhetoric" are often perceived as limited to the study of academic genres. I cannot foresee myself being limited to genres I want to challenge and reshape. The "rhetoric of fiction" and "rhetoric of theatre/film" are topics I would hope to teach in the future, from a technological and collaborative perspective.

Certainly, I see value in traditional forms, though I hope to influence their evolution to exploit technology. A serious academic work is creative. I hope to extend ways to express that creativity using technology, drawing from methods employed in creative composition.

It is my sincere belief that students who struggle with academic genre norms might excel with alternative approaches. Collaborative, multimedia composition has been studied for years, but we still employ traditional forms in most of our classes. I hope to be an advocate for change, ideally a radical shift towards collaborative compositions across the curriculum.

Comments

Popular posts from this blog

MarsEdit and Blogging

MarsEdit (Photo credit: Wikipedia ) Mailing posts to blogs, a practice I adopted in 2005, allows a blogger like me to store copies of draft posts within email. If Blogger , WordPress, or the blogging platform of the moment crashes or for some other reason eats my posts, at least I have the original drafts of most entries. I find having such a nicely organized archive convenient — much easier than remembering to archive posts from Blogger or WordPress to my computer. With this post, I am testing MarsEdit from Red Sweater Software based on recent reviews, including an overview on 9to5Mac . Composing posts an email offers a fast way to prepare draft blogs, but the email does not always work well if you want to include basic formatting, images, and links to online resources. Submitting to Blogger via Apple Mail often produced complex HTML with unnecessary font and paragraph formatting styles. Problems with rich text led me to convert blog entries to plaintext in Apple Mail

Learning to Program

Late last night I installed the update to Apple's OS X programming tool suite, Xcode 4. This summer, in my "free" time I intend to work my way through my old copy of Teach Yourself C and the several Objective-C books I own. While I do play with various languages and tools, from AppleScript to PHP, I've never managed to master Objective-C — which is something I want to do. As I've written several times, knowing simple coding techniques is a practical skill and one that helps learn problem solving strategies. Even my use of AppleScript and Visual Basic for Applications (VBA) on a regular basis helps remind me to tackle problems in distinct steps, with clear objectives from step to step. There are many free programming tools that students should be encouraged to try. On OS X, the first two tools I suggest to non-technical students are Automator and AppleScript. These tools allow you to automate tasks on OS X, similar to the batch files of DOS or the macros of Wor

Learning to Code: Comments Count

I like comments in computer programming source code. I've never been the programmer to claim, "My code doesn't need comments." Maybe it is because I've always worked on so many projects that I need comments  to remind me what I was thinking when I entered the source code into the text editor. Most programmers end up in a similar situation. They look at a function and wonder, "Why did I do it this way?" Tangent : I also like comments in my "human" writing projects. One of the sad consequences of moving to digital media is that we might lose all the little marginalia authors and editors leave on manuscript drafts. That thought, the desire to preserve my notes, is worthy of its own blog post — so watch for a post on writing software and notes. Here are my rules for comments: Source code files should begin with identifying comments and an update log. Functions, subroutines, and blocks of code should have at least one descriptive comment.