Journal 3

This week I found the readings to be enjoyable. I really need to stop confessing this, especially as a Writing major, but I am the worst at grammar. Although, the articles were not directly related to grammar, I feel that grammar is a huge part of designing, and constructing writing. I think what I enjoyed the most was the confirmation that writing is not easy, and that it is actually very difficult to make something an easy read for others. Even with my grammatical short-comings, I do think that I am a good writer, and it has been something that I have been told on occasion, I still feel like people do not understand what it actually takes to write something good.
I am at times guilty of the same judgment because there are things that one can read and immediately think that anyone could've written it. I always in the end come back to reality and acknowledge that in no way is writing ever "easy," even with the use of templates/style guides.
Although it may not cure all writing issues in companies, I do agree that style guides should be the first thing created. In fact my co-workers and I were discussing a similiar topic this morning. We are posting positions for departments and we want to ensure that all degree spellings are the same. This resulted in a discussion about the spelling of the BA and MA degrees. Is it Bachelors or Bachelor's and Masters or Master's? Granted both are acceptable, but to keep uniformity we needed to discuss which one to use.

Journal 2

I think that this weeks readings bring up a good point about Technical Communication/Writing. the first thing I want to talk about is the involved audience. I agree with Johnson in that the best way to know if something will be useful is to get the person who will be using it involved. It's like companies that have the pyramid organization where the people on top make the rules for those on the bottom without knowing what the 'bottom dewlers do.' Usually it results in unhappy employees and policies and procedures that don't work for the everyday transactions that occur. I think it works the same way for technical writers, designers, and audiences. I do feel that the users should be involved in the processes of course not every new technology can be collaboratorated on with hundreds of users, but even a few would be better than none. In the same sense technical writers are also possible users and are the ones that will eventually write the instructions and/or manual so I can agree that they should definitely be involved in the priliminaries and design phases. It just makes sense!
I can also agree that it is rediculous that technical writers are second to scientists, designers, etc. when it comes to new technology. The truth is they are all equally important and I think tech writers are really taken for granted. I must admit, I really never thought about who writes the manual, instructions, guidelines, how to's, etc. Now I see that most eveything we use and "build" or put together is based on a technical writer providing us that information. I supposed people figure that it can't be that hard to write the process of setting something up or putting something together because the idea is already laid out. But when the writer has to deal with edits and stipulations of someone who doesn't know the difference the results and difficulty show.
An example I found this week that just happened to go along with these articles was on target.com I was looking for a washer and dryer for the house I am trying to buy, and so I like to read reviews when I find a good price. I found a great price with a brand named Haier, but all the reviews were virtually the same. The manual for set-up was not user friendly, but the washer was a great buy.

Journal 1

In my readings almost immediately I noticed a trend. The biggest question or issue that Technical Communication/Technical Writing faces is that there is no accurate definition for what it is and/does. Depending on who you ask you may hear that there is no definition at all. To tell the truth I feel that technical writing really is all of the above (in terms of what the authors say about it). I understand why those in the profession want to have a formal definition to give when asked about what they do, but on the other hand I feel that it's not that necessary. I say that because in some respect I feel like my career kind of stands out like technical writing without a definition. I work in Human Resources, everyone has heard about it and every company has one, but really what is HR? I can't define it because it encompasses so much you can never cover it all.
I agree with the article that it has gotten so big it is almost impossible to accurately define it and not leave something out. It seems as though there is nothing that does not include technical writing. There are manuals/instructions for every thing you purchase I mean really what can you do that doesn't at some point require a technical writing. I think people think to technically about technical writing. Carolyn Miller's piece really shows that when the Faculty members practically went at it about putting technical writing as a humanities course. I found that so ridiculous that anyone would actually argue against it. Maybe I am weird, but I find technically writing to be humanistic; it may not be mushy, tear-jerking, or emotional, but it has to everything to do with people. Without technical writing little Bobby's dad couldn't build his swing set, and those same members on the committee probably would know how to post their grades or set-up their computers.
In my opinion technical writing is apart of our everyday lives.
For me it literally is and not only on a professional level at work when we implement new software and programs, but even at home. I love video games, RPG games are one of my favorite types. My boyfriend and I just bought an X-box 360 and got Fable II since we loved Fable I. Part of our gaming is purchasing the guide along with it and I am the navigator to tell my boyfriend what's next. Without technical writing I we would be missing so many things in the game and although it may sound comical to those reading, but it is completely true my boyfriend and I use that time as bonding and believe it or not it is so much fun and is what makes our relationship different and special for us. So for me technical writing doesn't need a definition to validate it, some things just are what they are.

Testing

I do not think I am much a blogger, I am so confused on how to view everyone else's blogs. I don't even know if anyone else posted so I figure if I am the only one that someone from class will read this and help, hopefully! LOL

Anywho, can someone also confirm what we are reading for tomorrow I know "Diary of a Tech Writer" is on the list, but I cannot find the paper that says which chapters in the book. Please help! :)

Sharifa