Skip to main content

Poet Posts...

I have several blogs, some public and some not-so-public. This blog is specifically for ramblings on "digital writing" and how we might use new technologies to improve the writing skills of students. My other blogs range from photos of my cats to updates on life in Minnesota so my friends can share in my adventures. In some ways, these are the same uses students have: vanity sites (who else cares about my cats?) and keeping in touch with friends. The question we need to ask is if using these technologies can improve writing in ways other tools might not. Or, are we merely entertaining students with new toys, deceiving ourselves into thinking what is more exciting must result in more learning.

I am a skeptic, having been a business owner, corporate executive, and college administrator. Technology might not only do little good, it might encourage bad habits and mistaken notions of what is acceptable when writing later in life.

My first required posts will be this weekend. I've never bothered with YouTube or online videos because video tends to hurt my eyes and cause literal physical discomfort. I have seen YouTube videos on television and wonder why people would seek out such things. Let us hope the video blogs I view are somewhat more appealing. Just seeing what is listed as "most popular" on YouTube and MySpace should scare any social critic.

I'm not sure asking students to frequent sites best known for videos of profane comedy and stupid stunts ending badly is wise. Maybe I can be convinced otherwise, but I am a skeptic.

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.