<?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: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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>The Technician</title>
	
	<link>http://chr.ishenry.com</link>
	<description />
	<lastBuildDate>Mon, 16 Aug 2010 22:19:41 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/ishenry/LWXM" /><feedburner:info uri="ishenry/lwxm" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>Gmail actually gets something really wrong.</title>
		<link>http://feedproxy.google.com/~r/ishenry/LWXM/~3/VYvfKPw9Y44/</link>
		<comments>http://chr.ishenry.com/2010/08/16/gmail-actually-gets-something-really-wrong/#comments</comments>
		<pubDate>Mon, 16 Aug 2010 22:19:41 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Horror Stories]]></category>

		<guid isPermaLink="false">http://chr.ishenry.com/?p=350</guid>
		<description>I&amp;#8217;m a huge fan of Gmail and Google Apps for many reasons.  I love the new redesign, and how they&amp;#8217;re finally promoting consistency across their major webapps.  It makes me feel like the web could really be a viable alternative alternative to desktop software.  I can even deal with slowness in Gmail, [...]&lt;img src="http://feeds.feedburner.com/~r/ishenry/LWXM/~4/VYvfKPw9Y44" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://chr.ishenry.com/2010/08/16/gmail-actually-gets-something-really-wrong/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://chr.ishenry.com/2010/08/16/gmail-actually-gets-something-really-wrong/</feedburner:origLink></item>
		<item>
		<title>MySQL and Linux swappiness</title>
		<link>http://feedproxy.google.com/~r/ishenry/LWXM/~3/0w4JDy9RDkI/</link>
		<comments>http://chr.ishenry.com/2010/07/29/mysql-and-linux-swappiness/#comments</comments>
		<pubDate>Fri, 30 Jul 2010 04:29:27 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[MySQL]]></category>

		<guid isPermaLink="false">http://chr.ishenry.com/?p=340</guid>
		<description>MySQL&amp;#8217;s InnoDB engine is really great.  Row-level locking is amazing in tables where there is heavy concurrency.  Write buffering is also awesome for cases where a table needs to accept a lot of data.  InnoDB&amp;#8217;s use of memory to store indexes or sometimes the entire table can also make reads incredibly fast, [...]&lt;img src="http://feeds.feedburner.com/~r/ishenry/LWXM/~4/0w4JDy9RDkI" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://chr.ishenry.com/2010/07/29/mysql-and-linux-swappiness/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://chr.ishenry.com/2010/07/29/mysql-and-linux-swappiness/</feedburner:origLink></item>
		<item>
		<title>Out of the Terminal</title>
		<link>http://feedproxy.google.com/~r/ishenry/LWXM/~3/nXMKSF60TZs/</link>
		<comments>http://chr.ishenry.com/2010/07/20/out-of-the-terminal/#comments</comments>
		<pubDate>Wed, 21 Jul 2010 05:08:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Web Architecture]]></category>

		<guid isPermaLink="false">http://chr.ishenry.com/?p=331</guid>
		<description>Every once and a while I get to leave server-land and get to do some fun projects that involve doing something on the front end.  The latest was building an embed script for the Behance Job List.  Projects like this, that get me out of the terminal and into a space that requires [...]&lt;img src="http://feeds.feedburner.com/~r/ishenry/LWXM/~4/nXMKSF60TZs" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://chr.ishenry.com/2010/07/20/out-of-the-terminal/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://chr.ishenry.com/2010/07/20/out-of-the-terminal/</feedburner:origLink></item>
		<item>
		<title>Accountability is a Feedback Loop</title>
		<link>http://feedproxy.google.com/~r/ishenry/LWXM/~3/lwO12pE8uJ0/</link>
		<comments>http://chr.ishenry.com/2010/06/22/accountability-is-a-feedback-loop/#comments</comments>
		<pubDate>Wed, 23 Jun 2010 05:28:10 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Process]]></category>

		<guid isPermaLink="false">http://chr.ishenry.com/?p=293</guid>
		<description>Accountability is a word that&amp;#8217;s getting tossed around a lot lately. You hear people saying things like:
 &amp;#8211; That developer should be held accountable for the validation problems.
 &amp;#8211; The tester should be accountable for not finding that bug.
 &amp;#8211; BP needs to be accountable for destroying an ecosystem.
