Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Good teaching guide: Difference between revisions

From EVE University Wiki
Uryence (talk | contribs)
m Uryence moved page Teaching classes to Good teaching guide: Existing page title ambiguous and potentially confusable with '"Teaching classes at EVE University". New title (sentence case as per MoS) makes it clear that this page is about *pedagogy* not about the practicalities of teaching.
Replace dead link. Consolidate CSS.
 
(9 intermediate revisions by 5 users not shown)
Line 3: Line 3:


The core messages of this page can be summarised as follows:
The core messages of this page can be summarised as follows:
* Prepare for what you want to cover
* Prepare for what you want to cover
* Make the class your own
* Make the class your own
Line 11: Line 10:


== Preparation ==  
== Preparation ==  
Sensible preparation underpins good teaching. You don't need to spend hours scripting every part of your class down to the word—this would make your class inflexible—but you do need to make sure you have laid the groundwork for your teaching.
Sensible preparation underpins good teaching. You don't need to spend hours scripting every part of your class down to the word—this would make your class inflexible—but you do need to make sure you have laid the groundwork for your teaching.


Line 22: Line 20:


=== Class notes ===
=== Class notes ===
Have you ever tried presenting someone else's work? It's harder to give a presentation that you don't know well yourself. Preparing a presentation, or even simply reordering the points in a way that makes the most sense to you, leads to a presentation that flows better and feels more natural as you present it, and so it will feel more natural to your audience as they listen to it.
Have you ever tried presenting someone else's work? It's harder to give a presentation that you don't know well yourself. Preparing a presentation, or even simply reordering the points in a way that makes the most sense to you, leads to a presentation that flows better and feels more natural as you present it, and so it will feel more natural to your audience as they listen to it.


Line 36: Line 33:
As an example, here is a section of possible notes for a class on research and production:
As an example, here is a section of possible notes for a class on research and production:
<div style="margin:0;background-color:{{{color|#ccccee}}};border:1px solid {{{border|#8888aa}}};border-left-width:5px;font-style:italic;text-align:left;padding:1em 1em 1em 1em; overflow:hidden;color:{{{text|#000022}}}">
<div style="margin: 0; border: 1px solid #8888AA; border-left-width: 5px; padding: 1em; background-color: #CCCCEE; color: #000022; font-style: italic;">
'''''Research'''
'''''Research'''
* Three things you can do to a BPO
* Three things you can do to a BPO
Line 51: Line 48:
* Productivity research:
* Productivity research:
** reduces production time
** reduces production time
** ...</div>
** ...
</div>


There is nothing earth-shattering here, but notes such as these will help you remember to cover all the points, and gives a logical sequence to use. By preparing a few bullet-point items to cover, you can still speak fluently without simply reading your notes.  
There is nothing earth-shattering here, but notes such as these will help you remember to cover all the points, and gives a logical sequence to use. By preparing a few bullet-point items to cover, you can still speak fluently without simply reading your notes.  
Line 64: Line 62:


=== Additional details ===
=== Additional details ===
Depending on the class, there may be little need for additional information. However, most classes have related topics that you might not intend to cover, but that you might be asked about. Think through these related topics, and prepare some short notes. It will help you to manage the class and deal with questions, and will also make you look smart!
Depending on the class, there may be little need for additional information. However, most classes have related topics that you might not intend to cover, but that you might be asked about. Think through these related topics, and prepare some short notes. It will help you to manage the class and deal with questions, and will also make you look smart!


Line 72: Line 69:


=== Final preparations ===
=== Final preparations ===
In the final run-up to your class:
In the final run-up to your class:
* check that you have your notes to hand
* check that you have your notes to hand
* check that you have any slides you'll be using
* check that you have any slides you'll be using
Line 86: Line 81:


== Giving the class ==
== Giving the class ==
 
EVE University classes ''typically'' run with audio and slides or game streaming delivered in one of the [[Discord]] classrooms, and textual chat or questions in the relevant "class-questions" channel on Discord.
EVE University classes ''typically'' run with audio on the public [[Mumble]] server, any slides or game streaming delivered in one of the [[Discord]] classrooms, and textual chat or questions in the relevant "class-questions" channel on Discord.


The best classes (in EVE and in real life) are those that:
The best classes (in EVE and in real life) are those that:
Line 103: Line 97:
At the start of the class, spend a few minutes telling people about the class. You might like to cover:
At the start of the class, spend a few minutes telling people about the class. You might like to cover:
* A brief overview of what you will be covering
* A brief overview of what you will be covering
* How you intend to use the chat channel and Mumble
* How you intend to use the Discord voice and chat channel options
* Whether you want a volunteer to link items for you as you talk about them
* Whether you want a volunteer to link items for you as you talk about them
* How you intend to deal with questions
* How you intend to deal with questions
Line 112: Line 106:
Putting this together, an introduction for a production and research class might look something like:
Putting this together, an introduction for a production and research class might look something like:


