<?xml version="1.0"?>
<rss version="2.0">
<channel>
  <title>Jason Menard&#039;s Weblog - Reviews category</title>
  <link>http://www.jmenard.com/blog/categories/reviews/</link>
  <description>java, software engineering, and all that jazz</description>
  <language>en</language>
  <copyright>Jason Menard</copyright>
  <lastBuildDate>Sun, 01 Jul 2007 02:44:00 GMT</lastBuildDate>
  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>Review - Release It!</title>
    <link>http://www.jmenard.com/blog/2007/06/30/review_release_it.html</link>
    
      
        <description>
          &lt;p&gt;&lt;a href=&#034;http://www.amazon.com/exec/obidos/ASIN/0978739213/jr_bunk-20&#034;&gt;&lt;img hspace=&#034;8&#034; border=&#034;0&#034; align=&#034;left&#034; src=&#034;http://images.amazon.com/images/P/0978739213.01.MZZZZZZZ.jpg&#034; alt=&#034;&#034; /&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Many of the texts on software engineering discuss following some methodology to produce an ideal design.  Working developers quickly learn that the ideal is rarely reality and things happen once we release software out into the wild.  Michael Nygard&#039;s &#034;Release It!&#034; picks up where these other books leave off.&lt;/p&gt;

&lt;p&gt;Nygard talks about all the things that can and will go wrong in the finely crafted software we were sure was ready for production.  A full two-thirds of the book is focused on capacity and stability issues including patterns and anti-patterns for both.  The remainder of the book deals with general design issues as well as maintaining health and status in an operational system.  &#034;Release It!&#034; provides many first hand accounts to illustrate his points, beginning with the Exception that grounded an airline, and these stories serve as excellent motivators.  It&#039;s better to learn from the mistakes of others, and I really appreciated the detail Nygard went into addressing some of these horror stories.&lt;/p&gt;

&lt;p&gt;The Pragmatic Programmers have a few &#034;must read&#034; books and &#034;Release It!&#034; is another one.  After reading it and heeding its advice, you&#039;ll feel a bit better knowing that your software is better prepared for the rigors of production.&lt;/p&gt;
        </description>
      
      
    
    
    
    <category>Reviews</category>
    
    <comments>http://www.jmenard.com/blog/2007/06/30/review_release_it.html#comments</comments>
    <guid isPermaLink="true">http://www.jmenard.com/blog/2007/06/30/review_release_it.html</guid>
    <pubDate>Sun, 01 Jul 2007 02:44:00 GMT</pubDate>
  </item>
  
  <item>
    <title>Review - Rails for Java Developers</title>
    <link>http://www.jmenard.com/blog/2007/05/19/review_rails_for_java_developers.html</link>
    
      
        <description>
          &lt;p&gt;&lt;a href=&#034;http://www.amazon.com/exec/obidos/ASIN/097761669X/jr_bunk-20&#034;&gt;&lt;img hspace=&#034;8&#034; border=&#034;0&#034; align=&#034;left&#034; alt=&#034;&#034; src=&#034;http://images.amazon.com/images/P/097761669X.01.MZZZZZZZ.jpg&#034; /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;In &amp;quot;Rails for Java Developers&amp;quot;, Stuart Halloway and Justin Gehtland provide an introduction to Ruby and the Rails web application framework aimed at the Java developer more familiar with frameworks such as Struts and Hibernate.  There&#039;s a lot of buzz in the Java community surrounding Ruby and Ruby on Rails so this title is quite timely.&lt;/p&gt;
