<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
  <channel>
    <title>Nate Klaiber</title>
    <link>http://nateklaiber.com</link>
    <description>Nate Klaiber</description>
    <geo:lat>40.477187</geo:lat><geo:long>-81.444397</geo:long><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/nateklaiber" type="application/rss+xml" /><item>
      <title>Seth Godin: Find your voice</title>
      <link>http://feedproxy.google.com/~r/nateklaiber/~3/oVgb4OdJKCI/seth-godin-find-your-voice</link>
      <description>&lt;blockquote&gt;&lt;p&gt;Find your voice, don't copy someone else's. &lt;cite&gt;&lt;a href="http://sethgodin.typepad.com/seths_blog/2009/06/find-your-voice.html"&gt;via&lt;/a&gt;&lt;/cite&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;img src="http://feeds.feedburner.com/~r/nateklaiber/~4/oVgb4OdJKCI" height="1" width="1"/&gt;</description>
      <dc:creator>Nate  Klaiber</dc:creator>
      <guid isPermaLink="false">http://nateklaiber.com/tumblelog/2009/6/29/seth-godin-find-your-voice</guid>
      <pubDate>Mon Jun 29 09:33:00 UTC 2009</pubDate>
    <feedburner:origLink>http://nateklaiber.com/tumblelog/2009/6/29/seth-godin-find-your-voice</feedburner:origLink></item>
    <item>
      <title>Uncle Bob: Crap code inevitable?</title>
      <link>http://feedproxy.google.com/~r/nateklaiber/~3/UFTe3S3N0wM/uncle-bob-crap-code-inevitable</link>
      <description>&lt;blockquote&gt;&lt;p&gt;Low quality code is not cheaper; it is vastly more expensive, even in the short term. Bad code slows everyone down from the minute that it is written. It creates a continuous and copious drag on further progress. It requires armies of coders to overcome that drag; and those armies must grow exponentially to maintain constant velocity against that drag. &lt;cite&gt;(&lt;a href="http://blog.objectmentor.com/articles/2009/04/23/crap-code-inevitable-rumblings-from-accu" title="Crap Code Inevitable?  Rumblings from ACCU."&gt;via&lt;/a&gt;)&lt;/cite&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;img src="http://feeds.feedburner.com/~r/nateklaiber/~4/UFTe3S3N0wM" height="1" width="1"/&gt;</description>
      <dc:creator>Nate  Klaiber</dc:creator>
      <guid isPermaLink="false">http://nateklaiber.com/tumblelog/2009/4/23/uncle-bob-crap-code-inevitable</guid>
      <pubDate>Thu Apr 23 08:09:00 UTC 2009</pubDate>
    <feedburner:origLink>http://nateklaiber.com/tumblelog/2009/4/23/uncle-bob-crap-code-inevitable</feedburner:origLink></item>
    <item>
      <title>TA: Swim with the current</title>
      <link>http://feedproxy.google.com/~r/nateklaiber/~3/lIkYUN30AMU/ta-swim-with-the-current</link>
      <description>&lt;blockquote&gt;&lt;p&gt;If you intend to remain viable as a business, realize that there is no escape from the current.  The marketplace &lt;em&gt;is&lt;/em&gt; the current.  Turbulence is inescapable.  Resistance as a defense only makes things worse. Instead, remain stable and absorb.  Yield to the current and make your way, surely and swiftly, to a new shore. &lt;cite&gt;&lt;a href="http://www.acleareye.com/sandbox_wisdom/2009/04/the-current-is.html" title="acleareye.com: Swim with the current"&gt;via&lt;/a&gt;&lt;/cite&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;img src="http://feeds.feedburner.com/~r/nateklaiber/~4/lIkYUN30AMU" height="1" width="1"/&gt;</description>
      <dc:creator>Nate  Klaiber</dc:creator>
      <guid isPermaLink="false">http://nateklaiber.com/tumblelog/2009/4/22/ta-swim-with-the-current</guid>
      <pubDate>Wed Apr 22 08:36:00 UTC 2009</pubDate>
    <feedburner:origLink>http://nateklaiber.com/tumblelog/2009/4/22/ta-swim-with-the-current</feedburner:origLink></item>
    <item>
      <title>Aaron Boeving launches new website</title>
      <link>http://feedproxy.google.com/~r/nateklaiber/~3/pWc-f_nCk30/aaron-boeving-launches-new-website</link>
      <description>&lt;p&gt;I will have more to say about his recent design in an upcoming blog post, but I wanted to at least say congrats to Aaron for getting his new design out into the wild. Some of you may have seen it as &lt;a href="http://www.unmatchedstyle.com/gallery/aaronboevingcom.php" title="aaronboeving.com | Unmatched Style"&gt;featured on Unmatched Style&lt;/a&gt; recently, if not, then check out &lt;a href="http://www.aaronboeving.com"&gt;Aaron Boeving&lt;/a&gt; for all the goodness. &lt;/p&gt;