<div style="margin:0;background-color:{{{color|#ccccee}}};border:1px solid {{{border|#8888aa}}};border-left-width:5px;font-style:italic;text-align:left;padding:1em 1em 1em 1em; overflow:hidden;color:{{{text|#000022}}}">
<div style="margin: 0; border: 1px solid #8888AA; border-left-width: 5px; padding: 1em; background-color: #CCCCEE; color: #000022; font-style: italic;">
Hi, I'm [Name]; thank you for attending my class on research and production!
Hi, I'm [Name]; thank you for attending my class on research and production!


Before we get started, a few logistical details.
Before we get started, a few logistical details.


OK, so I am going to be using Mumble to give the class. Please make sure you have push-to-talk set on Mumble, and keep Mumble quiet during the class. You can put any questions you might have as I go along into the "class-questions" channel on Discord; it helps them be more visible if you begin them with a capital "Q". I will be watching the channel and fielding questions. If you ask a question I am going to cover in a few minutes then please don't think I am ignoring you—I will get to it! Also, if topics come up that might need some time to discuss, I've got 20 minutes for questions and answers at the end, and we can cover larger topics then.
OK, so I am going to be using Discord to give the class. Please make sure you have push-to-talk set on Discord, and keep the voice channel quiet during the class. You can put any questions you might have as I go along into the imbedded chat channel on Discord; it helps them be more visible if you begin them with a capital "Q". I will be watching the channel and fielding questions. If you ask a question I am going to cover in a few minutes then please don't think I am ignoring you—I will get to it! Also, if topics come up that might need some time to discuss, I've got 20 minutes for questions and answers at the end, and we can cover larger topics then.


For the class, I am going to run through research first, looking at a blueprint in detail and then covering the various research you can do on one and the skills involved. For those who know a little about research already, I intend to cover Invention in detail at the end. After covering the research side of things, I'll go into production, the skills involved and cover a little bit on how to get into production for profit. I'll finally cover invention, which is the production of Tech 2 goods using invented Tech 2 blueprints.</div>
For the class, I am going to run through research first, looking at a blueprint in detail and then covering the various research you can do on one and the skills involved. For those who know a little about research already, I intend to cover Invention in detail at the end. After covering the research side of things, I'll go into production, the skills involved and cover a little bit on how to get into production for profit. I'll finally cover invention, which is the production of Tech 2 goods using invented Tech 2 blueprints.</div>
Line 129: Line 123:
; Draw on personal experience.
; Draw on personal experience.
: Anecdotes and examples from your own experience can really help points stick in students' minds. If you can underpin one of the ideas you're getting across by telling a brief story from your own gameplay, go for it. Stories of lucrative successes and impressive killmails are great, but don't be afraid to tell stories of failure too, especially if they're amusing: everyone appreciates a teacher who can see the funny side of their own past mistakes.
: Anecdotes and examples from your own experience can really help points stick in students' minds. If you can underpin one of the ideas you're getting across by telling a brief story from your own gameplay, go for it. Stories of lucrative successes and impressive killmails are great, but don't be afraid to tell stories of failure too, especially if they're amusing: everyone appreciates a teacher who can see the funny side of their own past mistakes.
; Summarize detail after delivering it.
: Many aspects of EVE contain dense details fascinating to the numerically-minded. Not all students will have a head for figures, though, so when you've delved into the guts of a complex quantitative topic, make sure you summarize its implications in plain language afterwards. In a class on fitting, for instance, it's ''nice'' if students leave knowing the exact percentage reductions involved in [[stacking penalties]], but it's ''crucial'' that they leave knowing that adding a fourth Gyrostabilizer to their shield [[Rupture]] fit probably isn't worth it. Often this wrapping-up summary after a point is a great moment to rephrase the point or explain it using a metaphor, to give students a second chance at understanding it.


; Always be clear when you touch on matters of opinion, rather than facts.  
; Always be clear when you touch on matters of opinion, rather than facts.  
Line 143: Line 140:


