<?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: Other people&#8217;s expectations</title>
	<atom:link href="http://blog.melchua.com/2006/12/17/other-peoples-expectations/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.melchua.com/2006/12/17/other-peoples-expectations/</link>
	<description>Braindump of the Mel. Seek coherency and relevance at your own risk.</description>
	<lastBuildDate>Thu, 09 Sep 2010 01:13:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mel</title>
		<link>http://blog.melchua.com/2006/12/17/other-peoples-expectations/comment-page-1/#comment-155</link>
		<dc:creator>Mel</dc:creator>
		<pubDate>Tue, 19 Dec 2006 06:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.melchua.com/2006/12/17/other-peoples-expectations/#comment-155</guid>
		<description>Some people do it better than others. I believe that a good coach, teacher, (or more broadly, feedback-giver) is one that does take into account the situation of the other person as best they can; they&#039;ll never get it perfectly, but they might notice a few things about you that you missed.&lt;br/&gt;&lt;br/&gt;And sometimes &quot;I would have done it another way&quot; is valuable feedback to have. In the case you mentioned, had I been one of the seniors on that project and heard your comment, I would have taken that as a reason for me to become more software-fluent. Not because David Does It So It Must Be Better And I Should Do It Too, but because being able to understand your perspective will ultimately make my own perspective better.</description>
		<content:encoded><![CDATA[<p>Some people do it better than others. I believe that a good coach, teacher, (or more broadly, feedback-giver) is one that does take into account the situation of the other person as best they can; they&#8217;ll never get it perfectly, but they might notice a few things about you that you missed.</p>
<p>And sometimes &#8220;I would have done it another way&#8221; is valuable feedback to have. In the case you mentioned, had I been one of the seniors on that project and heard your comment, I would have taken that as a reason for me to become more software-fluent. Not because David Does It So It Must Be Better And I Should Do It Too, but because being able to understand your perspective will ultimately make my own perspective better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Klempner</title>
		<link>http://blog.melchua.com/2006/12/17/other-peoples-expectations/comment-page-1/#comment-154</link>
		<dc:creator>David Klempner</dc:creator>
		<pubDate>Mon, 18 Dec 2006 08:06:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.melchua.com/2006/12/17/other-peoples-expectations/#comment-154</guid>
		<description>Another thought, along the same lines: they really aren&#039;t &lt;i&gt;that&lt;/i&gt; qualified to give you substantial feedback.&lt;br/&gt;&lt;br/&gt;That is, &quot;I would have done it this other way&quot; isn&#039;t that useful of feedback. The feedback you&#039;d really need is &quot;this won&#039;t work&quot;, but you can&#039;t really figure that out until you&#039;re done.&lt;br/&gt;&lt;br/&gt;Also, even the &quot;I would have done it another way&quot; feedback cannot really take into account skills.&lt;br/&gt;&lt;br/&gt;I saw what I initially viewed as absurd misdesign in a senior project back last fall in my own program. Specifically, they were using a piece of hardware that had a parallel port connector, but their software only spoke serial. So, naturally, they solved the problem with extra hardware rather than doing an easy solution in software.&lt;br/&gt;&lt;br/&gt;On the other hand, I don&#039;t think their team went on to do kernel programming in their first job. As much as a software approach is both objectively better and easier for a programmer, if they didn&#039;t have any programmers on their team &lt;i&gt;their&lt;/i&gt; approach was distinctly better.&lt;br/&gt;&lt;br/&gt;It&#039;s hard to account for that sort of thing in feedback.</description>
		<content:encoded><![CDATA[<p>Another thought, along the same lines: they really aren&#8217;t <i>that</i> qualified to give you substantial feedback.</p>
<p>That is, &#8220;I would have done it this other way&#8221; isn&#8217;t that useful of feedback. The feedback you&#8217;d really need is &#8220;this won&#8217;t work&#8221;, but you can&#8217;t really figure that out until you&#8217;re done.</p>
<p>Also, even the &#8220;I would have done it another way&#8221; feedback cannot really take into account skills.</p>
<p>I saw what I initially viewed as absurd misdesign in a senior project back last fall in my own program. Specifically, they were using a piece of hardware that had a parallel port connector, but their software only spoke serial. So, naturally, they solved the problem with extra hardware rather than doing an easy solution in software.</p>
<p>On the other hand, I don&#8217;t think their team went on to do kernel programming in their first job. As much as a software approach is both objectively better and easier for a programmer, if they didn&#8217;t have any programmers on their team <i>their</i> approach was distinctly better.</p>
<p>It&#8217;s hard to account for that sort of thing in feedback.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
