Technically Challenged

I remember the instant hesitation I felt as I debated whether or not to take this course- Technical Writing. The first word of the title alone presented a challenge, even though it was associated with writing, my forte. Perhaps my lack of knowledge of what the course entailed (despite reading the description and learning outcome over and over) was what intimidated me the most. Whatever the case was, I had to take that leap because, honestly, I needed a second course to add to my schedule. So, here I am, a non-swimmer, in a body of water with no life jacket. Yet, my need to survive is in full gear and I am confident that I am going to make it out of this alive. Hey, work with me here. If Amanda Metz Bemer, a student in the the field of technical communication, did it, so can I. According to Bemer, Technical communication as a field has struggled over the years to define itself (kudos to me for trying to understand it). To add to that revelation, she quotes Jo Allen, who states that all definitions of technical communication thus far seem to focus on a "single aspect of technical writing." However, this is not something that she is willing to accept. In her determination to define this field, she suggests that professors and graduate students are in need of it. Personally, I am not in dire need of it, but I am curious and do sympathize with the frustrated individuals that are either in the field academically or professionally, or contemplating that route. Who would want to deal with having to explain a major or a job description with no real clue on how to? Perhaps technical communicators should generate a manual on "defining technical writing" and leave out the technical stuff for technically challenged people like myself, technically speaking. Bemer may just be the one to do it. I just hope by the end of this semester I leave this class realizing that I was never drowning- just simply holding my breath in a 3 ft. pool.