<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Beautiful code...</title><link>http://blogs.msdn.com/b/ericgu/archive/2007/08/14/beautiful-code.aspx</link><description>O'reilly publishes Beautiful Code 
 Jonathan Edwards counters with a beautiful explanation . 
 Now, I haven't read the new book, but I have a strong resonance with what Edwards wrote. You should definitely read the whole thing, but I few sentences jumped</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Beautiful code... best written by two or more</title><link>http://blogs.msdn.com/b/ericgu/archive/2007/08/14/beautiful-code.aspx#4594410</link><pubDate>Mon, 27 Aug 2007 20:00:39 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4594410</guid><dc:creator>noslenytram</dc:creator><description>&lt;p&gt;I find that pair programming solves much of &amp;quot;not smart enough&amp;quot; problem. &amp;nbsp;The common sense of one is always questionable. &amp;nbsp;If two agree, success rates (and the chance of beautiful code) go way up.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=4594410" width="1" height="1"&gt;</description></item><item><title>re: Beautiful code...</title><link>http://blogs.msdn.com/b/ericgu/archive/2007/08/14/beautiful-code.aspx#4493502</link><pubDate>Tue, 21 Aug 2007 15:09:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4493502</guid><dc:creator>Jon Kruger</dc:creator><description>&lt;p&gt;Great points... sometimes I have to remind myself that the architecture itself is not the deliverable! &amp;nbsp;It's always tempting to want to refactor some piece of old code because I want it to look better or be more &amp;quot;correct&amp;quot; from a design perspective, but many times that refactoring isn't going to provide enough business value for all the time I spent on it.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=4493502" width="1" height="1"&gt;</description></item><item><title>re: Beautiful code...</title><link>http://blogs.msdn.com/b/ericgu/archive/2007/08/14/beautiful-code.aspx#4483608</link><pubDate>Mon, 20 Aug 2007 21:42:41 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4483608</guid><dc:creator>Oisin Grehan</dc:creator><description>&lt;p&gt;You say &amp;quot;The goal is not to have beautiful, elegant, code. The goal is to have *useful* code that does what you need it to do.&amp;quot;&lt;/p&gt;