=== Fielding questions ===
=== 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 chat channel imbedded in the classroom channel on Discord for questions (see [[Attending_classes#Public_Discord]]). 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 Discord 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 verbally 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.
The important thing with questions is to deal with them when you want, without letting them disarrange your class structure.


=== Keeping control ===
=== Keeping control ===
Serious or malicious disruption is rare in EVE University classes, but you need to be able to keep control of the class, and occasionally channel the efforts of people who might want to help but are misdirecting their efforts.
Serious or malicious disruption is rare in EVE University classes, but you need to be able to keep control of the class, and occasionally channel the efforts of people who might want to help but are misdirecting their efforts.


Line 160: Line 157:
* anyone continually trying to answer questions "for you" in the class channel ("Could those of you responding to questions in the class channel please stop? I know you are trying to be helpful, but it's a distraction, and I intend to cover these points as I go along.")
* anyone continually trying to answer questions "for you" in the class channel ("Could those of you responding to questions in the class channel please stop? I know you are trying to be helpful, but it's a distraction, and I intend to cover these points as I go along.")
* anyone misbehaving in channel
* anyone misbehaving in channel
* anyone repeatedly speaking or keying up on Mumble because they do not have "Push to Talk" enabled correctly.
* anyone repeatedly speaking or keying up on Discord because they do not have "Push to Talk" enabled correctly (most users are required to have push to talk enabled by permissions - but not all!).
 
In the first instance, courteously ask them to stop. If they don't, ask a Teaching Officer or EVE University Manager/Director for assistance with this, if necessary. Always be polite! The moment you start raising your voice to someone, you've lost control. Stay polite, and your class will be on your side.


In the first instance, courteously ask them to stop. If they don't, then mute or kick them. Ask a Teaching Officer for assistance with this if necessary. Always be polite! The moment you start raising your voice to someone, you've lost control. Stay polite, and your class will be on your side.
"Backseat teaching" presents a slightly subtler and more complex problem: in some circumstances, experienced players might be unable to resist the temptation to chip in with corrections or expansions. Rare, brief corrections of minor mistakes offered in a generous spirit are not normally a problem (and occur in real-life educational settings: every teacher slips up occasionally). If someone is regularly keying up on Discord and taking the direction of the class away from your plan, though, you should gently ask them to stop.


"Backseat teaching" presents a slightly subtler and more complex problem: in some circumstances, experienced players might be unable to resist the temptation to chip in with corrections or expansions. Rare, brief corrections of minor mistakes offered in a generous spirit are not normally a problem (and occur in real-life educational settings: every teacher slips up occasionally). If someone is regularly keying up on Mumble and taking the direction of the class away from your plan, though, you should gently ask them to stop.


== After teaching ==
== After teaching ==
Immediately after teaching, you might well want to take a brief comfort break. Soon after teaching, though, do note down any ideas for improvement which you had during the class. These could be additional points that you have realized the class might need to cover, tweaks to its structure, or related topics about which you would now like to know more yourself.


Immediately after teaching, you might well want to take a brief comfort break. Soon after teaching, though, do note down any ideas for improvement which you had during the class. These could be additional points which you have realised the class might need to cover, or tweaks to its structure, or related topics about which you would now like to know more yourself.
They could also be methodological notes: were there things in your teaching which went badly or well? Reflect on what happened, why, and what you can do to make the teaching (even) better next time. The Teaching Department will gather the evaluation from students, and sum it up for you, passing on any useful feedback or tips that they can offer, within a few days.


They could also be methodological notes: were there things in your teaching which went badly or well? Reflect on what happened, why, and what you can do to make the teaching (even) better next time. The Teaching Department will gather the evaluation from students, and sum it up for you, passing on any useful feedback or tips that they can offer, within a few days.
After you've written your after-class report, go back to the original forum advert post, and change the [CLASS] tag to [COMPLETED].


Then pat yourself on the back for a job well done, and (perhaps) return to playing EVE!
Then pat yourself on the back for a job well done, and (perhaps) return to playing EVE!


== Other Resources ==
== Other resources ==
* Toastmasters International: http://ibmottawa.toastmastersclubs.org/Quick_Guide_To_Public_Speaking.html  (toastmastersclubs.org) focuses on public speaking, so this is a great resource for in-game and in-real-life presentations.
* Toastmasters International: [https://www.toastmasters.org/resources/public-speaking-tips Public Speaking Tips] https://ibmottawa.toastmastersclubs.org/Quick_Guide_To_Public_Speaking.html  (toastmastersclubs.org) focuses on public speaking, so this is a great resource for in-game and in-real-life presentations.
 
{{EVEUniversityNav}}
 


[[Category:Guides]]
[[Category:Guides]]
[[Category:Teaching Resources]]
[[Category:Teaching Resources]]