<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	>

<channel>
	<title>teaching Archives - rweber.net</title>
	<atom:link href="https://www.rweber.net/tag/teaching/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.rweber.net/tag/teaching/</link>
	<description>trying to be a mile wide AND a mile deep</description>
	<lastBuildDate>Wed, 11 Oct 2017 23:41:37 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
<site xmlns="com-wordpress:feed-additions:1">37896774</site>	<item>
		<title>Talk Advice 2</title>
		<link>https://www.rweber.net/editorials/talk-advice-2/</link>
					<comments>https://www.rweber.net/editorials/talk-advice-2/#respond</comments>
		
		<dc:creator><![CDATA[Rebecca]]></dc:creator>
		<pubDate>Wed, 28 Nov 2012 13:00:31 +0000</pubDate>
				<category><![CDATA[Editorials]]></category>
		<category><![CDATA[communication]]></category>
		<category><![CDATA[teaching]]></category>
		<guid isPermaLink="false">http://www.rweber.net/?p=221</guid>

					<description><![CDATA[<p>Last week I wrote about talk content. It&#8217;s time for round two of talk advice: delivery. These points are largely aimed at technical talks given on projected slides, since that is the overwhelming majority of the talks I&#8217;ve attended in the past ten years. First, addressing slides or boardwork: Don&#8217;t put too much on a [&#8230;]</p>
<p>The post <a href="https://www.rweber.net/editorials/talk-advice-2/">Talk Advice 2</a> appeared first on <a href="https://www.rweber.net">rweber.net</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Last week I wrote about <a href="https://www.rweber.net/neither/academics/talk-advice-1/">talk content</a>.  It&#8217;s time for round two of talk advice: delivery.  These points are largely aimed at technical talks given on projected slides, since that is the overwhelming majority of the talks I&#8217;ve attended in the past ten years.</p>
<p>First, addressing slides or boardwork:</p>
<ul>
<li> Don&#8217;t put too much on a slide.</li>
<li> However, don&#8217;t put so little on each slide that you&#8217;ve moved on to the next before the audience has time to read it.</li>
<li> Feel free to only <b>say</b> some things.  In fact, if literally everything is written out the audience may wonder why they&#8217;re listening to you when it would be much faster to read the slides.  You need the key points, the technical definitions, and anything else the audience may want to re-read, as well as diagrams or pictures.  Think of your slides as the highlighted or boxed portions of a textbook.</li>
<li> It is helpful to repeat important information (especially definitions) on later slides, or at least verbally.</li>
<li> Turn down the contrast and brightness on your computer screen (both separately and together) to check readability if you&#8217;re using anything other than black and white; projectors often wash things out a bit.</li>
<li>In a chalkboard talk, write top to bottom, left to right, and respect the seams of the board as edges of paper &#8211; it is difficult to write across them neatly.  When going back for a second round, erase your previous writing thoroughly.</li>
<li> Make sure the type (or your handwriting) is large enough.</li>
<li> Use whitespace generously &#8211; avoid large blocks of solid text as much as possible.</li>
<li> Landscape orientation allows higher magnification since it matches the usual projection screen dimensions better than portrait.</li>
<li>Stand to the side of your slides or what you&#8217;ve just written.  It is continually surprising to me the number of people who stand in front of their writing until they have moved far enough past it in the talk that reading it would be a distraction to the audience instead of a help.</li>
<li> Proofread!  You might not catch everything, but you&#8217;ll catch the most egregious errors.  Putting the slides aside for a day will help your observational abilities &#8211; when you look at something repeatedly you often start seeing your memory of it rather than the actuality.</li>
</ul>
<p>Secondly, your speaking:</p>
<ul>
<li> Practice!  When you have given many talks you will need less practice, but when you are starting out, multiple sessions are desirable.</li>
<li>I have never attended a talk that was read aloud from a prepared paper that did not bore me to tears.  Use notes, but don&#8217;t read word for word.</li>
<li>Speak loudly but do not shout.  While whispering and mumbling are clearly not desirable, neither is yelling.  Note that you can yell without raising your voice, as well.  The audience will not understand more if you are strenuously emphatic; they will simply feel accosted.
<li> Note that while practicing your talk by yourself is good, it is inexact for timing.  Err on the side of &#8220;too short&#8221; (within reason, of course &#8211; prepare more than thirty minutes of material for an hour-long talk); between extra things you say and questions from the audience the length will most likely increase, and if not, well, no one minds ending early.</li>
</ul>
<p>The post <a href="https://www.rweber.net/editorials/talk-advice-2/">Talk Advice 2</a> appeared first on <a href="https://www.rweber.net">rweber.net</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.rweber.net/editorials/talk-advice-2/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">221</post-id>	</item>
		<item>
		<title>Talk Advice 1</title>
		<link>https://www.rweber.net/editorials/talk-advice-1/</link>
					<comments>https://www.rweber.net/editorials/talk-advice-1/#respond</comments>
		
		<dc:creator><![CDATA[Rebecca]]></dc:creator>
		<pubDate>Wed, 21 Nov 2012 13:00:30 +0000</pubDate>
				<category><![CDATA[Editorials]]></category>
		<category><![CDATA[communication]]></category>
		<category><![CDATA[teaching]]></category>
		<guid isPermaLink="false">http://www.rweber.net/?p=210</guid>

					<description><![CDATA[<p>I started compiling advice for conference and colloquium talks some time ago, writing notes to myself while attending talks, prompted by good and bad features of the talks I was listening to, as well as from my own experiences. This installation of advice is aimed at the content of the talk; next week I&#8217;ll have [&#8230;]</p>
<p>The post <a href="https://www.rweber.net/editorials/talk-advice-1/">Talk Advice 1</a> appeared first on <a href="https://www.rweber.net">rweber.net</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>I started compiling advice for conference and colloquium talks some time ago, writing notes to myself while attending talks, prompted by good and bad features of the talks I was listening to, as well as from my own experiences.  This installation of advice is aimed at the content of the talk; next week I&#8217;ll have one aimed at delivery.  Note that since I have primarily lived in the technical world, this is aimed at people giving technical talks.  The next installation will have more points that are applicable to talks in general.</p>
<p>The key to giving a good talk is to remember that <b>talks are about the audience, not you</b>.  If the audience comes away understanding your result and its significance, you win.  If the audience comes away confused, annoyed, or otherwise feeling that you&#8217;ve wasted their time, you lose.</p>
<p>I always tell students that <b>talks are an exercise in letting go</b>.  You must accept that you won&#8217;t be able to say everything you know.  There&#8217;s a time limit and a speed limit, and both need to be respected to keep the audience&#8217;s respect.  Pick a goal for your talk (understanding the statement, motivation, and significance of one specific result would be a typical one) and ruthlessly tear out anything that does not assist you in getting to that goal.  Omit proofs if you can and give high-level summaries or &#8220;proof by example&#8221; if you cannot; give only special cases of definitions and results if that&#8217;s all you need (but always label them as such).<sup>1</sup>  Less is more.</p>
<p>Your audience will be more forgiving of seeing several things they already know than of an unfamiliar idea being flashed before them with inadequate preparation.  Take into account the audience you are going to address, of course: a seminar in which everyone is at least a graduate student in your field requires less background than a colloquium talk wherein, although everyone is a mathematician, many will have seen your topic most recently in a class they took a decade or more past.  Within reason, it&#8217;s all right to be imprecise, as well.  I have seen many talks where the speaker said something along the lines of, &#8220;I&#8217;m lying to you now, but it&#8217;s morally correct.&#8221;<sup>2</sup>  Examples are helpful and getting bogged down in details is not; it will require more than a talk worth of information to truly understand the details of your work no matter what you do.</p>
<p>Give context for your work.  As with background, how much you have to say will depend on your audience.  The history of your work can be helpful in understanding how you came up with your proof, if it is not a standard technique (e.g., &#8220;we tried this and it didn&#8217;t work, so we looked into why&#8230;&#8221;).  Clarify your contribution but don&#8217;t obsess over it; while you certainly don&#8217;t want to appear to take credit for someone else&#8217;s major idea, you don&#8217;t have to itemize who worked out each specific detail.</p>
<p>Think carefully about organization.  The best order to explain things in a talk may be different from the best order for the full research paper.  Remind your audience of your goal periodically and repeat key definitions or lemmas if they are being used any time other than immediately after their original statement.  Don&#8217;t insult the intelligence of your audience, of course, but remember that most or all of them haven&#8217;t been working on this topic recently, unlike you, and can&#8217;t refer back to earlier material like they could in a paper.</p>
<p>The 3 Cs are to be clear, concise, and charming.  I have no advice for the last one, but I hope this post has been useful for the first two.</p>
<p><sup>1</sup> Of course in a topic-specific seminar, you may have been asked to explain a proof, in which case this rule is clearly changed.</p>
<p><sup>2</sup> Any mathematician will understand this phrase, but non-mathematicians might not.  &#8220;Lying&#8221; is used typically to mean &#8220;being somewhat imprecise,&#8221; and &#8220;morally correct&#8221; means &#8220;literally false, at least in some aspects, but gives good intuition.&#8221;</p>
<p>The post <a href="https://www.rweber.net/editorials/talk-advice-1/">Talk Advice 1</a> appeared first on <a href="https://www.rweber.net">rweber.net</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.rweber.net/editorials/talk-advice-1/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">210</post-id>	</item>
	</channel>
</rss>
