<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://vrl.cs.brown.edu/wiki/index.php?action=history&amp;feed=atom&amp;title=User%3AJadrian_Miles%2FThesis_proposal_feedback%2Fdhl_meeting_notes</id>
	<title>User:Jadrian Miles/Thesis proposal feedback/dhl meeting notes - Revision history</title>
	<link rel="self" type="application/atom+xml" href="http://vrl.cs.brown.edu/wiki/index.php?action=history&amp;feed=atom&amp;title=User%3AJadrian_Miles%2FThesis_proposal_feedback%2Fdhl_meeting_notes"/>
	<link rel="alternate" type="text/html" href="http://vrl.cs.brown.edu/wiki/index.php?title=User:Jadrian_Miles/Thesis_proposal_feedback/dhl_meeting_notes&amp;action=history"/>
	<updated>2026-04-21T07:59:51Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.1</generator>
	<entry>
		<id>http://vrl.cs.brown.edu/wiki/index.php?title=User:Jadrian_Miles/Thesis_proposal_feedback/dhl_meeting_notes&amp;diff=4591&amp;oldid=prev</id>
		<title>Jadrian Miles: New page: Don&#039;t come off as glib.  dhl suggests: # pause after every question so it&#039;s clear you&#039;re thinking and/or say their question back to them to make sure you&#039;ve got it right, and never cut peo...</title>
		<link rel="alternate" type="text/html" href="http://vrl.cs.brown.edu/wiki/index.php?title=User:Jadrian_Miles/Thesis_proposal_feedback/dhl_meeting_notes&amp;diff=4591&amp;oldid=prev"/>
		<updated>2010-10-12T18:56:56Z</updated>

		<summary type="html">&lt;p&gt;New page: Don&amp;#039;t come off as glib.  dhl suggests: # pause after every question so it&amp;#039;s clear you&amp;#039;re thinking and/or say their question back to them to make sure you&amp;#039;ve got it right, and never cut peo...&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Don&amp;#039;t come off as glib.  dhl suggests:&lt;br /&gt;
# pause after every question so it&amp;#039;s clear you&amp;#039;re thinking and/or say their question back to them to make sure you&amp;#039;ve got it right, and never cut people off;&lt;br /&gt;
# if a question isn&amp;#039;t clear, say you don&amp;#039;t understand and ask them to re-ask;&lt;br /&gt;
# end every answer with &amp;quot;did that answer your question?&amp;quot; or something similar, even (especially?) if your answer is just, &amp;quot;that&amp;#039;s a good point; I&amp;#039;ll think about it&amp;quot;;&lt;br /&gt;
# answer the question asked; don&amp;#039;t spiral off into a discussion of something else (like the clustering bit with Chad) &amp;#039;&amp;#039;unless&amp;#039;&amp;#039; it serves a point you&amp;#039;re about to make;&lt;br /&gt;
# remember that people just mention stuff you didn&amp;#039;t think of, not to suggest that you screwed up, but to bring it up.  Respond positively and don&amp;#039;t try to justify why you didn&amp;#039;t do it.  Trying to show engagement with the idea by talking about how it relates to what you already did can rob your commenter of a sense of ownership over their comment.  Reinforce their ownership.&lt;br /&gt;
&lt;br /&gt;
Clear up misunderstandings early.&lt;br /&gt;
&lt;br /&gt;
Don&amp;#039;t apologize in a talk.  If you forgot something, don&amp;#039;t mention it.&lt;br /&gt;
&lt;br /&gt;
Answering a single question in the middle of the talk isn&amp;#039;t the time for a conversation.  Defer to the questioner; just say they&amp;#039;re right.  Leave discussion for the closing Q&amp;amp;A.  Spike said &amp;quot;unambiguous&amp;quot; seemed weird, so just agree with him and show you mean it: edit in place or something.  A further discussion can wait until after the talk or a private meeting later.&lt;br /&gt;
&lt;br /&gt;
Balance the desire to answer questions completely with the desire to make sure the talk is over on time.  Ending your talk late &amp;#039;&amp;#039;pisses people off&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
Spike said to number the slides.  Helps some people, doesn&amp;#039;t bother most others.&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
Try video-recording your talk.  You&amp;#039;ll be surprised and might get a better feel for how you come across when answering questions.&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
Chad sez: most of the questions derived from misunderstandings.  Make input and output of every step clear.  Make your goal clear.  Make your terminology clear.  Context doesn&amp;#039;t matter as much to CSers as clear &amp;quot;problem statements&amp;quot; for each contribution.&lt;/div&gt;</summary>
		<author><name>Jadrian Miles</name></author>
	</entry>
</feed>