&lt;p&gt;As a side note, Aaron and I worked together on designing &lt;a href="http://www.nkbookreviews.com" title="Nate Klaiber Book Reviews"&gt;my personal book review site&lt;/a&gt;. I posted a new review there today on the book, &lt;em&gt;Design Patterns in Ruby&lt;/em&gt; by Russ Olsen. If you are a Ruby developer and are interested, &lt;a href="http://www.nkbookreviews.com/reviews/design-patterns-in-ruby" title="Design Patterns in Ruby (Book Review) - Review - Nate Klaiber Book Reviews"&gt;check out the review&lt;/a&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/nateklaiber/~4/pWc-f_nCk30" height="1" width="1"/&gt;</description>
      <dc:creator>Nate  Klaiber</dc:creator>
      <guid isPermaLink="false">http://nateklaiber.com/tumblelog/2009/4/2/aaron-boeving-launches-new-website</guid>
      <pubDate>Thu Apr 02 09:57:00 UTC 2009</pubDate>
    <feedburner:origLink>http://nateklaiber.com/tumblelog/2009/4/2/aaron-boeving-launches-new-website</feedburner:origLink></item>
    <item>
      <title>37Signals: Make it memorable</title>
      <link>http://feedproxy.google.com/~r/nateklaiber/~3/CAkzlL2IL5w/37signals-make-it-memorable</link>
      <description>&lt;blockquote&gt;&lt;p&gt;It was during this time that I’d think about the sites that I appreciated from a design standpoint. Many of them are personal blogs or cool brochure sites. I began to realize that these sites displayed information well, but I could not exactly remember what they were about. They sure were pretty with fantastic CSS, but I can’t really remember what what the site said. Did it say anything? &lt;a href="http://www.37signals.com/svn/posts/1652-designers-make-it-memorable"&gt;&lt;cite&gt;via&lt;/cite&gt;&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;img src="http://feeds.feedburner.com/~r/nateklaiber/~4/CAkzlL2IL5w" height="1" width="1"/&gt;</description>
      <dc:creator>Nate  Klaiber</dc:creator>
      <guid isPermaLink="false">http://nateklaiber.com/tumblelog/2009/3/30/37signals-make-it-memorable</guid>
      <pubDate>Mon Mar 30 08:07:00 UTC 2009</pubDate>
    <feedburner:origLink>http://nateklaiber.com/tumblelog/2009/3/30/37signals-make-it-memorable</feedburner:origLink></item>
    <item>
      <title>Seth Godin: Yeah, but he really knows his stuff</title>
      <link>http://feedproxy.google.com/~r/nateklaiber/~3/7MD0z98206c/seth-godin-yeah-but-he-really-knows-his-stuff</link>
      <description>&lt;blockquote&gt;&lt;p&gt;He's the first one to point out a minor technical glitch and the last guy to want to get on board with a new program. He hazes first-timers and avoids the people who are actually productive. Or he's the one who can take any metaphor and make it literal, instantly, poking holes in it as he goes.&lt;/p&gt;

&lt;p&gt;And of course, he's the one everyone has to tiptoe around, because they know his technical status can sink their initiative.&lt;/p&gt;

&lt;p&gt;I think you should fire this person immediately. Okay, maybe give him exactly one warning.&lt;a href="http://sethgodin.typepad.com/seths_blog/2009/03/yeah-but-he-really-knows-his-stuff.html"&gt;&lt;cite&gt;via&lt;/cite&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/nateklaiber/~4/7MD0z98206c" height="1" width="1"/&gt;</description>
      <dc:creator>Nate  Klaiber</dc:creator>
      <guid isPermaLink="false">http://nateklaiber.com/tumblelog/2009/3/23/seth-godin-yeah-but-he-really-knows-his-stuff</guid>
      <pubDate>Mon Mar 23 07:51:00 UTC 2009</pubDate>
    <feedburner:origLink>http://nateklaiber.com/tumblelog/2009/3/23/seth-godin-yeah-but-he-really-knows-his-stuff</feedburner:origLink></item>
    <item>
      <title>Seth Godin: What would a professional do?</title>
      <link>http://feedproxy.google.com/~r/nateklaiber/~3/wn_DnF66LIk/seth-godin-what-would-a-professional-do</link>
      <description>&lt;blockquote&gt;&lt;p&gt; Does your customer/client/employee actually believe that they haven't been shortchanged by your amateur performance? &lt;strong&gt;It is costing you in ways you're not measuring because you're willfully ignoring the consequences?&lt;/strong&gt; Think of all the sub-pro experiences you've had as a customer, instances where someone was pretending to be a chef or a bartender or a computer jock but just came up short... Were you delighted? &lt;cite&gt;&lt;a href="http://sethgodin.typepad.com/seths_blog/2009/01/what-would-a-professional-do.html"&gt;via&lt;/a&gt;&lt;/cite&gt;&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Really enjoyed this particular part of his entry today. While I will be the first to admit that I am continually learning, I stumble across many people at the ground level (think basic HTML 101) who are marketing themselves as 'web designers'. I watch them work hours to complete tasks that should literally take them minutes when done the right way. I see the outcome as something that is unmaintainable and unusable. Then I watch the cycle repeat time and time again. Time is money, in these instances. The amateurs spend hours of their time (business time), doing basic tasks. This cost is then passed on to the client. The client then pays more, and gets much less.&lt;/p&gt;
&lt;p&gt;Design is not a strength of mine (gasp, you say, as you look at this finely crafted blog!). For client projects, I will seek out a professional designer. Someone who knows the great details of designing for the web. Someone who is a true professional. Sure, I could do it - but it would take twice as long and the results wouldn't come close to that of a professional designer. It's about working smarter, not harder. When it comes to a client on the other end, then it also becomes an ethical decision, in my opinion.&lt;/p&gt;
&lt;p&gt;The truth of the matter is this will never end. There will always be amateurs out there (I say that in the nicest way possible), not knowing how to do things but are able to sell it. They often times equate quantity with quality. More output equals better. I tend to think the opposite. Find the right people to network with. Find the people passionate about what they do. Network with these people to help create quality products. More output is not necessarily better.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/nateklaiber/~4/wn_DnF66LIk" height="1" width="1"/&gt;</description>
      <dc:creator>Nate  Klaiber</dc:creator>
      <guid isPermaLink="false">http://nateklaiber.com/tumblelog/2009/1/29/seth-godin-what-would-a-professional-do</guid>
      <pubDate>Thu Jan 29 08:53:00 UTC 2009</pubDate>
    <feedburner:origLink>http://nateklaiber.com/tumblelog/2009/1/29/seth-godin-what-would-a-professional-do</feedburner:origLink></item>
    <item>
      <title>I need your help with the direction of NK Book Reviews</title>
      <link>http://feedproxy.google.com/~r/nateklaiber/~3/m1MtRq3dOIg/i-need-your-help-with-the-direction-of-nk-book-reviews</link>
      <description>&lt;h3&gt;Happening at NK Book Reviews&lt;/h3&gt;