&lt;p&gt;Halloway and Gehtland provide a tutorial to learning Ruby and Rails by examining similarities with Java.  The tutorial progresses by providing examples in both Ruby and Java using popular Java frameworks.  The introduction of Ruby and Rails concepts by juxtaposing them with similar concepts implemented in Java is comforting for the developer who may feel a little intimidated by the differences between the languages.  Working through the book, the Java developer will learn the basics about creating and deploying Ruby on Rails applications, picking up an exciting new language along the way.&lt;/p&gt;
&lt;p&gt;The first three chapters introduce the Ruby programming language.  This is the best Java-centric Ruby introduction that I&#039;ve seen and it&#039;s something I wish I had available to me when I was first learning the language.  The rest of the material covers the basics of Rails applications as well as web services and security issues.  I found the chapters on testing and automating the development process to be particularly good.&lt;/p&gt;
&lt;p&gt;The approach this book takes may not be suitable for everyone.  After a certain point, I found that the constant juxtaposition of the Java way of accomplishing a task with the Ruby on Rails way of accomplishing a task wore a bit thin.  I found myself just trying to skip past the Java bits to get on with the Ruby.  Still, I found the book to be quite good overall.  If you are an experienced Java developer seeking a gentle introduction to Ruby on Rails, you can&#039;t do better than &amp;quot;Rails for Java Developers&amp;quot;.&lt;/p&gt;
        </description>
      
      
    
    
    
    <category>Reviews</category>
    
    <comments>http://www.jmenard.com/blog/2007/05/19/review_rails_for_java_developers.html#comments</comments>
    <guid isPermaLink="true">http://www.jmenard.com/blog/2007/05/19/review_rails_for_java_developers.html</guid>
    <pubDate>Sun, 20 May 2007 03:55:00 GMT</pubDate>
  </item>
  
  <item>
    <title>Review - Everyday Scripting with Ruby: For Teams, Testers, and You</title>
    <link>http://www.jmenard.com/blog/2007/04/01/review_everyday_scripting_with_ruby_for_teams_testers_and_you.html</link>
    
      
        <description>
          &lt;p&gt; &lt;a href=&#034;http://www.amazon.com/exec/obidos/ASIN/0977616614/jr_bunk-20&#034;&gt;&lt;img hspace=&#034;8&#034; border=&#034;0&#034; align=&#034;left&#034; alt=&#034;&#034; src=&#034;http://images.amazon.com/images/P/0977616614.01.MZZZZZZZ.jpg&#034; /&gt;&lt;/a&gt; &lt;/p&gt;
&lt;p&gt;When I first heard that the Pragmatic Programmers were putting out a book on Ruby oriented towards testers, I thought to myself that I knew a few testers who might be able to benefit.&amp;nbsp; I was a bit surprised when I received the book and the focus changed from that of testing to something a bit more generic.&amp;nbsp; And after flipping through it I was afraid this would be just yet another book teaching Ruby.&lt;/p&gt;
&lt;p&gt;Despite my initial misgivings, as I read through the book its value became apparent.&amp;nbsp; This is not a book aimed at teaching people who are interested in developing complex systems in Ruby; this title is aimed squarely at using Ruby for scripting.&amp;nbsp; &amp;quot;Everyday Scripting with Ruby&amp;quot; is a task-oriented tutorial that will help the reader quickly become productive writing useful scripts.&amp;nbsp; The examples throughout the book are truly indicative of the types of problems that scripts are written to solve, and the book doesn&#039;t waste much time on fluff or things that are otherwise not likely to be of interest to the scripter.&lt;/p&gt;
&lt;p&gt;While &amp;quot;Everyday Scripting with Ruby&amp;quot; isn&#039;t much of a reference manual, it does work pretty well as a tutorial.&amp;nbsp; Readers will typically get the most value from the book by reading it cover-to-cover and following along by getting the examples working on their own computers.&amp;nbsp; Many of the chapters finish with problems for the reader to try out on their own, with the solutions to the problems being detailed in the back of the book.&amp;nbsp; Through reading the text, trying the examples, and further exploration of the material through tackling the end-of-chapter problems, the reader will come away confidant that they can use Ruby to successfully write scripts to solve their problems.&amp;nbsp; You can&#039;t ask for much more than that.&lt;/p&gt;
        </description>
      
      
    
    
    
    <category>Reviews</category>
    
    <comments>http://www.jmenard.com/blog/2007/04/01/review_everyday_scripting_with_ruby_for_teams_testers_and_you.html#comments</comments>
    <guid isPermaLink="true">http://www.jmenard.com/blog/2007/04/01/review_everyday_scripting_with_ruby_for_teams_testers_and_you.html</guid>
    <pubDate>Sun, 01 Apr 2007 22:59:00 GMT</pubDate>
  </item>
  
  <item>
    <title>Review - Practices of an Agile Developer</title>
    <link>http://www.jmenard.com/blog/2006/05/10/review_practices_of_an_agile_developer.html</link>
    
      
        <description>
          &lt;p&gt; &lt;a href=&#034;http://www.amazon.com/exec/obidos/ASIN/097451408X/jr_bunk-20&#034;&gt;&lt;img hspace=&#034;8&#034; border=&#034;0&#034; align=&#034;left&#034; alt=&#034;&#034; src=&#034;http://images.amazon.com/images/P/097451408X.01.MZZZZZZZ.jpg&#034; /&gt;&lt;/a&gt; &lt;/p&gt;
