# 1 So many options

Communication is a major concern in any course. Web courses make this a little trickier by reducing the options for face-to-face discussion.

Options for communications in this course include:

# 2 General Rules for On-line Communications

## 2.1 Public and Private Communications

Choose a communications option that is appropriate to the nature of the discussion.

Some of the communications options that you have will open your discussion up to the entire class. Others will limit your discussion to the instructor or to your team on a group assignment.

Use email or office hours for those kinds of questions.

• Similarly, questions about your own grade on an assignment should be limited to a private communication with the instructor. In fact, if you were to try to ask such a question in the public Discussion area, ODU privacy policies would prohibit the instructor from replying.

• For group assignments, of course, you can consider opening up the conversation to include your team members. But you should not discuss specifics of solutions to group assignments with other teams.

On the other hand, questions about the course subject matter or purely clarification questions about an assignment may be useful subjects for the entire class. These are good subjects for the Discussions area.

The instructor may, if he feels it is appropriate, copy an e-mailed question to the Discussions area so that the answer becomes available to everyone.

## 2.2 Etiquette in Email and Other Written Communications

• Students posting in the Discussions area or sending email to the instructor or to classmates are expected to conform to the norms for civility and respect for ones’ classmates and instructors that are common to all on-campus speech and writing.

• Emotions are often hard to convey and easy to misunderstand in written text. Smileys and other emoticons can help (but don’t assume that attaching a :-) to an insult will make everything OK with the people reading your post.).

DON’T WRITE IN ALL CAPITALS or in all bold or, even worse, IN ALL BOLD CAPITALS. This is considered to be shouting, and most people don’t like to be shouted at, whether in real life or on-line.

• “Shooting the messenger” is seldom a good idea. In general, assume that people who take the time to reply to your posts are honestly trying to help. Getting mad at them and “flaming” back is counter-productive if you really want people to help you.

Replies to posts will often be short and to the point simply because the responder has limited time. Don’t mistake terseness for rudeness.

Many people who post questions and requests for help may have made very basic mistakes. If you omit the details of everything you thought of and checked before making your post, don’t be insulted if someone replies with a very basic suggestion or a link to something that you have already read.

In an ordinary conversation, no one appreciates the person who barges in and insists on changing the topic of discussion. And if two groups of people actually insist on trying to simultaneously carry on a discussion on two distinct topics within the same conversation, the result is usually confusing to everyone.

Whether posted in Discussions or sent via email, a question is the beginning of a dialog. A well-prepared question will get you an informative answer quickly. A poorly-prepared one may get you irrelevant answers or may require several rounds of back-and-forth dialog, delaying your eventual answer by many hours or even days.

So it’s in your own self-interest to ask your question in a way that gets you the answer you need as quickly as possible.

## 3.1 Identification

Who are you? : If you are sending me email, make sure your course login name or your real name appears somewhere in the message. I hate getting mail from partyAnimal@hotmail.com saying “Why did I get such a low grade on question 5?” when I have no idea who this person is!

What course is this? : Again, if you are sending me a question via email, please remember to state which course you are asking about. I teach multiple courses most semesters.

For email, please put the course number (CS350) in the subject line. I configure my email reader to flag such messages for priority handling, giving you less chance of being lost amid the daily flood of spam.

Use a clear and precise subject header.: In Discussions, your subject header helps people decide if your post is worth reading. It also helps people find prior discussions that may have been relevant to later posts.

In e-mail, the subject line shares much the same purpose. Empty and short subject lines are also more likely to get tossed by autoamtic spam filters.

## 3.2 You Have to Give Information to Get Information

When you ask a question, you usually want an appropriate answer that will let you get past whatever difficulty you are having. So that answer needs to be relevant to your particular difficulty and tailored to your understanding of the course material.

I’m not psychic.

If you send me an email consisting of nothing more than “I’m stuck on this assignment.”, there’s really no way I can give you the kind of answer you are hoping for. You need to tell me:

• What part of the assignment are you stuck on?

• What have you tried so far? (Be specific. If you’ve tried lots of things, tell me about your best attempt so far.)

• What happened when you tried it?

If you don’t tell me those things, I’m just going to have to ask for that information, delaying the process of getting you the answer you want.

If you have an issue with a webpage, \emphasis{tell me the URL}. If a link is broken, \emphasis{tell me the URL of the page containing the link} and describe the location of the link. Don’t just tell me “the link to assignment 2 is broken”. I probably have a dozen different links to that assignment in different pages.

## 3.3 Thou Shalt Not Paraphrase

There’s nothing more frustrating than getting a question like

“When I try to compile my solution to the first assignment, I get an error message. What’s wrong?”

Grrr. What was the (exact) text of the error message? Was this on a Linux or Windows machine? What compiler were you using? What compiler options did you set? What did the code look like that was flagged by the message?

No, I’m not kidding. I get messages like this all the time. And it wastes my time as a question answerer to have to prompt for all the necessary information. It also means a significant delay to the student in getting an answer, because we have to go through multiple exchanges of messages before I even understand the question.

The single most important thing you can do to speed answers to your questions is to be specific. I’m not psychic. I can only respond to the information you provide to me.

• Never, ever paraphrase an error message (“I got a message that said something about a bad type.”)
• Never, ever paraphrase a command that you typed in that gave unexpected results (“I tried lots of different compilation options but none of them worked.”, or, my personal favorite, “I tried everything.”)
• Never, ever paraphrase your source code (“I tried adding a loop, but it didn’t help.”)
• Never, ever paraphrase your test data (“My program works perfectly when I run it.”)

All of the above are real quotes. And they are not at all rare.

The problem with all of these is that they omit the details that would let me diagnose the problem.

## 3.4 “Copy and Paste” is Your Friend!

And it’s not all that hard to provide those details. Error messages can be copied and pasted into your message. The commands you typed and the responses you received can be copied-and-pasted from your ssh/xterm session into your message. Your source code can be copied-and-pasted or attached to the message.

Note that this information is almost always plain text. Unless you really need to show me graphics, please don’t send me screen shots. They are often hard to read and often do not allow me to make the fine distinctions I need to tell what is going on. Keep in mind that raster graphics formats (gif, jpg, png, etc.) often look very different when rendered on screens with different resolutions.