&lt;p&gt;I have been making some more changes over at &lt;a href="http://www.nkbookreviews.com"&gt;www.nkbookreviews.com&lt;/a&gt;. Some of them are visible changes, and some are still behind the scenes for future feature releases. I am excited about the culmination of data I have related to all of the books, authors, and publishers. Here's some of the content that has been added recently:&lt;/p&gt;
	
&lt;p&gt;I recently finished reviewing &lt;a href="http://www.nkbookreviews.com/books/building-findable-websites-web-standards-seo-and-beyond"&gt;&lt;em&gt;Building Findable Websites&lt;/em&gt;&lt;/a&gt; by &lt;a href="http://www.nkbookreviews.com/authors/aarronwalter"&gt;Aarron Walter&lt;/a&gt;. Here is a short snippet of the review:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;There are many pieces of the puzzle that fit together to portray the big picture, and it is up to us as web developers to make sure all of those pieces are in place for the end users. Some of these things include &lt;em&gt;accessibility&lt;/em&gt;, &lt;em&gt;usability&lt;/em&gt;, &lt;em&gt;copywriting&lt;/em&gt;, &lt;em&gt;information architecture&lt;/em&gt;, &lt;em&gt;design&lt;/em&gt;, and more. That's what this entire book is about - putting the pieces of the puzzle together to create a useful, usable, search engine friendly, and ultimately, findable website. &lt;cite&gt;&lt;a href="http://www.nkbookreviews.com/reviews/building-findable-websites-web-standards-seo-and-beyond"&gt;Read More&lt;/a&gt;&lt;/cite&gt;&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;I recently received, and am currently reading, &lt;a href="http://www.nkbookreviews.com/books/programming-in-objective-c-2-0-second-edition"&gt;&lt;em&gt;Programming in Objective-C 2.0&lt;/em&gt;&lt;/a&gt; by &lt;a href="http://www.nkbookreviews.com/authors/stephenkochan"&gt;Stephen Kochan&lt;/a&gt;. I am completely new to the programming scene on Mac OS X and iPhone development, and this has proven to be a very good read so far. It is geared towards beginners, so the first few chapters have been programming basics in the context of Objective-C. I am very impressed at the author's ability to gradually show shorthand techniques, by first showing the base of how you can achieve different tasks (IE: If/Else and Ternary operator). This is a tough book to put down, and since I am completely new to this - I often times find myself in front of the computer running through the different exercises at the end of each chapter. I look forward to finishing this book.&lt;/p&gt;

&lt;p&gt;Outside of regular content, I have also integrated what I think to be some &lt;strong&gt;very useful advertising pieces&lt;/strong&gt;. On some pages you will now see information from &lt;a href="http://www.authenticjobs.com"&gt;Authentic Jobs&lt;/a&gt; and &lt;a href="http://www.inthesidebar.com"&gt;SidebarAds&lt;/a&gt;. A big thank you to both Cameron Moll and Jonathan Snook for coordinating this with me. My goal with these are simple. I have had several people in the past contact me about different jobs or services related to web development. Some looking for jobs in the industry, and still others looking to get different work done. I have done my best to point people in the right direction, and most of the time it would lead back to Authentic Jobs. Initially they are using the default embedded advertisements, but I am working behind the scenes now on the Authentic Jobs API to integrate the job postings with more targeted content related to book and review detail pages. I will keep you posted as more comes of that. I hope that some will find these useful as just another part to their education process.&lt;/p&gt;

&lt;p&gt;A &lt;strong&gt;search index is currently being integrated&lt;/strong&gt;. This was a feature I left out at the beginning, because it didn't quite feel ready to me. I didn't want to just settle with a &lt;code&gt;LIKE&lt;/code&gt; search on all of the information. I wanted to create a more useful and targeted search index. This obviously takes time, but I think there will be many benefits to having it done right.&lt;/p&gt;

&lt;h3&gt;Resources&lt;/h3&gt;
&lt;p&gt;I have been in conversation with Lachy about his recently released website, &lt;a href="http://www.uncoverr.com"&gt;Uncoverr.com&lt;/a&gt;. We have found that we both share some of the same goals and visions, and I look forward to collaborating with him in some different ventures in the future. He has a great vision for that website, and is actively getting more content to fill it out. He recently did an author interview with the one and only, &lt;a href="http://www.uncoverr.com/jonathan-snook/"&gt;Jonathan Snook&lt;/a&gt; (of the newly re-designed &lt;a href="http://www.snook.ca"&gt;snook.ca&lt;/a&gt;), and also posted a review of &lt;a href="http://www.uncoverr.com/javascript-the-missing-manual-review/"&gt;&lt;em&gt;JavaScript: The Missing Manual&lt;/em&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;Communication&lt;/h3&gt;
&lt;p&gt;For those who don't know, I have also added a &lt;a href="http://twitter.com/nkbookreviews"&gt;Twitter feed for nkbookreviews&lt;/a&gt;. I did this to supplement other avenues of communication. The &lt;strong&gt;twitter timeline&lt;/strong&gt; will be used for several things:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Let you know when a review is posted.&lt;/li&gt;
	&lt;li&gt;Keep you updated on books I am reading.&lt;/li&gt;
	&lt;li&gt;Snippets and quotes I find helpful or interesting from the books.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This will be used two ways. As I write to this feed, I will be pulling all of my thoughts back into the website to harvest with some other pieces of data.&lt;/p&gt;
