
<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Troubleshooting.</title>
	<atom:link href="http://www.helenemartin.com/2009-08-troubleshooting/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.helenemartin.com/2009-08-troubleshooting/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=troubleshooting</link>
	<description>Education, computer science, sewing...</description>
	<lastBuildDate>Sat, 04 Sep 2010 15:36:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Aliya Walji</title>
		<link>http://www.helenemartin.com/2009-08-troubleshooting/comment-page-1/#comment-46</link>
		<dc:creator>Aliya Walji</dc:creator>
		<pubDate>Tue, 08 Sep 2009 09:52:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.helenemartin.com/?p=245#comment-46</guid>
		<description>Ok this is clearly not as thoughtful a reply as the others but still, somewhat on topic.  I&#039;m thinking of printing this and giving it to my boss:

http://xkcd.com/627/</description>
		<content:encoded><![CDATA[<p>Ok this is clearly not as thoughtful a reply as the others but still, somewhat on topic.  I&#8217;m thinking of printing this and giving it to my boss:</p>
<p><a href="http://xkcd.com/627/" rel="nofollow">http://xkcd.com/627/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hélène Martin</title>
		<link>http://www.helenemartin.com/2009-08-troubleshooting/comment-page-1/#comment-42</link>
		<dc:creator>Hélène Martin</dc:creator>
		<pubDate>Tue, 01 Sep 2009 01:44:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.helenemartin.com/?p=245#comment-42</guid>
		<description>Hi, Jim!  That&#039;s a really good analogy you make... especially given my background.  You are good, sir!  Here&#039;s the thing, I actually get a lot more annoyed when people ask me how many languages I speak when I say I have a linguistics degree than when I&#039;m asked to fix a computer because I have a CS degree.  In a way, I feel like the latter is ok -- I should understand my field&#039;s tools.  The former is kind of like asking a marine biologist how many lions he&#039;s dissected because, well, he&#039;s a scientist who works with animals.  Or something.  Linguists generally study how either a particular language works or what abstract principles govern the process of language.  As Jim knows. 

Part of the reason I&#039;m ok with being asked to fix a computer is exactly what Sylvia brings up.  I should be able to figure it out because I&#039;m a problem solver.  I don&#039;t understand these other folks who find it beneath them to care or know: if they can&#039;t figure it out, then they&#039;re just not very good at solving problems, which is Not Good!</description>
		<content:encoded><![CDATA[<p>Hi, Jim!  That&#8217;s a really good analogy you make&#8230; especially given my background.  You are good, sir!  Here&#8217;s the thing, I actually get a lot more annoyed when people ask me how many languages I speak when I say I have a linguistics degree than when I&#8217;m asked to fix a computer because I have a CS degree.  In a way, I feel like the latter is ok &#8212; I should understand my field&#8217;s tools.  The former is kind of like asking a marine biologist how many lions he&#8217;s dissected because, well, he&#8217;s a scientist who works with animals.  Or something.  Linguists generally study how either a particular language works or what abstract principles govern the process of language.  As Jim knows. </p>
<p>Part of the reason I&#8217;m ok with being asked to fix a computer is exactly what Sylvia brings up.  I should be able to figure it out because I&#8217;m a problem solver.  I don&#8217;t understand these other folks who find it beneath them to care or know: if they can&#8217;t figure it out, then they&#8217;re just not very good at solving problems, which is Not Good!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sylvia</title>
		<link>http://www.helenemartin.com/2009-08-troubleshooting/comment-page-1/#comment-40</link>
		<dc:creator>Sylvia</dc:creator>
		<pubDate>Wed, 19 Aug 2009 00:47:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.helenemartin.com/?p=245#comment-40</guid>
		<description>This is an interesting topic you bring up.

And I totally agree with Craig about the asking the right question. I also think that the reason computer scientists are better at doing that than other people is that we are around computers all the time and have experience using them and sometimes breaking them (whether intentionally or by accident). Over time we learn to not be afraid of the computer and learn how various things interact with each other (even if only on a surface level, such as key settings being different for various applications). When it comes to solving the problem we have ways to narrow things down and maybe a few guesses as to what&#039;s wrong. And if we need to we know how to ask Google too. Other people always seem to think that the problem is something really complicated and even if they searched they either wouldn&#039;t get the right query or wouldn&#039;t understand the solutions that came up. So they don&#039;t bother. They ask their tech-savvy friends instead.

I don&#039;t think there&#039;s really a way to teach troubleshooting. People just have to know that often it&#039;s not that complicated and they can do it themselves if they tried.

Perhaps if you had a list of common problems and how to troubleshoot them, it would give students a starting point from where to go or perhaps ideas as to what could have went wrong. Show them that it&#039;s not that complicated.

(And here are some pictures for relevant amusement:
&lt;a href=&quot;http://wwwdelivery.superstock.com/WI/223/1538/PreviewComp/SuperStock_1538R-7022.jpg&quot; rel=&quot;nofollow&quot;&gt; L&#039;problem&lt;/a&gt; 
&lt;a href=&quot;http://pro.corbis.com/images/42-17678879.jpg?size=572&amp;uid={C4DBB0F0-E4E2-4ED9-99B7-617D2EDF272B}&quot; rel=&quot;nofollow&quot;&gt;Building experience!&lt;/a&gt; 
&lt;a&gt;But really, computers are nice.&lt;/a&gt; )</description>
		<content:encoded><![CDATA[<p>This is an interesting topic you bring up.</p>
<p>And I totally agree with Craig about the asking the right question. I also think that the reason computer scientists are better at doing that than other people is that we are around computers all the time and have experience using them and sometimes breaking them (whether intentionally or by accident). Over time we learn to not be afraid of the computer and learn how various things interact with each other (even if only on a surface level, such as key settings being different for various applications). When it comes to solving the problem we have ways to narrow things down and maybe a few guesses as to what&#8217;s wrong. And if we need to we know how to ask Google too. Other people always seem to think that the problem is something really complicated and even if they searched they either wouldn&#8217;t get the right query or wouldn&#8217;t understand the solutions that came up. So they don&#8217;t bother. They ask their tech-savvy friends instead.</p>
<p>I don&#8217;t think there&#8217;s really a way to teach troubleshooting. People just have to know that often it&#8217;s not that complicated and they can do it themselves if they tried.</p>
<p>Perhaps if you had a list of common problems and how to troubleshoot them, it would give students a starting point from where to go or perhaps ideas as to what could have went wrong. Show them that it&#8217;s not that complicated.</p>
<p>(And here are some pictures for relevant amusement:<br />
<a href="http://wwwdelivery.superstock.com/WI/223/1538/PreviewComp/SuperStock_1538R-7022.jpg" rel="nofollow"> L&#8217;problem</a><br />
<a href="http://pro.corbis.com/images/42-17678879.jpg?size=572&amp;uid={C4DBB0F0-E4E2-4ED9-99B7-617D2EDF272B}" rel="nofollow">Building experience!</a><br />
<a>But really, computers are nice.</a> )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Gold</title>
		<link>http://www.helenemartin.com/2009-08-troubleshooting/comment-page-1/#comment-39</link>
		<dc:creator>Jim Gold</dc:creator>
		<pubDate>Tue, 18 Aug 2009 23:08:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.helenemartin.com/?p=245#comment-39</guid>
		<description>Your introduction reminded me of the first class session of my Linguistics 101 class a few years ago.  The professor asked us to guess what the most common question he received when he told a stranger that he was a linguist.  There were a couple odd guesses from my classmates, but I guessed it was &quot;How many languages do you know?&quot; and I was right.  As a polyglot yourself, it might not be a terribly maladroit question, but my professor only knew English fluently (though he admitted that he knew a little Japanese), so it was a consistently awkward way of starting a conversation at a social event.

As for troubleshooting, in particular, I think your example (along with any number of other examples you or I could produce) just go to show that there are significant differences between people in their willingness and ability to analyze problems (technical or otherwise), and even to be able explain whatever problems they have (i.e. constructing the right Google query to get the intended search results).  It&#039;s kinda fascinating how, I imagine, most people out there manage to get through life without being able to answer a large portion of the questions that may go through their mind every day, assuming those questions even occur to them in the first place.

Hi!  :D</description>
		<content:encoded><![CDATA[<p>Your introduction reminded me of the first class session of my Linguistics 101 class a few years ago.  The professor asked us to guess what the most common question he received when he told a stranger that he was a linguist.  There were a couple odd guesses from my classmates, but I guessed it was &#8220;How many languages do you know?&#8221; and I was right.  As a polyglot yourself, it might not be a terribly maladroit question, but my professor only knew English fluently (though he admitted that he knew a little Japanese), so it was a consistently awkward way of starting a conversation at a social event.</p>
<p>As for troubleshooting, in particular, I think your example (along with any number of other examples you or I could produce) just go to show that there are significant differences between people in their willingness and ability to analyze problems (technical or otherwise), and even to be able explain whatever problems they have (i.e. constructing the right Google query to get the intended search results).  It&#8217;s kinda fascinating how, I imagine, most people out there manage to get through life without being able to answer a large portion of the questions that may go through their mind every day, assuming those questions even occur to them in the first place.</p>
<p>Hi!  <img src='http://www.helenemartin.com/wordpress/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hélène Martin</title>
		<link>http://www.helenemartin.com/2009-08-troubleshooting/comment-page-1/#comment-38</link>
		<dc:creator>Hélène Martin</dc:creator>
		<pubDate>Tue, 18 Aug 2009 23:01:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.helenemartin.com/?p=245#comment-38</guid>
		<description>Interesting anecdote.  I think you&#039;re absolutely right that asking the right question is most of the battle!</description>
		<content:encoded><![CDATA[<p>Interesting anecdote.  I think you&#8217;re absolutely right that asking the right question is most of the battle!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig</title>
		<link>http://www.helenemartin.com/2009-08-troubleshooting/comment-page-1/#comment-37</link>
		<dc:creator>Craig</dc:creator>
		<pubDate>Tue, 18 Aug 2009 22:43:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.helenemartin.com/?p=245#comment-37</guid>
		<description>I would assert that 90% of &quot;knowing how to fix computers&quot; is knowing how to ask the right question. Awareness of which search terms are likely to drill down to what you&#039;re looking for is both a learned skill and a problem of vocabulary. I was much less effective at helping people in Japan because I just didn&#039;t know what words to search for in Google.</description>
		<content:encoded><![CDATA[<p>I would assert that 90% of &#8220;knowing how to fix computers&#8221; is knowing how to ask the right question. Awareness of which search terms are likely to drill down to what you&#8217;re looking for is both a learned skill and a problem of vocabulary. I was much less effective at helping people in Japan because I just didn&#8217;t know what words to search for in Google.</p>
]]></content:encoded>
	</item>
</channel>
</rss>