&lt;p&gt;I think this is too simplistic a view; they are not so easy to separate as concepts. Besides, if I was to concentrate on the latter without any attention to the former, I would probably feel compelled change careers in a matter of weeks. Constructing things that are &amp;quot;beautiful&amp;quot; [to us] is part of the joy of living day to day, no?&lt;/p&gt;
&lt;p&gt;- Oisin&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=4483608" width="1" height="1"&gt;</description></item><item><title>re: Beautiful code...</title><link>http://blogs.msdn.com/b/ericgu/archive/2007/08/14/beautiful-code.aspx#4402345</link><pubDate>Wed, 15 Aug 2007 19:50:22 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4402345</guid><dc:creator>Frank Hileman</dc:creator><description>&lt;p&gt;Isn't it just a catchy title? The essays inside don't have much to do with each other. &amp;quot;Boring designs&amp;quot; would not be so catchy.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=4402345" width="1" height="1"&gt;</description></item><item><title>re: Beautiful code...</title><link>http://blogs.msdn.com/b/ericgu/archive/2007/08/14/beautiful-code.aspx#4397605</link><pubDate>Wed, 15 Aug 2007 11:55:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4397605</guid><dc:creator>Stu Smith</dc:creator><description>&lt;p&gt;I'm halfway through the book, and the thing I liked most about it isn't that it has loads of techniques, or that it tries to tell you the &amp;quot;one true methodology&amp;quot;, but that it makes you think. There was some code in there that I thought was horribly ugly - but I was always thinking about what might be more beautiful.&lt;/p&gt;
&lt;p&gt;I think the title of the book is perhaps deliberately controversial - but the fact that we're all talking about it says something. This isn't a book that teaches - it's a book you argue with.&lt;/p&gt;
&lt;p&gt;(Personally, I'd put your 30-minute argument slightly differently - any design which takes more than 30 mins to EXPLAIN is probably a waste of time).&lt;/p&gt;
&lt;p&gt;Stu&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=4397605" width="1" height="1"&gt;</description></item><item><title>re: Beautiful code...</title><link>http://blogs.msdn.com/b/ericgu/archive/2007/08/14/beautiful-code.aspx#4389299</link><pubDate>Tue, 14 Aug 2007 23:41:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4389299</guid><dc:creator>Matthew Cuba</dc:creator><description>&lt;p&gt;I suspect I can learn something from the book and will probably pick it up, but in the end, the code I write needs to work, be efficient and clear. &amp;nbsp;I'm not overly concerned about writing so that the new hire can follow it; I'm concerned about writing it so that *I* can follow it 12 months from now when it needs to change and it isn't fresh in my mind. &amp;nbsp;The new hire will ask if s/he has questions. &amp;nbsp;I'm certainly not going out of my way to obfuscate the code. &amp;nbsp;Simplicity rocks - everything else is at first clever and later a pain.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=4389299" width="1" height="1"&gt;</description></item><item><title>re: Beautiful code...</title><link>http://blogs.msdn.com/b/ericgu/archive/2007/08/14/beautiful-code.aspx#4389111</link><pubDate>Tue, 14 Aug 2007 23:26:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4389111</guid><dc:creator>Charles</dc:creator><description>&lt;p&gt;Michael, if it we're me I wouldn't say code level design. I would say one work unit of design. &amp;nbsp;Whatever that unit might be. For some it may be a 1000 ft. overview diagram, for others it may be a page, for still others it may be a function. &amp;nbsp;I think that whatever one plans to do, accomplish or delegate before re-evaluating and moving on should take no more than 30 minutes of design time.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=4389111" width="1" height="1"&gt;</description></item><item><title>re: Beautiful code...</title><link>http://blogs.msdn.com/b/ericgu/archive/2007/08/14/beautiful-code.aspx#4386760</link><pubDate>Tue, 14 Aug 2007 20:52:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4386760</guid><dc:creator>Reeve Fritchman</dc:creator><description>&lt;p&gt;Doesn't code have to be read by others and maintained by others?&lt;/p&gt;
&lt;p&gt;In writing application code, I assume Darwin had it wrong. &amp;nbsp;While writing a nice long expression may be elegant, I have to assume the 7th programmer (my target audience) working on the code will be a new hire, unfamiliar with the application, and possibly clueless. &amp;nbsp;So, I'll break the long expression down into something easily digestible.&lt;/p&gt;
&lt;p&gt;Even then, it's often not good enough!&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=4386760" width="1" height="1"&gt;</description></item><item><title>re: Beautiful code...</title><link>http://blogs.msdn.com/b/ericgu/archive/2007/08/14/beautiful-code.aspx#4385597</link><pubDate>Tue, 14 Aug 2007 19:29:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4385597</guid><dc:creator>Michael Giagnocavo</dc:creator><description>&lt;p&gt;Of course correctness needs to be #1 priority in a program, but hopefully #2 will be clarity. &lt;/p&gt;
&lt;p&gt;With respects to over 30 minutes of design being a waste of time, I'm assuming you mean purely code-level design?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=4385597" width="1" height="1"&gt;</description></item><item><title>MSDN Blog Postings  &amp;raquo; Beautiful code...</title><link>http://blogs.msdn.com/b/ericgu/archive/2007/08/14/beautiful-code.aspx#4385460</link><pubDate>Tue, 14 Aug 2007 19:20:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4385460</guid><dc:creator>MSDN Blog Postings  » Beautiful code...</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://msdnrss.thecoderblogs.com/2007/08/14/beautiful-code/"&gt;http://msdnrss.thecoderblogs.com/2007/08/14/beautiful-code/&lt;/a&gt;&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=4385460" width="1" height="1"&gt;</description></item></channel></rss>