Problem Solving Emails

It always amazes me how much class discussion can be generated with a simple activity, especially when the activity is grounded in the experience of students. Take this one, from Graves and Graves’ A Strategic Guide to Technical Communication: 

In-Class Exercise 7.3

You have to miss class to attend the funeral of an extended family member, but you have an assignment due at the beginning of that class. Write an email message to your instructor using the information in the previous section and the organization pattern outlined in Figure 7.3 to help you develop and structure your communication. Remember, you need to both identify and solve the problem that your upcoming absence will create.

The organizational pattern for problem solving emails that Graves and Graves provides is as follows:

Figure 7.3

1) Identify and describe the problem.

2) Give whatever background is necessary.

3) Describe options for solving the problem.

4) Recommend a solution and offer assistance to solve the problem.

I believe the reason that this assignment generates so much discussion in the classroom is that it is a very real and relatable situation, but I also think it presents an important intellectual challenge for students because it asks them to think, in a very concrete way, from the reader’s perspective. Students have to think of the problem from the instructor’s perspective. The student has to miss class and will not be able to turn in an assignment and will also miss the work done in the class that day. The necessary background is not about the student’s life, it’s about the work missed, how it is articulated on the syllabus. It also give the students the ability, in presenting solutions to the problem, a chance to articulate their understanding of the values of the course.

 

Cover Letters

I’m on a really large search committee with professors from both the Arts and the Sciences, and I’ve been surprised by the number of people in the Sciences who do not read cover letters, who only look at the CV portion of job application packets.

My students in technical writing mentioned that some firms hiring interns explicitly ask students not to include cover letters with their resumes.

I argued in class that even if an employer does not want a cover letter, writing one is a good idea because doing so will help you develop stories and examples that you could use in an interview session, but now I’m really curious what this potential trend means.

 

 

 

 

 

 

 

 

Teaching Technical Writing By The Book

I am teaching technical writing “by the book” for the first time in many years. That is to say I’ve taught technical writing a few times in the last few year, but this is the first time in a while that I’ve used a book. This semester, I’m using Heather Graves and Roger Graves’s Strategic Guide to Technical Communication (2nd Edition). 

I have to admit that I’m departing from my usual textbook-less approach because I am finding the business of being a departmental chair more time consuming than I’d like, and I’m hoping that the textbook provides structures that I’m currently not able to provide.  I want to write about some of the experiments I’ve tried in technical writing, but I thought I’d do so through the lens of comparison with this semester.

(The last time I taught technical writing, for example, I centered my class on making robots, and there isn’t a textbook that let me do that, but I will have to tell you more about that later…)

 

Teaching Revision with Manuscripts

Deep Down in the Classroom

By Jennifer Daly

Synthesis of an Idea:

During this summer’s National Endowment for the Humanities two-week seminar “Transcendentalism and Reform in the Age of Emerson, Thoreau, and Fuller” we would get together for discussion forums on everything from our own writing to pedagogical practices to activism inside and outside the classroom. One evening, a professor had mentioned the Digital Thoreau Project as a way to show the students the synthesis of Walden and to track the very deliberate changes Henry David Thoreau made in each of the manuscripts.  After much thinking, I had the thought that this could be done with almost any writer—as long as there was a manuscript. I decided that I would utilize manuscripts to open a conversation about process and revision with First Year Writing students this year and see if it was accessible to them.  There was a chance that they a) wouldn’t care, or…

View original post 1,316 more words

Assignment: Creating (and Coding) a Professional Website

(Note: If you have stumbled on this page by accident, this is an assignment I’ve given my English 5593 class. I’m posting it here because some colleagues are interested in seeing the assignment. –rb).

By April 14th, you will have created a professional website and an “off the grid” replication of that website, which will be built from the ground up and which will replicate as many of the features of your professional website as you are able to create.

The Professional Website:

Using WordPress, Weebly, or another free site, create a digital portfolio that allows future employers to find out who you are and what you do. At minimum, this site should have an “about me” page, a CV, and a description of working projects.

Here are a few examples of Professional Websites:

http://timorich.net/

http://ceball.com/

http://bonnielenorekyburz.com/

Process Material for the LRO:

  • include any challenges you encountered when creating your professional site, as well as a description of how you met those challenges
  • include a description of the ethos you are trying to project and how you believe this site projects that ethos
  • include a description from someone else of your site’s ethos. Is there a difference between your perception and the perception of the outside observer? What do you make of these differences?

The Replication

Create a multiple page “website” (turned in on a jumpdrive, a CD, or hung up on the web somewhere) which has working links (internal and external) and CSS applied.

Process Materials for the Replication:

  • keep a good record of roadblocks you experienced, how you got around them, and how you helped others
  • reflect on the process overall and what each (the WordPress and the ground up) taught you about online style, editing, and persuasion

 

Assumptions:

This assignment has been written to meet the experience level of the majority of the class, who has little to no experience coding. We are assuming, then, that many of us are going to fail to fully replicate our professional websites. Unlike most assignments, then, failure is part of the point. What has the attempt to replicate something already on the web taught you about coding? What has it taught you about writing for the web? By keeping an accurate record of our thoughts along the way, you will be given a clearer sense of when to allow digital platforms to do coding work for you, when you should do the work yourself, and when you can and should copy code (giving proper credit to the original coders, of course.)

If you are in the small minority of people in this class who has experience coding, remember that in order to have something meaningful to write about for your LRO, you will need to push the boundaries of your experiments. What things have you not tried in your coding experience yet? What happened when you tried to apply those experiments to the replicated professional page?

Exercises Related to Editing Project 1

  1. Using the basic terminology from Chapter 1 of Castro and Hyslop, see how many of the “Webpage Building Blocks” you can identify on the homepage of the professional website you created in WordPress, etc. To do so, you will need to look at the coding underneath your page by “viewing its source.” Annotate, in some way, the code of the site, labeling what makes up the “head” and “body” sections, what specifically is part of the “markup,” what specifically is a link to other content, and what specifically is textual content on the page. Don’t stress about getting this right (at this point, a great deal of this is going to look like goobledygook). The goal here is simply to see what you are able to identify and what you are not. Feel free to compare notes and ask others in the class.  (2/01/15)
  2. Use Chapters 2 & 3 of Castro to “reverse engineer” your WordPress site. Start with the simple text of your site, then see if you can add headings, links, headers, and footers. (2/10/15). The same rules about stress from above apply. Our goal is to engage the process and keep a log of what happens throughout.
  3. Use Chapter 4 of Castro to continue this process. Today, you might experiment with isolating a line of code from your WordPress site (or from somewhere else) and cutting and pasting it into your own site. What happened when you did that? What does the process teach you?  (2/12/15)
  4. Use Chapters 5 & 6 to continue this process. As some of the code becomes more complicated, you might utilize some of the ready made work at htmlcssvqs.com. (2/17/2015)
  5. Use the material about CSS to create a style sheet you apply to the HTML pages you have created. You might eventually experiment with CSS Zen Garden, in order to give your website different looks. (First mentioned 2/26/15)