<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Eric Wendelin&#039;s Blog &#187; Books</title>
	<atom:link href="http://eriwen.com/category/books/feed/" rel="self" type="application/rss+xml" />
	<link>http://eriwen.com</link>
	<description>Programming productively with open-source tools</description>
	<lastBuildDate>Thu, 26 Apr 2012 18:48:47 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>Best algorithms book I ever read</title>
		<link>http://eriwen.com/books/best-algorithms-book/</link>
		<comments>http://eriwen.com/books/best-algorithms-book/#comments</comments>
		<pubDate>Wed, 23 Feb 2011 11:00:45 +0000</pubDate>
		<dc:creator>Eric Wendelin</dc:creator>
				<category><![CDATA[Books]]></category>
		<category><![CDATA[Programming]]></category>

		<guid isPermaLink="false">http://eriwen.com/?p=1272</guid>
		<description><![CDATA[<img src="http://static.eriwen.com/images/algorithm_design_manual.jpeg" alt="The Algorithm Design Manual" class="img-left" width="160" height="214"/>I took a fair amount of time looking at data structures and algorithms while I was studying for my interviews with Google, and based on informed suggestions from <a href="http://steve-yegge.blogspot.com/2008/03/get-that-job-at-google.html" title="Get that job at Google">Steve Yegge's infamous post</a>, I decided to buy <a href="http://www.amazon.com/Algorithm-Design-Manual-Steven-Skiena/dp/1849967202/ref=sr_1_1?ie=UTF8&#038;qid=1297127794&#038;sr=8-1">The Algorithm Design Manual</a> by Steven S. Skiena.

If you don't care to read my ramblings about this book, here's a summary: Buy this book if you do ANY serious programming.

<h2>What makes The Algorithm Design Manual</h2>
2 main reasons I make this blatantly positive assessment: 
<ol><li>The first several chapters are dedicated to the basics of data structures and common problems involving algorithms. This is obviously not a unique feature, but what is unique are the "war stories" from actual field work. The stories include <strong>discussion about the failure cases</strong> and how Skiena went about solving problems he encountered. This alone is enough to make this book worthwhile.</li>
<li>Chapters 11-18 are a giant catalogue of algorithmic problems. Again, not a unique trait. However, not only does Skiena describe the basic approaches to solving each type of problem, he <strong>includes links to different implementations of in-the-field optimized solutions</strong>. He also brings up questions you should ask yourself when choosing an implementation.</li></ol>
 <a href="http://eriwen.com/books/best-algorithms-book/">Continue reading <span class="meta-nav">&#8594;</span></a>


Related posts:<ol><li><a href='http://eriwen.com/java/how-not-to-pass-the-scjp-exam/' rel='bookmark' title='How not to pass the SCJP exam'>How not to pass the SCJP exam</a></li>
<li><a href='http://eriwen.com/java/scwcd-lessons/' rel='bookmark' title='Lessons learned from the SCWCD'>Lessons learned from the SCWCD</a></li>
<li><a href='http://eriwen.com/microformats/add-hcard-to-blogroll/' rel='bookmark' title='Microformats: Add hCard to your blogroll in 2 minutes flat'>Microformats: Add hCard to your blogroll in 2 minutes flat</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p><img src="http://static.eriwen.com/images/algorithm_design_manual.jpeg" alt="The Algorithm Design Manual" class="img-left" width="160" height="214"/>I took a fair amount of time looking at data structures and algorithms while I was studying for my interviews with Google, and based on informed suggestions from <a href="http://steve-yegge.blogspot.com/2008/03/get-that-job-at-google.html" title="Get that job at Google">Steve Yegge&#8217;s infamous post</a>, I decided to buy <a href="http://www.amazon.com/Algorithm-Design-Manual-Steven-Skiena/dp/1849967202/ref=sr_1_1?ie=UTF8&#038;qid=1297127794&#038;sr=8-1">The Algorithm Design Manual</a> by Steven S. Skiena.</p>
<p>If you don&#8217;t care to read my ramblings about this book, here&#8217;s a summary: Buy this book if you do ANY serious programming.</p>
<h2>What makes The Algorithm Design Manual</h2>
<p>2 main reasons I make this blatantly positive assessment: </p>
<ol>
<li>The first several chapters are dedicated to the basics of data structures and common problems involving algorithms. This is obviously not a unique feature, but what is unique are the &#8220;war stories&#8221; from actual field work. The stories include <strong>discussion about the failure cases</strong> and how Skiena went about solving problems he encountered. This alone is enough to make this book worthwhile.</li>
<li>Chapters 11-18 are a giant catalogue of algorithmic problems. Again, not a unique trait. However, not only does Skiena describe the basic approaches to solving each type of problem, he <strong>includes links to different implementations of in-the-field optimized solutions</strong>. He also brings up questions you should ask yourself when choosing an implementation.</li>
</ol>
<p>The only caveat here is that most of the examples are written in C, which can be troublesome if you don&#8217;t know or have forgotten about pointers.</p>
<h2>You should buy this book if&#8230;</h2>
<p>You have at least <strong>1 year of computer science training</strong> under your belt. If you are just writing one website in PHP for your cousin&#8217;s lemonade stand; then I don&#8217;t know why have you read this far. In that case you won&#8217;t be interested in this book. </p>
<p>Students and professionals alike will find <a href="http://www.amazon.com/Algorithm-Design-Manual-Steven-Skiena/dp/1849967202/ref=sr_1_1?ie=UTF8&#038;qid=1297127794&#038;sr=8-1">The Algorithm Design Manual</a> useful. In addition to the standard problem sets, I&#8217;ve also found the accompanying interview questions to be very interesting. </p>
<p>The only programming book that tops this is <a href="http://www.amazon.com/Pragmatic-Programmer-Journeyman-Master/dp/020161622X/ref=sr_1_1?s=books&#038;ie=UTF8&#038;qid=1298329702&#038;sr=1-1" title="The Pragmatic Programmer: From Journeyman to Master book from Amazon">The Pragmatic Programmer</a> by Andy Hunt and Dave Thomas.</p>
<p>What are some of the best Data Structures/Algorithms books you&#8217;ve found?</p>


<p>Related posts:<ol><li><a href='http://eriwen.com/java/how-not-to-pass-the-scjp-exam/' rel='bookmark' title='How not to pass the SCJP exam'>How not to pass the SCJP exam</a></li>
<li><a href='http://eriwen.com/java/scwcd-lessons/' rel='bookmark' title='Lessons learned from the SCWCD'>Lessons learned from the SCWCD</a></li>
<li><a href='http://eriwen.com/microformats/add-hcard-to-blogroll/' rel='bookmark' title='Microformats: Add hCard to your blogroll in 2 minutes flat'>Microformats: Add hCard to your blogroll in 2 minutes flat</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://eriwen.com/books/best-algorithms-book/feed/</wfw:commentRss>
		<slash:comments>27</slash:comments>
		</item>
		<item>
		<title>Book Review: MooTools 1.2 Beginner&#8217;s Guide</title>
		<link>http://eriwen.com/books/mootools-1-2-beginners-guide/</link>
		<comments>http://eriwen.com/books/mootools-1-2-beginners-guide/#comments</comments>
		<pubDate>Thu, 11 Mar 2010 11:00:23 +0000</pubDate>
		<dc:creator>Eric Wendelin</dc:creator>
				<category><![CDATA[Books]]></category>

		<guid isPermaLink="false">http://eriwen.com/?p=1125</guid>
		<description><![CDATA[<img src="http://static.eriwen.com/images/mootools-beginners.png" alt="MooTools 1.2 Beginner's Guide cover" style="float: left; margin: 0 8px 8px 0; " width="100" height="123"/>I have liked the works of Jacob Gube of <a href="http://sixrevisions.com">Six Revisions</a> and <a href="http://www.garrickcheung.com">Garrick Cheung</a> of the MooTools Community Team, so when <a href="http://www.packtpub.com">Packt Publishing</a> wanted me to review their book, I accepted. 

I hope authors, as well as readers, will gain some insights. Here is my review of <a href="http://www.packtpub.com/mootools-1-2-beginners-guide/book">MooTools 1.2 Beginner's Guide</a>.
 <a href="http://eriwen.com/books/mootools-1-2-beginners-guide/">Continue reading <span class="meta-nav">&#8594;</span></a>


Related posts:<ol><li><a href='http://eriwen.com/javascript/text-size-prefs/' rel='bookmark' title='Guest Post: Save Text Size Preference Using MooTools and PHP'>Guest Post: Save Text Size Preference Using MooTools and PHP</a></li>
<li><a href='http://eriwen.com/css/color-palette-with-css-and-moo/' rel='bookmark' title='Create a Color Palette Using CSS and MooTools 1.2'>Create a Color Palette Using CSS and MooTools 1.2</a></li>
<li><a href='http://eriwen.com/java/scwcd-lessons/' rel='bookmark' title='Lessons learned from the SCWCD'>Lessons learned from the SCWCD</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p><img src="http://static.eriwen.com/images/mootools-beginners.png" alt="MooTools 1.2 Beginner's Guide cover" style="float: left; margin: 0 8px 8px 0; " width="100" height="123"/>I have liked the works of Jacob Gube of <a href="http://sixrevisions.com">Six Revisions</a> and <a href="http://www.garrickcheung.com">Garrick Cheung</a> of the MooTools Community Team, so when <a href="http://www.packtpub.com">Packt Publishing</a> wanted me to review their book, I accepted. </p>
<p>I hope authors, as well as readers, will gain some insights. Here is my review of <a href="http://www.packtpub.com/mootools-1-2-beginners-guide/book">MooTools 1.2 Beginner&#8217;s Guide</a>.</p>
<h2>Book Structure</h2>
<p>The book basically takes you, step-by-step, through downloading the <a href="http://mootools.net">MooTools library</a> parts and building simple examples with HTML, CSS, and, of course, MooTools. It seems to touch on many of major parts of MooTools: Core, DOM selection, Events, Ajax, and Fx. Finally, it introduces you to MooTools More and how to write your own MooTools plugins. it approaches everything with <strong>very simple, very &#8220;hands-on&#8221; examples</strong>. There are some deviations (like pop quizzes), but they are few.</p>
<p>The examples themselves generally introduce a topic, give an HTML/CSS template and then progressively fill in the MooTools bits.</p>
<h2>The Good</h2>
<p>You can tell that the authors are bloggers by their very informal writing style. They know how to use simple language so that their writing does not impede the learning ability of the reader. I was able to read the entire book in about <strong>3 hours cover-to-cover, a testament to how easy-to-read it is</strong>. </p>
<p>This is a book that a real, never-coded-a-web-page-before dude(tte) could pick up and do something with immediately. </p>
<h2>The Bad</h2>
<p>It truly is a <strong>beginner&#8217;s</strong> guide, and having some sort of MooTools knowledge myself I was annoyed by the verboseness of the examples. There seemed to be a lot of times I was seeing a small code example stretched out to several pages of text. </p>
<p>I was slightly disappointed by the number of linguistic (spelling and grammar) mistakes throughout the book. These were obviously not cultural differences between the UK-based Packt and the US. I was always able to understand what the writer meant, but I kept getting hung up on the mistakes because that&#8217;s the kind of asshole I am ;)</p>
<p>I really <strong>missed a good reference or appendix section</strong> at the end where I could find links to more information about the parts of MooTools I was learning about. There was some stuff within the chapter texts, but not enough.</p>
<h2>You should buy this book if&#8230;</h2>
<p>&#8230; you are truly a beginning web developer. This book is a great introduction to web development with a core focus on MooTools. It seems to generally promote good web development practices in my opinion. </p>
<p>Conversely, this book is not great to use just for reference. If you want to lookup anything advanced, it&#8217;s not going to be your best bet. </p>
<p><a href="http://www.packtpub.com/mootools-1-2-beginners-guide/book">MooTools 1.2 Beginner&#8217;s Guide &raquo;</a></p>


<p>Related posts:<ol><li><a href='http://eriwen.com/javascript/text-size-prefs/' rel='bookmark' title='Guest Post: Save Text Size Preference Using MooTools and PHP'>Guest Post: Save Text Size Preference Using MooTools and PHP</a></li>
<li><a href='http://eriwen.com/css/color-palette-with-css-and-moo/' rel='bookmark' title='Create a Color Palette Using CSS and MooTools 1.2'>Create a Color Palette Using CSS and MooTools 1.2</a></li>
<li><a href='http://eriwen.com/java/scwcd-lessons/' rel='bookmark' title='Lessons learned from the SCWCD'>Lessons learned from the SCWCD</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://eriwen.com/books/mootools-1-2-beginners-guide/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

