<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Posts tagged peer-review  - Entropy and Ecstasy</title><link>http://aaron.maenpaa.ca/blog/tags/peer-review/</link><description>The most recent ranting and ravings of a madman.</description><lastBuildDate>Sun, 22 May 2016 05:32:35 GMT</lastBuildDate><generator>PyRSS2Gen-1.0.0</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Design Critique</title><link>http://aaron.maenpaa.ca/blog/entries/2014/11/10/design_critique/</link><description>&lt;blockquote&gt;
&lt;p&gt;To evaluate design, you must be impartial. You have to check your personal taste and predispositions at the door and consider whether the work succeeds in solving the problem at hand.&lt;/p&gt;
&lt;p class="attribution"&gt;—&lt;a class="reference external" href="http://bootstrappingdesign.com/"&gt;Bootstrapping Design&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Here Jarrod is talking about design reviews in art school... but this resonates with my experience doing code review. One of the rabbit holes it's easy to fall into is picking at stuff you'd have done differently independent of whether or not it would actually make the work better.&lt;/p&gt;
</description><guid isPermaLink="true">http://aaron.maenpaa.ca/blog/entries/2014/11/10/design_critique/</guid><pubDate>Mon, 10 Nov 2014 10:29:15 GMT</pubDate></item></channel></rss>