Netiquette

1. Be Clear
• The subject line or your email should match the purpose of the text.
2. Don't Send Right Away
• When you write an email, save it and read it later.
• Emotions can't be seen through a computer screen, so your tone may be misconstrewed.
3. Keep it Simple
• People won't read an email if it is full of long, bulky paragraphs.
• Use bolded font to highlight key points/things the reader should remember.
• Use numbered or bulleted lists for information. It's easy to read, brief, and to the point.
4. Research
• Know what you are talking about, and when using references, cite them not only for your own protection, but also so others can use that information.
5. Stay on Topic
• If an email has a million different talking points, audience might get confused.
6. Use Proper Grammar
• Don't use internet slang. "LMAO" and "WTF" have no place in a professional setting. 
• Stay formal.
7. Keep your Cool
• Sometimes email makes it easy to be angry and say angry things when someone has upset you or hasn't been doing their job.
• Because they aren't right in front of you, it might make it easier to have an angrier tone.
• Keep your head, because emails can easily be forwarded.
8. Network Safety
• Always make sure emails only include "need to know" information.
• Because you can never ensure complete network security, top secret information shouldn't be included in an email.

Presentation and Free Response

            First, the presentation was great.  I thoroughly enjoyed hearing about all the different publishing models, and how they have all changed.  Also, he was hilarious.  I was almost sure he would be boring since he works in the library, haha.  I really learned a lot of new things about publishing something, and the pros and cons of what it means to really get something out there.  I have a tremendous problem with someone saying that your work is no longer your work – and that you have to get permission from them to print your own writing out.  That just seems incredibly wrong. 

          Which then leads me into my point about the article - I really don’t care that things are becoming more and more available.  I don’t think it is ever fair for a company to say to a newspaper that because things are becoming free, they should be able to profit off of their writing, and hardly pay the newspaper to do all of the work.  The same thing goes for authors.  If you want someone to write something, they should be paid.  I would so much rather support a company that pays its authors, than get something for free when I know the company is basically ripping the authors off.  I’m a bit biased as an aspiring author, but I still find it incredibly insulting in any case.  We wouldn’t ask nurses to work for 30% of their original income because health care is starting to be free in other areas.  Wouldn’t you rather have a nurse that knows she is getting paid the wages she deserved? Or a nurse that knows that all the work she does is practically for nothing?

It seems like it should be a very clear answer.  Authors are people too, and it isn’t “Free” to ask someone to write something, pay them hardly anything, and then make millions of dollars because you are the one to sell it on your website for a reduced price. Very unfair, and I can’t believe that is the way things are going.

Code of Ethics: Delane Moehring, Free- LanceTechnical Writer

1.      I will always be on time, and come prepared to start the day’s work.

2.      I will always maintain a level of professionalism, in my conduct as well as my appearance.

a.       I am a big believer in being responsible for my actions, for my work, and being held accountable in the event of a mistake.

b.      I will always give credit to those to whom credit is due.  Plagiarism is something I take as a very serious offense, and any work contributed by others in my writing will be cited.

c.       I am very respectful, and will follow instructions promptly, as well as efficiently.

3.      Any contracts, legal documents, and grants that I am asked to write for a company will remain private between myself and the company.

4.      I will not compromise my moral integrity for any type of document, especially in terms of violating another person’s rights and/or safety.

Chapter 4 Precis

Delane  Moehring

English 305

DiPrince

3 September 2012

Chapter 4 Précis

            Markel, in Chapter 4 of Technical Communication, discusses how to write collaboratively in order to work on projects effectively with other students and/or coworkers.  Markel gives examples of the advantages and disadvantages of working together, how to conduct valuable meetings, and what tools to use to help promote good teamwork.  His purpose in writing and giving these tips is to help technical writers, or even students, work in teams on projects or in the work-place effectively. Given the examples and guidelines, it appears that Markel is speaking to an audience that includes either students studying in technical writing, or technical writers who might have issues working in teams and collaborating in the work-place.

Chapter 3 Precis

Delane  Moehring

English 305

DiPrince

3 September 2012

Chapter 3 Précis

            Markel, in Chapter 3 of Technical Communication, discusses how to write technical documents (i.e. schedules, budgets, etc.) using several different processes of planning, analyzing, researching, outlining and organizing, and drafting.  Markel supports these methods by showing examples of documents written by these guidelines, and gives written and photographic instructions on how to make your documents more efficient through different options on your computer.  His purpose in writing and giving these tips is to help technical writers write documents effectively, more precisely, and with more efficiency. Given the examples and guidelines, it appears that Markel is speaking to an audience that are either beginners in technical writing, or technical writers who are trying to improve their skills in writing important technical documents.