Good teaching guide: Difference between revisions

Line 143:

=== Fielding questions ===

Ask people to use the in-~~game Class (EVE Uni)~~ chat channel for questions. It will give you more control over the class and allow you to deal with questions when you want to do so.

Ask people to use the "class-questions" chat channel on Discord for questions. Having questions delivered textually will give you more control over the class and allow you to deal with questions when you want to do so. You can open the floor on Mumble for voice questions at the end of the class if you want.

* If you are going to defer a topic then let the class know.

* If you are going to defer a topic, then let the class know.

* When answering a question from the in-game channel, repeat the question in Mumble before answering it~~. Recordings will make more sense and there might be people listening only on Mumble~~.

* When answering a question from the in-game channel, repeat the question in Mumble before answering it, for anyone who hasn't seen the question.

* If you have a lot of similar questions, then take a short bit of time out to consolidate them into a short topics - "~~A lot of~~ people are asking questions relating to passive shield tanking so I'm going to take a bit of time out to cover that ~~as a topic~~" ~~- if appropriate~~.

* If you have a lot of similar questions, then you can take a short bit of time out to consolidate them into a short topics: "Many people are asking questions relating to passive shield tanking, so I'm going to take a bit of time out to cover that now".

* If someone asks a question that you are not sure how to answer, then don't answer definitively. You might think you know the answer, in which case let them know: "''Someone has asked how ~~moon mining~~ works - I know the rough details, but it is a bit beyond the scope of this course, so ~~if it is OK with you,~~ I'll leave that for a more detailed course on ~~POSes~~''".

* If someone asks a question that you are not sure how to answer, then don't answer definitively. You might think you know the answer, in which case let them know: "Someone has asked how X works. I know the rough details, but it is a bit beyond the scope of this course, so I'll leave that for a more detailed course on X".

** Don't be afraid to say that you don't know something! You're there to teach, not to impress everyone, and many topics in EVE are extremely dense and rich.

The important thing with questions is to deal with them when you want, without letting them disarrange your class structure.

@@ Line 143: / Line 143: @@
 === Fielding questions ===
-Ask people to use the in-game Class (EVE Uni) chat channel for questions. It will give you more control over the class and allow you to deal with questions when you want to do so.
+Ask people to use the "class-questions" chat channel on Discord for questions. Having questions delivered textually will give you more control over the class and allow you to deal with questions when you want to do so. You can open the floor on Mumble for voice questions at the end of the class if you want.
-* If you are going to defer a topic then let the class know.
+* If you are going to defer a topic, then let the class know.
-* When answering a question from the in-game channel, repeat the question in Mumble before answering it. Recordings will make more sense and there might be people listening only on Mumble.
+* When answering a question from the in-game channel, repeat the question in Mumble before answering it, for anyone who hasn't seen the question.
-* If you have a lot of similar questions, then take a short bit of time out to consolidate them into a short topics - "A lot of people are asking questions relating to passive shield tanking so I'm going to take a bit of time out to cover that as a topic" - if appropriate.
+* If you have a lot of similar questions, then you can take a short bit of time out to consolidate them into a short topics: "Many people are asking questions relating to passive shield tanking, so I'm going to take a bit of time out to cover that now".
-* If someone asks a question that you are not sure how to answer, then don't answer definitively. You might think you know the answer, in which case let them know: "''Someone has asked how moon mining works - I know the rough details, but it is a bit beyond the scope of this course, so if it is OK with you, I'll leave that for a more detailed course on POSes''".
+* If someone asks a question that you are not sure how to answer, then don't answer definitively. You might think you know the answer, in which case let them know: "Someone has asked how X works. I know the rough details, but it is a bit beyond the scope of this course, so I'll leave that for a more detailed course on X".
+** Don't be afraid to say that you don't know something! You're there to teach, not to impress everyone, and many topics in EVE are extremely dense and rich.
 The important thing with questions is to deal with them when you want, without letting them disarrange your class structure.