Aug.29th,2006; HW#5; Job Application characteristics

For a job apllication to be accessible, the packet (basically, the job application, with a cover letter, and one's resume) needs to be clear --no "wishy-washy" language as well as stating what position one is applying for. A cover letter as well as the resume , and the application itself is to be mistake-free. The packet needs to have all the necessary information for the potential employer to call the prospective candidate back for further information. The use of specific examples of pertinent former job positiions gives the packet a degree of concreteness. There needs to be a specific order to each component of a job packet so that the reader(in this instance, a possible boss) isn't confused or worse--throws all of it out!! Saying this, one certainly needs to have the list of qualifications of the job position desired, very visible.
As for the resume within the job packet, it needs to have all of the same accessibility criteria. The useability of a resume, I feel is probably slightly more important than accessibility. The resume must have a straight-forward lay-out, with emphasis on one's skills, knowledge and/or experience. Attention-getting headings assist the reader in reaching the "jist"-those qualifications without having to sift through the "extra" stuff.
Relevancy is closely tied with useability, in that if the total packet doesn't have up-to-date qualifications and information for a position that the company needs to be filled, that job application packet will very likely be ignored and thrown in the well-known "circular" file (the trash bin).

Aug. 29,2006; HW#1; Reading Reflection



To start, I never realized or put much thought to how techical communication is everywhere, as well as its long history (see page4 of "Concise Guide to Technical Communication").
I also hadn't thought either of the numerous quality characteristics that are involved in producing technical documents (way to go IBM technical editors!)
In my future career, I can imagine myself writing/inputting a document that explains some vital component of a web-site I created, to someone who may be ignorant of the intricacies of Web design/development, with using the information from the textbook. I can craft a document that can be error-free; with all the perrtinent information; uses understandable language; has a logical sequence; and very likely contain graphics or charts to explain further what I had written (see page4-5 of "Concise Guide. . ." under accessibility).

Aug. 25; HW#1; Introduction

Hello everyone!
My name is Onita Jarman, I'm attending MCC to earn anA.A.S.degree in Web technology. I am what is termed as a "re-entry student"--meaning I've not been in academia for awhile; in my case about 12 years. Additionally, I'm older than the majority of students on campus.
My academic goals are to excell in every one of the required courses for my degree program as well as have abit of fun.
Professionally, after earning this degree of mine, I hope to, ultimately, do free-lance Web-site design/development.
What I want from this course, Tech. Writing, is become better at communicating with future business associates and future clients. At this point, I believe I am a very good writer--I have been writing in a journal for the past 20 years.
That is it, for now!