This time around, we’ve got a post from Colum McAndrew. Based on a lot of what we’ve been hearing and reading, the topic of Colum’s post will definitely generate comment.
Is your curiosity sufficiently piqued? If so, come back tomorrow.

This time around, we’ve got a post from Colum McAndrew. Based on a lot of what we’ve been hearing and reading, the topic of Colum’s post will definitely generate comment.
Is your curiosity sufficiently piqued? If so, come back tomorrow.

This time ’round, our guest blogger will be Julio Vazquez. In his post, Julio looks at an area that many technical communicators neglect.
Intrigued? Then check this space tomorrow. You won’t be disappointed.

This time ’round, we have Mark Fidelman offering some insights into a subject that we don’t cover much in this space.
Drop by tomorrow to read Mark’s interesting and informative post.

Scott will be hosting a seminar titled “Getting Organized with Google Apps” at the Camaraderie coworking space in Toronto on September 23, 2010.
In this one-hour seminar, Scott will look at how to organize your work and life using Google Apps. More than just a walk through of how to use the software, this seminar will offer useful techniques you can get more organized and productive, in a simple way. You’ll learn how to integrate Google Apps into your workflow and lifestyle. Best of all, you can apply these techniques to any organization tool that you work with.
You can find more details about the seminar, and register for it, here.
The cost for attendees is $10 (Cdn.), payable via PayPal. The proceeds from this event will help sponsor the FLOSS Manuals book sprint to be held at Toronto Open Source Week on October 26 and 27, 2010.

This time around, our guest poster is Bill Kerschbaum. Bill takes a well-known technical communication analogy and reshapes it in a really interesting way with this must-read post.
Intrigued? Check this space tomorrow.

Keep an eye out for tomorrow’s guest post by Tristan Bishop. It’s somewhat different from the post (even the guest posts) that usually appear in this space. But it’s something every technical writer should read.