&lt;p&gt;Next, I have been thinking about getting an &lt;strong&gt;email newsletter&lt;/strong&gt; in place. &lt;em&gt;Is this something you would subscribe to and find useful?&lt;/em&gt; I see it containing some of the same things as the twitter timeline, only on a less frequent posting schedule. Used as more of a brief overview of activity, an email dashboard of sorts.&lt;/p&gt;

&lt;h3&gt;Oops!&lt;/h3&gt;
&lt;p&gt;I have noticed recently that some URLs need to be updated for RSS subscriptions at the site. I will be updating these items this weekend to assure they get redirected to their proper spots. I apologize for those who have received errors with the feed while trying to subscribe. For now, the main feed to subscribe is &lt;a href="http://www.nkbookreviews.com/reviews/rss.xml" title="Nate Klaiber Book Reviews active RSS feed"&gt;http://www.nkbookreviews.com/reviews/rss.xml&lt;/a&gt;

&lt;h3&gt;I need your help&lt;/h3&gt;
&lt;p&gt;As I have gathered all of the different data for the reviews site, I am trying to find some of the different useful ways I can roll into useful features. My goal from the beginning was to keep the site as clean as possible, and make sure that each piece I added was useful and served a purpose. This meant that at launch time I actually removed several features, as I wasn't sure they were quite ready. Some of those were related to taggings, nested categorizing, and intended audiences, others were related to meta information from the books.&lt;/p&gt;

&lt;p&gt;So, my question for you is: &lt;strong&gt;When trying to find the right book on a certain topic, what do you look for in a review and extra information that help you make your decisions?&lt;/strong&gt; Be sure to let me know in the comments, or email me directly at &lt;a href="http://nateklaiber.comailto:nate@theklaibers.com"&gt;nate@theklaibers.com&lt;/a&gt;.&lt;p&gt;&lt;img src="http://feeds.feedburner.com/~r/nateklaiber/~4/m1MtRq3dOIg" height="1" width="1"/&gt;</description>
      <dc:creator>Nate  Klaiber</dc:creator>
      <guid isPermaLink="false">http://nateklaiber.com/blog/2009/1/17/i-need-your-help-with-the-direction-of-nk-book-reviews</guid>
      <pubDate>Sat Jan 17 13:24:01 UTC 2009</pubDate>
    <feedburner:origLink>http://nateklaiber.com/blog/2009/1/17/i-need-your-help-with-the-direction-of-nk-book-reviews</feedburner:origLink></item>
    <item>
      <title>Seth Godin: What to do when the new thing doesn't work</title>
      <link>http://feedproxy.google.com/~r/nateklaiber/~3/ivQVcYF7j7M/seth-godin-what-to-do-when-the-new-thing-doesnt-work</link>
      <description>&lt;blockquote&gt;&lt;p&gt;From the start, you have to choose a path and stick with it. Either you are on the path of the TV Industrial complex, and you're prepared to promote and spam and spend and make average stuff for average people... or you are busy embracing the new media for everything it can offer. &lt;cite&gt;&lt;a href="http://sethgodin.typepad.com/seths_blog/2009/01/what-to-do-when.html"&gt;via&lt;/a&gt;&lt;/cite&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;img src="http://feeds.feedburner.com/~r/nateklaiber/~4/ivQVcYF7j7M" height="1" width="1"/&gt;</description>
      <dc:creator>Nate  Klaiber</dc:creator>
      <guid isPermaLink="false">http://nateklaiber.com/tumblelog/2009/1/9/seth-godin-what-to-do-when-the-new-thing-doesnt-work</guid>
      <pubDate>Fri Jan 09 09:53:00 UTC 2009</pubDate>
    <feedburner:origLink>http://nateklaiber.com/tumblelog/2009/1/9/seth-godin-what-to-do-when-the-new-thing-doesnt-work</feedburner:origLink></item>
    <item>
      <title>Rails 3 to feature new guest, Merb</title>
      <link>http://feedproxy.google.com/~r/nateklaiber/~3/Dt2PDtx-Obo/rails-3-to-feature-new-guest-merb</link>
      <description>&lt;blockquote&gt;&lt;p&gt;There's absolutely no pleasing everyone. You can't and shouldn't try to make everyone love you. The best you can do is make sure that they're hating you for the right reasons.&lt;cite&gt;&lt;a href="http://www.loudthinking.com/posts/36-work-on-what-you-use-and-share-the-rest"&gt;via&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;I look forward to the merging of the two frameworks. It's a smart move that will ultimately give people more choice (and potentially less overhead or server footprint). In my time researching PHP Frameworks, I don't think I would see this happen with any of them - even if they all are trying to achieve the same goal. To me, it's not about competition - these are two bodies with the same passions, goals, and desires - just taking slightly different routes. Merging makes perfect sense.&lt;/p&gt;
&lt;p&gt;Now I wonder what CakePHP will do, will they try and find someone to merge with? I mean, it only makes logical sense with their hanging on the coattails of Rails and all ;)&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/nateklaiber/~4/Dt2PDtx-Obo" height="1" width="1"/&gt;</description>
      <dc:creator>Nate  Klaiber</dc:creator>
      <guid isPermaLink="false">http://nateklaiber.com/tumblelog/2008/12/24/rails-3-to-feature-new-guest-merb</guid>
      <pubDate>Wed Dec 24 09:20:00 UTC 2008</pubDate>
    <feedburner:origLink>http://nateklaiber.com/tumblelog/2008/12/24/rails-3-to-feature-new-guest-merb</feedburner:origLink></item>
    <item>
      <title>[NK Book Reviews] Website optimization: speed, search engine and conversion rate secrets</title>
      <link>http://feedproxy.google.com/~r/nateklaiber/~3/UMWOW6gvRIg/nk-book-reviews-website-optimization-speed-search-engine-and-conversion-rate-secrets</link>
      <description>&lt;p&gt;As I continue to migrate my reviews over to &lt;a href="http://www.nkbookreviews.com"&gt;http://www.nkbookreviews.com&lt;/a&gt;, I am going to cross-post some links to recent reviews. The most recent review was today, with &lt;a href="http://www.nkbookreviews.com/reviews/website-optimization-speed-search-engine-and-conversion-rate-secrets"&gt;Website Optimization: Speed, Search Engine and Conversion Rate Secrets&lt;/a&gt;. This is an O'Reilly book packed full of great information.&lt;/p&gt;