The term seems to be thrown around [...]&lt;img src="http://feeds.feedburner.com/~r/ishenry/LWXM/~4/lwO12pE8uJ0" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://chr.ishenry.com/2010/06/22/accountability-is-a-feedback-loop/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://chr.ishenry.com/2010/06/22/accountability-is-a-feedback-loop/</feedburner:origLink></item>
		<item>
		<title>I’ll buy time any day.</title>
		<link>http://feedproxy.google.com/~r/ishenry/LWXM/~3/3z8IjN6DUiw/</link>
		<comments>http://chr.ishenry.com/2010/06/15/ill-buy-time-any-day/#comments</comments>
		<pubDate>Wed, 16 Jun 2010 06:11:07 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Web Dev Teams]]></category>

		<guid isPermaLink="false">http://chr.ishenry.com/?p=277</guid>
		<description>Many people value money as the most important thing in life, and will gladly trade time for it.  The pursuit of saving money is an extremely American one.  People will spend time in line for free stuff, just because it&amp;#8217;s free.  Motorists getting tickets will spend days in court, just to avoid [...]&lt;img src="http://feeds.feedburner.com/~r/ishenry/LWXM/~4/3z8IjN6DUiw" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://chr.ishenry.com/2010/06/15/ill-buy-time-any-day/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://chr.ishenry.com/2010/06/15/ill-buy-time-any-day/</feedburner:origLink></item>
		<item>
		<title>Death of the CTR</title>
		<link>http://feedproxy.google.com/~r/ishenry/LWXM/~3/k3Er2rA6Ato/</link>
		<comments>http://chr.ishenry.com/2010/05/31/death-of-the-ctr/#comments</comments>
		<pubDate>Tue, 01 Jun 2010 00:13:28 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Advertising]]></category>
		<category><![CDATA[Mobile]]></category>

		<guid isPermaLink="false">http://chr.ishenry.com/?p=285</guid>
		<description>Since the dawn of online advertising, the gold standard of effectiveness has been the CTR.  This has made a lot of sense, since for the first time ever, adertisers could leverage technology to figure out exactly how well they were communicating.  A user would click, and that click would be recorded.  The [...]&lt;img src="http://feeds.feedburner.com/~r/ishenry/LWXM/~4/k3Er2rA6Ato" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://chr.ishenry.com/2010/05/31/death-of-the-ctr/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://chr.ishenry.com/2010/05/31/death-of-the-ctr/</feedburner:origLink></item>
		<item>
		<title>MySQL Slave Delay and Maatkit</title>
		<link>http://feedproxy.google.com/~r/ishenry/LWXM/~3/ashil5tkbvc/</link>
		<comments>http://chr.ishenry.com/2010/05/02/mysql-slave-delay-and-maatkit/#comments</comments>
		<pubDate>Mon, 03 May 2010 04:11:07 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[MySQL]]></category>

		<guid isPermaLink="false">http://chr.ishenry.com/?p=279</guid>
		<description>This post could alternately be titled: &amp;#8216;How to make developers hate you.&amp;#8217;
A very common criticism of MySQL is that there is no support for delayed replication.  Delaying data flowing from master to slave can be very useful in certain cases.  For example, running a co-located slave for backups is still susceptible to data [...]&lt;img src="http://feeds.feedburner.com/~r/ishenry/LWXM/~4/ashil5tkbvc" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://chr.ishenry.com/2010/05/02/mysql-slave-delay-and-maatkit/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://chr.ishenry.com/2010/05/02/mysql-slave-delay-and-maatkit/</feedburner:origLink></item>
		<item>
		<title>MySQL skip-name-resolve</title>
		<link>http://feedproxy.google.com/~r/ishenry/LWXM/~3/hrPB0wpKAjw/</link>
		<comments>http://chr.ishenry.com/2010/04/02/mysql-skip-name-resolve/#comments</comments>
		<pubDate>Sat, 03 Apr 2010 02:03:02 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[MySQL]]></category>

		<guid isPermaLink="false">http://chr.ishenry.com/?p=278</guid>
		<description>Small, obscure optimizations sometimes have the potential to make the greatest impact.  For example, every time a connection is made, MySQL will do a DNS lookup of the host that is trying to connect.  If MySQL is handling many connections, the overhead of an extra DNS lookup can be hefty, simply because of [...]&lt;img src="http://feeds.feedburner.com/~r/ishenry/LWXM/~4/hrPB0wpKAjw" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://chr.ishenry.com/2010/04/02/mysql-skip-name-resolve/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://chr.ishenry.com/2010/04/02/mysql-skip-name-resolve/</feedburner:origLink></item>
		<item>
		<title>Sandboxes</title>
		<link>http://feedproxy.google.com/~r/ishenry/LWXM/~3/MSz8uEdtdbQ/</link>
		<comments>http://chr.ishenry.com/2010/02/22/sandboxes/#comments</comments>
		<pubDate>Tue, 23 Feb 2010 04:20:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Systems Administration]]></category>

		<guid isPermaLink="false">http://chr.ishenry.com/?p=253</guid>
		<description>Setting up a sandbox environment has normally been a trivial task.  Set up a vhost, get a copy of the database, build out the app, and start doing stuff.  When &amp;#8216;Stuff&amp;#8217; is &amp;#8216;Done&amp;#8217; push the changes onto production, and bask in your own crapulence.  That is, until your data set exceeds the [...]&lt;img src="http://feeds.feedburner.com/~r/ishenry/LWXM/~4/MSz8uEdtdbQ" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://chr.ishenry.com/2010/02/22/sandboxes/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://chr.ishenry.com/2010/02/22/sandboxes/</feedburner:origLink></item>
		<item>
		<title>Japanese Inspection</title>
		<link>http://feedproxy.google.com/~r/ishenry/LWXM/~3/-PU-ylX-q0k/</link>
		<comments>http://chr.ishenry.com/2010/02/11/japanese-inspection/#comments</comments>
		<pubDate>Fri, 12 Feb 2010 06:04:20 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Web Dev Teams]]></category>

		<guid isPermaLink="false">http://chr.ishenry.com/?p=257</guid>
		<description>Everybody procrastinates.  Some tasks that get pushed off don&amp;#8217;t matter, it just gets done later.  Some tasks that go over deadline result in profanities and bloody noses. But every once in a while, tasks come along that have an expiration date.  As in, if it doesn&amp;#8217;t get done by a certain time, [...]&lt;img src="http://feeds.feedburner.com/~r/ishenry/LWXM/~4/-PU-ylX-q0k" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://chr.ishenry.com/2010/02/11/japanese-inspection/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://chr.ishenry.com/2010/02/11/japanese-inspection/</feedburner:origLink></item>
	</channel>
</rss><!-- Dynamic page generated in 0.276 seconds. --><!-- Cached page generated by WP-Super-Cache on 2010-08-31 21:05:15 -->
