Skip to main content

The Purdue Online Writing Lab

The Online Writing Lab (OWL) at Purdue University (http://owl.english.purdue.edu/owl/) is one of the two websites I check when I have a writing related question. The other is the Tameri Guide, of course, since Susan and I tend to add content to Tameri based on our experiences writing and teaching. I am a bit envious of the great content on Purdue OWL, though. It is probably the best academic writing site on the Web.

Recently the OWL began adding slide shows, movies, and podcasts for students and teachers. The MLA and APA citation guides were already invaluable, but I've started to accept that students want content in digital form.

The podcasts' content focuses on rhetorical concepts. Because students struggle with ethos, pathos, logos, and kairos, any additional explanations are helpful. I'm for anything that helps students sort through the complicated textbook definitions of these concepts.

For a few years the OWL has been adding PowerPoint presentations on a range of writing topics. I'm not a fan of PowerPoint; slides are best used to introduce topics. Slides, by their nature, are superficial and should be accompanied by further reading and discussion. Still, the slides help students focus on key topics and concepts they should remember. The long list of available presentations is impressive and I do encourage teachers and students to browse the OWL library.

The OWL movies focus on visual rhetoric, but they too can be useful for writers. Unless we're discussing audiobooks, most of our words appear on pages or screens. Design affects the perceptions of texts, including how seriously a reader approaches the words. The OWL movies are a good starting point for discussions of visual rhetoric.

For the basics of academic writing, you won't find many resources equal to the OWL. Again, the website is: http://owl.english.purdue.edu/owl/

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.