&lt;p&gt;If you haven't already, be sure to add the &lt;a href="http://www.nkbookreviews.com/reviews/rss"&gt;NK Book Reviews feed&lt;/a&gt; as it will have the most recent reviews and information. Thanks for reading, and let me know if you have any feedback as I spend time refining the process and website.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/nateklaiber/~4/UMWOW6gvRIg" height="1" width="1"/&gt;</description>
      <dc:creator>Nate  Klaiber</dc:creator>
      <guid isPermaLink="false">http://nateklaiber.com/tumblelog/2008/12/15/nk-book-reviews-website-optimization-speed-search-engine-and-conversion-rate-secrets</guid>
      <pubDate>Mon Dec 15 11:55:00 UTC 2008</pubDate>
    <feedburner:origLink>http://nateklaiber.com/tumblelog/2008/12/15/nk-book-reviews-website-optimization-speed-search-engine-and-conversion-rate-secrets</feedburner:origLink></item>
    <item>
      <title>D-I: How to build a gantt chart with the Google Charts API</title>
      <link>http://feedproxy.google.com/~r/nateklaiber/~3/D_F7MWpLCNk/d-i-how-to-build-a-gantt-chart-with-the-google-charts-api</link>
      <description>&lt;blockquote&gt;&lt;p&gt;The Google Charts API is an excellent way to add high quality charting to your web application.  We first started working with the API as part of the &lt;a href="http://www.simpli5.com"&gt;Simpli5&lt;/a&gt; dashboard development, and were quite impressed with its functionality and ease of use.  Wrapper classes were developed and added to our Sandstone Application Framework to make the addition charts to Simpli5 and other applications as simple as possible. &lt;cite&gt;&lt;a href="http://www.designinginteractive.com/code/how-to-build-a-gantt-chart-with-the-google-charts-api/"&gt;via&lt;/a&gt;&lt;/cite&gt;&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;This is truly an awesome way to use the Google Charts API. Dave got to show me how he worked this out first hand from a whiteboard, and I was impressed. If you have a need to integrate gantt charts into an application you are working on, be sure to check this out first to save you some potential headaches.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/nateklaiber/~4/D_F7MWpLCNk" height="1" width="1"/&gt;</description>
      <dc:creator>Nate  Klaiber</dc:creator>
      <guid isPermaLink="false">http://nateklaiber.com/tumblelog/2008/12/9/d-i-how-to-build-a-gantt-chart-with-the-google-charts-api</guid>
      <pubDate>Tue Dec 09 11:39:00 UTC 2008</pubDate>
    <feedburner:origLink>http://nateklaiber.com/tumblelog/2008/12/9/d-i-how-to-build-a-gantt-chart-with-the-google-charts-api</feedburner:origLink></item>
    <item>
      <title>Luke W: Signaling Flexible Inputs</title>
      <link>http://feedproxy.google.com/~r/nateklaiber/~3/1C--hDDzZR0/luke-w-signaling-flexible-inputs</link>
      <description>&lt;blockquote&gt;&lt;p&gt;[...] For instance, there are basically five different ways a valid phone number could be specified in the United States. A simple script can check to see if one of these has been used and then submit the information in whatever format the back-end system requires. The chore of adhering to a specific format is taken off the person providing an answer and instead given to a small bit of code. &lt;cite&gt;&lt;a href="http://www.lukew.com/ff/entry.asp?755"&gt;via&lt;/a&gt;&lt;/cite&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;img src="http://feeds.feedburner.com/~r/nateklaiber/~4/1C--hDDzZR0" height="1" width="1"/&gt;</description>
      <dc:creator>Nate  Klaiber</dc:creator>
      <guid isPermaLink="false">http://nateklaiber.com/tumblelog/2008/12/9/luke-w-signaling-flexible-inputs</guid>
      <pubDate>Tue Dec 09 08:45:00 UTC 2008</pubDate>
    <feedburner:origLink>http://nateklaiber.com/tumblelog/2008/12/9/luke-w-signaling-flexible-inputs</feedburner:origLink></item>
    <item>
      <title>Seth Godin: The internet is almost full</title>
      <link>http://feedproxy.google.com/~r/nateklaiber/~3/gZwuuuNgd74/seth-godin-the-internet-is-almost-full</link>
      <description>&lt;blockquote&gt;&lt;p&gt;Nothing can grow forever, and exponential growth is always short lived. We're running out of disk space, so if you have something left to say, better hurry. Once it's full, it's full. &lt;cite&gt;&lt;a href="http://sethgodin.typepad.com/seths_blog/2008/12/warning-the-int.html"&gt;via&lt;/a&gt;&lt;/cite&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;img src="http://feeds.feedburner.com/~r/nateklaiber/~4/gZwuuuNgd74" height="1" width="1"/&gt;</description>
      <dc:creator>Nate  Klaiber</dc:creator>
      <guid isPermaLink="false">http://nateklaiber.com/tumblelog/2008/12/9/seth-godin-the-internet-is-almost-full</guid>
      <pubDate>Tue Dec 09 08:44:00 UTC 2008</pubDate>
    <feedburner:origLink>http://nateklaiber.com/tumblelog/2008/12/9/seth-godin-the-internet-is-almost-full</feedburner:origLink></item>
    <item>
      <title>Introducing the new Nate Klaiber Book Reviews</title>
      <link>http://feedproxy.google.com/~r/nateklaiber/~3/DJR6EHgwNsY/introducing-the-new-nate-klaiber-book-reviews</link>
      <description>&lt;div style="width: 621px; border: 2px solid #666; background-color: #ccc; padding: 2px; margin-bottom: 12px;" class="photo-caption"&gt;&lt;img style="display: block;" src="http://nateklaiber.com/site_files/0005/0310/nkreviews_large.jpg" alt="Nate Klaiber Book Reviews"&gt;&lt;em style="font-style: none; margin-left: 4px;font-size: 9px;  color: #000;"&gt;Stamp given to me as a gift from my wife on Christmas, 2007&lt;/em&gt;&lt;/div&gt;