&lt;p&gt;&lt;em&gt;Agility&lt;/em&gt; remains a popular buzzword in the industry.  Methodologies, tools, and even programming languages have had the adjective applied to them.  But what does it mean to be an &amp;quot;agile developer&amp;quot;?  How do we know if we&#039;re &amp;quot;agile&amp;quot;?  Should I expect the ladies to saunter over at parties and say, &amp;quot;I couldn&#039;t help noticing that you&#039;re agile, how about coming back to my place&amp;quot;?  To answer these questions, a good place to start would be to read &lt;em&gt;Practices of an Agile Developer&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;This book, which could have easily been titled &lt;em&gt;Forty-five Habits of Highly Agile People&lt;/em&gt;, starts out by defining agility and what it means for something to be agile.  It then proceeds to layout forty-five agile practices grouped into seven areas: Beginning Agility, Feeding Agility, Delivering What Users Want, Agile Feedback, Agile Coding, Agile Debugging, and Agile Collaboration.  Your companions on your journey are a demon whose taunts remind you of how not to do things, and a guardian angel eager to steer you onto the path of righteous agility.  Each practice is well motivated and adequately described.  Additionally, each has sections letting you know what it should feel like if you are following the practice correctly, and how to strike a balance to keep from going overboard or not far enough when following a particular practice.&lt;/p&gt;
&lt;p&gt;While the focus of this book is agility, the practices described really lend themselves well to all developers, even the agility impaired.  Practices such as &amp;quot;Question until you understand&amp;quot; and &amp;quot;Write cohesive code&amp;quot;, to name only a couple, are just plain old good advice for anyone who writes code.  So even if you don&#039;t aspire to reach the summits of agility, you can look at this book as a self-help book for developers.  Read it, soak in some of the good sense it offers, and be better for it.&lt;/p&gt;
        </description>
      
      
    
    
    
    <category>Reviews</category>
    
    <comments>http://www.jmenard.com/blog/2006/05/10/review_practices_of_an_agile_developer.html#comments</comments>
    <guid isPermaLink="true">http://www.jmenard.com/blog/2006/05/10/review_practices_of_an_agile_developer.html</guid>
    <pubDate>Wed, 10 May 2006 04:23:15 GMT</pubDate>
  </item>
  
  <item>
    <title>Review - Best of Ruby Quiz</title>
    <link>http://www.jmenard.com/blog/2006/05/10/review_best_of_ruby_quiz.html</link>
    
      
        <description>
          &lt;p&gt; &lt;a href=&#034;http://www.amazon.com/exec/obidos/ASIN/0976694077/jr_bunk-20&#034;&gt;&lt;img hspace=&#034;8&#034; border=&#034;0&#034; align=&#034;left&#034; src=&#034;http://images.amazon.com/images/P/0976694077.01.MZZZZZZZ.jpg&#034; alt=&#034;&#034; /&gt;&lt;/a&gt; &lt;/p&gt;
&lt;p&gt;Picking up the basics of a new programming language such as Ruby can be enjoyable, but if you can&#039;t apply what you&#039;ve learned quickly that knowledge may be fleeting. &lt;em&gt;Best of Ruby Quiz&lt;/em&gt; can help out.  &lt;em&gt;Best of Ruby Quiz&lt;/em&gt; contains twenty-five fun programming challenges (&amp;quot;quizzes&amp;quot;) that are excellent for exercising your new Ruby chops.  The quizzes vary in difficulty and each includes in-depth discussions covering multiple solutions.  More importantly, the quizzes really are fun!&lt;/p&gt;
&lt;p&gt;The quizzes in &lt;em&gt;Best of Ruby Quiz&lt;/em&gt; are excerpted from the author&#039;s web site &amp;quot;Ruby Quiz&amp;quot; so while you could certainly save yourself a few bucks and just visit the site, the book is a much more polished product.  Also, I believe that the immediacy of the book with its superior layout really enhances the learning experience when compared to the web site.&lt;/p&gt;
&lt;p&gt;This book makes a great companion to the Pickaxe and the two books form an effective one-two punch for learning Ruby.  So go ahead and sit down with a copy of this book, fire up the code editor of your choice, pick a quiz and start coding.  Not only will you learn a thing or two about Ruby, you&#039;ll have a good time doing it.&lt;/p&gt;
        </description>
      
      
    
    
    
    <category>Reviews</category>
    
    <comments>http://www.jmenard.com/blog/2006/05/10/review_best_of_ruby_quiz.html#comments</comments>
    <guid isPermaLink="true">http://www.jmenard.com/blog/2006/05/10/review_best_of_ruby_quiz.html</guid>
    <pubDate>Wed, 10 May 2006 04:19:27 GMT</pubDate>
  </item>
  
  </channel>
</rss>