&lt;p&gt;I have decided to soft launch my new book reviews website, &lt;a href="http://www.nkbookreviews.com" title="Nate Klaiber Book Reviews"&gt;Nate Klaiber Book Reviews&lt;/a&gt;. This website has been tucked away for the past year, while I dedicated my working hours to &lt;a href="http://www.reflectyoursite.com"&gt;Reflect CMS&lt;/a&gt;. A great big thank you to &lt;a href="http://www.aboeving.com"&gt;Aaron Boeving&lt;/a&gt; for helping me take this website from idea to reality. He was the designer of the interface. There are some things still rough around the edges, but I forced myself to get it out into the wild. Now that it's up, I will be taking feedback and making iterations.&lt;/p&gt;
&lt;p&gt;While this past year kept me busy with work, I didn't stop reading books. I have a queue of reviews lined up and will be releasing them over the next few weeks. A lot of great books, authors and reviews will be making their way to the site. If you are an author and would like to update any bio information, feel free to &lt;a href="http://www.nkbookreviews.com/contact"&gt;contact me&lt;/a&gt; and I will get it updated. Thanks to those authors who have already given me some updated bios and pictures.&lt;/p&gt;
&lt;h3&gt;My Goals&lt;/h3&gt;
&lt;p&gt;My goal with this site was simple: &lt;strong&gt;To have an online storage of my personal library and reviews&lt;/strong&gt;. It all started with blog posts, but they simply weren't contextual enough to let me create the proper data models for books, authors, publisher, and reviews. Also, behind the scenes is an administration panel that lets me do some fun things:&lt;/p&gt;
&lt;ul style="list-style-type: square;"&gt;
	&lt;li&gt;&lt;strong&gt;A customizable sitemap&lt;/strong&gt;. This is automatically generated in the application via observers, but I also have the flexibility to add other static pages or alter any information as I see fit. This generates the sitemap.xml file used by all major search engines. It's less work for me, but gives me the freedom and flexibility to adjust things such as title, description, and tags on the fly. Search engine friendly URL's are automatically generated to my liking in each section. I have a robots exclusions setup to eventually block potential duplicate content pages. SEO benefits baked in.&lt;/li&gt;
	&lt;li&gt;&lt;strong&gt;Taxonomy baked in&lt;/strong&gt;. There are categories and tags stored with every piece of content. These will eventually make their way into the interface, when I find out how I want to use them in a proper manner. In the meantime, they will help serve the search index that will arrive within the week.&lt;/li&gt;
	&lt;li&gt;I can keep some &lt;strong&gt;fun stats for my personal knowledge&lt;/strong&gt;. I know how many pages I have read, how many I have to read, and where I am within each book. This was something I was happy to see inside of &lt;a href="http://readernaut.com/nateklaiber"&gt;Readernaut&lt;/a&gt;. I can also &lt;em&gt;check out&lt;/em&gt; books to friends, and keep track of who has what book.&lt;/li&gt;
	&lt;li&gt;&lt;strong&gt;Integration with other web services&lt;/strong&gt;. Shortly around the bend, I will be integrating some of my Flickr photos to their attached reviews thanks to machine-tagging. I will also be adding calls to action to purchase from Amazon, and work closely with their API to help people purchase books when they want to. I will also be integrating with Twitter as a pseudo-RSS feed for those interested in following. Not only will I integrate with other services, but there will be a public API available for the site as it stands now. It was built with &lt;abbr title="Representational State Transfer"&gt;REST&lt;/abbr&gt; in mind.&lt;/li&gt;
	&lt;li&gt;The ability to &lt;strong&gt;filter books based on their intended audiences&lt;/strong&gt;. These come directly from the publishers, and can be found on most of the books. This allows you to find books based on your level of experience. More will come with this.&lt;/li&gt;
	&lt;li&gt;There will be several RSS options. While many of you have said you enjoy the lengthy reviews, I will also have cliff notes versions available on all of the reviews and feeds. More to come on these options.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Stay tuned for some more updates on this progress. I will be keeping this site as a tumblelog of things going on in the industry, so if you want to subscribe to only book reviews, be sure to update your feeds with the new RSS feed at NK Book Reviews: &lt;a href="http://www.nkbookreviews.com/reviews/rss"&gt;http://www.nkbookreviews.com/reviews/rss&lt;/a&gt;. If you would prefer to follow me on twitter, you can follow &lt;a href="http://www.twitter.com/nkbookreviews"&gt;@nkbookreviews&lt;/a&gt; and it will notify you of recent reviews!&lt;/p&gt;
&lt;h3&gt;Transitions&lt;/h3&gt;
&lt;p&gt;Launching this site is also part of another transition. In September I left my role as Marketing Director with &lt;a href="http://www.clearfunction.com"&gt;Clear Function&lt;/a&gt;. I simply couldn't stand Aaron Boeving any longer. OK, that last part isn't true. The timing was right for me to do something I had been wanting to do for a while, which is start my own business. It also let Stephen and Aaron restructure some of their plans with Clear Function. It was a good thing for all parties involved, and I still consider them to be incredible friends and colleagues.&lt;/p&gt;
&lt;p&gt;With that transition taking place, I received some guidance from some excellent friends and colleagues and started &lt;strong&gt;The Klaibers Web Engineering, LLC&lt;/strong&gt;. I connected with a local agency, &lt;a href="http://www.wris.com" title="Western Reserve Internet Services"&gt;WRIS&lt;/a&gt;, and began taking on some different projects with them. My role with them as a &lt;em&gt;Strategic Partner&lt;/em&gt; is great, and they have a talented team working behind the scenes there. Their new website is just around the corner. With this new venture, I have revived the old domain of &lt;a href="http://www.theklaibers.com"&gt;www.theklaibers.com&lt;/a&gt;. This will be getting a new makeover after the first of the year.&lt;/p&gt;
&lt;p&gt;A very special thank you to many different friends and family during this transition time: &lt;a href="http://kands.reflectsite.com/"&gt;Stephen Rainey&lt;/a&gt;, &lt;a href="http://www.aboeving.com"&gt;Aaron Boeving&lt;/a&gt;, &lt;a href="http://scribblewerks.com"&gt;Scott Meier&lt;/a&gt;, &lt;a href="http://fuzendesign.com/"&gt;Hector Cabarcas&lt;/a&gt;, &lt;a href="http://bradcolbow.com"&gt;Brad Colbow&lt;/a&gt;, &lt;a href="http://minchdesign.com"&gt;Craig Minch&lt;/a&gt;, &lt;a href="http://www.braddielman.com"&gt;Brad Dielman&lt;/a&gt;, &lt;a href="http://shallowthoughts.org/"&gt;Bridget Stewart&lt;/a&gt;, &lt;a href="http://resistmedia.net/blog/"&gt;Beth Dean&lt;/a&gt;, &lt;a href="http://www.designinginteractive.com"&gt;Josh Walsh&lt;/a&gt;, &lt;a href="http://www.faithfulgeek.org"&gt;Joe Fiorini&lt;/a&gt;, &lt;a href="http://brendancullen.com"&gt;Brendan Cullen&lt;/a&gt;, &lt;a href="http://www.theinbetween.org/"&gt;Matt Becker&lt;/a&gt;, John MacAdam, Patrick Gerber, Eric Wiley, &lt;a href="http://www.sprokets.net"&gt;Vince Frantz&lt;/a&gt;, and a handful of other people. This also includes my own family, &lt;strong&gt;especially my wife&lt;/strong&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/nateklaiber/~4/DJR6EHgwNsY" height="1" width="1"/&gt;</description>
      <dc:creator>Nate  Klaiber</dc:creator>
      <guid isPermaLink="false">http://nateklaiber.com/blog/2008/12/4/introducing-the-new-nate-klaiber-book-reviews</guid>
      <pubDate>Thu Dec 04 18:05:01 UTC 2008</pubDate>
    <feedburner:origLink>http://nateklaiber.com/blog/2008/12/4/introducing-the-new-nate-klaiber-book-reviews</feedburner:origLink></item>
    <item>
      <title>Seth Godin: The you show</title>
      <link>http://feedproxy.google.com/~r/nateklaiber/~3/Dedwzk4fOAU/seth-godin-the-you-show</link>
      <description>&lt;blockquote&gt;&lt;p&gt;When you go to Las Vegas, Penn and Teller don't ask you what sort of lights you want, what tricks you want to see and how long the show should be. They put on their show. If you don't like it, that's fine. Plenty of other people do. As a result, they win. They get to do their work, their way. And they profit from their confidence.&lt;/p&gt;

&lt;p&gt;Some bosses don't want to hire people who have a vision, a personality and a shtick. That's okay. You don't want to work for them anyway. &lt;cite&gt;&lt;a href="http://sethgodin.typepad.com/seths_blog/2008/11/the-you-show.html"&gt;via&lt;/a&gt;&lt;/cite&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;img src="http://feeds.feedburner.com/~r/nateklaiber/~4/Dedwzk4fOAU" height="1" width="1"/&gt;</description>
      <dc:creator>Nate  Klaiber</dc:creator>
      <guid isPermaLink="false">http://nateklaiber.com/tumblelog/2008/11/25/seth-godin-the-you-show</guid>
      <pubDate>Tue Nov 25 07:23:00 UTC 2008</pubDate>
    <feedburner:origLink>http://nateklaiber.com/tumblelog/2008/11/25/seth-godin-the-you-show</feedburner:origLink></item>
    <item>
      <title>Seth Godin: You will be misunderstood</title>
      <link>http://feedproxy.google.com/~r/nateklaiber/~3/O64VMPhtey8/seth-godin-you-will-be-misunderstood</link>
      <description>&lt;blockquote&gt;&lt;p&gt;If you've got 140 characters to make your point, the odds are you are going to be misunderstood (a lot). There may be nothing wrong with that, but you should be prepared for it to happen. And most of the time, people won't take the time to ask. They'll just assume you're an ignorant jerk and move on. &lt;cite&gt;&lt;a href="http://sethgodin.typepad.com/seths_blog/2008/11/misunderstood.html"&gt;via&lt;/a&gt;&lt;/cite&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;img src="http://feeds.feedburner.com/~r/nateklaiber/~4/O64VMPhtey8" height="1" width="1"/&gt;</description>
      <dc:creator>Nate  Klaiber</dc:creator>
      <guid isPermaLink="false">http://nateklaiber.com/tumblelog/2008/11/24/seth-godin-you-will-be-misunderstood</guid>
      <pubDate>Mon Nov 24 07:18:00 UTC 2008</pubDate>
    <feedburner:origLink>http://nateklaiber.com/tumblelog/2008/11/24/seth-godin-you-will-be-misunderstood</feedburner:origLink></item>
    <item>
      <title>Myth 5: Rails is hard because of Ruby</title>
      <link>http://feedproxy.google.com/~r/nateklaiber/~3/0kg9M0jJZBw/myth-5-rails-is-hard-because-of-ruby</link>
      <description>&lt;blockquote&gt;&lt;p&gt;I've talked to lots of PHP and Java programmers who love the idea and concept of Rails, but are afraid of stepping in because of Ruby. The argument goes that since they already know PHP or Java, that it would be less work to just pick one of the Rails knockoffs in those languages. I really don't think so. &lt;cite&gt;&lt;a href="http://www.loudthinking.com/posts/34-myth-5-rails-is-hard-because-of-ruby"&gt;via&lt;/a&gt;&lt;/cite&gt;&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Having come from PHP and then jump straight into Ruby, I found the transition a breath of fresh air. Ruby is what makes me enjoy Rails. The beauty of the language makes it fun to program.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/nateklaiber/~4/0kg9M0jJZBw" height="1" width="1"/&gt;</description>
      <dc:creator>Nate  Klaiber</dc:creator>
      <guid isPermaLink="false">http://nateklaiber.com/tumblelog/2008/11/17/myth-5-rails-is-hard-because-of-ruby</guid>
      <pubDate>Mon Nov 17 09:25:00 UTC 2008</pubDate>
    <feedburner:origLink>http://nateklaiber.com/tumblelog/2008/11/17/myth-5-rails-is-hard-because-of-ruby</feedburner:origLink></item>
    <item>
      <title>Chad Fowler: Writing APIs to wrap APIs</title>
      <link>http://feedproxy.google.com/~r/nateklaiber/~3/c9X7GFmMDb0/chad-fowler-writing-apis-to-wrap-apis</link>
      <description>&lt;p&gt;In response to the question &lt;strong&gt;Why write concrete wrapper code?&lt;/strong&gt;, Chad Fowler states:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;It may seem like a nitpick, but as a Ruby programmer I want to use APIs that look like Ruby code. “fbsession.users_getInfo()” looks like PHP code to my eyes. It’s no surprise. Facebook is written in PHP, and its HTTP/XML API was designed by the same PHP programmers that created Facebook. Wrapping the Facebook API allows me to isolate and hide the PHP idioms, such that the code I use reads like “normal” Ruby code. You could argue that this is not a technical issue, and you’d be right. But I believe in the power of both consonance and dissonance in software development. Dissonant code stands out and alerts the reader that something strange and exceptional is taking place. Sometimes that strange and exceptional thing is just bad code. Sometimes it’s an unusual technique that should be highlighted. &lt;cite&gt;&lt;a href=""&gt;via&lt;/a&gt;&lt;/cite&gt;&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Having written wrappers around APIs for Flickr, Vimeo, Twitter, and Upcoming - I couldn't agree more with his statements. I have seen Ruby Flickr API libraries that look just like the PHP. It's one large library, with methods like &lt;code&gt;photo_getTags()&lt;/code&gt;. I would much rather write a concrete wrapper that allows my Ruby to look and function like the Ruby I love. I would rather write something like &lt;code&gt;@photo.tags&lt;/code&gt;, and incorporate my helper methods such as &lt;code&gt;@photo.tags?&lt;/code&gt; and &lt;code&gt;@photo.tags_count&lt;/code&gt;. It makes this much more elegant and easier to deal with, and with enough thought into the design, still allows you to be agile with the calls taking place underneath.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/nateklaiber/~4/c9X7GFmMDb0" height="1" width="1"/&gt;</description>
      <dc:creator>Nate  Klaiber</dc:creator>
      <guid isPermaLink="false">http://nateklaiber.com/tumblelog/2008/11/13/chad-fowler-writing-apis-to-wrap-apis</guid>
      <pubDate>Thu Nov 13 11:02:00 UTC 2008</pubDate>
    <feedburner:origLink>http://nateklaiber.com/tumblelog/2008/11/13/chad-fowler-writing-apis-to-wrap-apis</feedburner:origLink></item>
    <item>
      <title>Myth 1: Rails is hard to deploy</title>
      <link>http://feedproxy.google.com/~r/nateklaiber/~3/0woqKwMk3nI/myth-1-rails-is-hard-to-deploy</link>
      <description>&lt;blockquote&gt;&lt;p&gt;So while there are still reasons to run your own custom multi-tier setup of manually configured pieces, just like there are people shying away from mod_php for their particulars, I think we've finally settled on a default answer. Something that doesn't require you to really think about the first deployment of your Rails application. Something that just works out of the box. Even if that box is a shared host!&lt;/p&gt;

&lt;p&gt;In conclusion, Rails is no longer hard to deploy. Phusion Passenger has made it ridiculously easy. &lt;cite&gt;&lt;a href="http://www.loudthinking.com/posts/30-myth-1-rails-is-hard-to-deploy"&gt;via&lt;/a&gt;&lt;/cite&gt;&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;I recently setup Phusion Passenger on my development machine and absolutely love it. Integrated with the PHP work I do with virtual hosts, now I no longer need to run several different webservers.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/nateklaiber/~4/0woqKwMk3nI" height="1" width="1"/&gt;</description>
      <dc:creator>Nate  Klaiber</dc:creator>
      <guid isPermaLink="false">http://nateklaiber.com/tumblelog/2008/11/13/myth-1-rails-is-hard-to-deploy</guid>
      <pubDate>Thu Nov 13 07:54:00 UTC 2008</pubDate>
    <feedburner:origLink>http://nateklaiber.com/tumblelog/2008/11/13/myth-1-rails-is-hard-to-deploy</feedburner:origLink></item>
  </channel>
</rss>
