<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
	
	>
<channel>
	<title>
	Comments on: FRAC 2 &#8211; Part 5	</title>
	<atom:link href="https://wolfhusky.net/duncan/wp/2006/06/frac-2-part-5/feed/" rel="self" type="application/rss+xml" />
	<link>https://wolfhusky.net/duncan/wp/2006/06/frac-2-part-5/</link>
	<description>My little corner of the web</description>
	<lastBuildDate>Tue, 31 Dec 2019 22:33:52 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: mstegosaurus		</title>
		<link>https://wolfhusky.net/duncan/wp/2006/06/frac-2-part-5/#comment-4154</link>

		<dc:creator><![CDATA[mstegosaurus]]></dc:creator>
		<pubDate>Sat, 03 Jun 2006 17:24:07 +0000</pubDate>
		<guid isPermaLink="false">http://woofwoofarf.wordpress.com/2006/06/02/frac-2-part-5/#comment-4154</guid>

					<description><![CDATA[Checkpoint 10
For the record, that&#039;s totally where we lost it. 
Once we figured out we&#039;d be taking the brown line somewhere-- but before we&#039;d solved the puzzle-- I figured we should head inbound since there were more stops in that direction than the other, thus making it more likely that our next destination was that way-- by the time we realized my error and doubled back, we ended up on the same outbound train as Yuk, and that was pretty much the end of it. 
In re: the brute force solution of trying each word against eighteen possible combinations, that&#039;s not exactly how I did it-- it&#039;s more efficent to start with three letter words and figure out which ones are &quot;the&quot; or &quot;and&quot;, for example, then try to figure out other words from context and only use the grid to verify. It&#039;s sort of like doing an acrostic puzzle (which, incidentally, might be something to include next year.)
In re: hubcaps vs. wheels, it&#039;s a sonic thing-- the first word of the next line in the piece the team name is taken from is &quot;perhaps&quot;. Plus, hubcaps is an inherently funnier word.]]></description>
			<content:encoded><![CDATA[<p>Checkpoint 10<br />
For the record, that&#8217;s totally where we lost it.<br />
Once we figured out we&#8217;d be taking the brown line somewhere&#8211; but before we&#8217;d solved the puzzle&#8211; I figured we should head inbound since there were more stops in that direction than the other, thus making it more likely that our next destination was that way&#8211; by the time we realized my error and doubled back, we ended up on the same outbound train as Yuk, and that was pretty much the end of it.<br />
In re: the brute force solution of trying each word against eighteen possible combinations, that&#8217;s not exactly how I did it&#8211; it&#8217;s more efficent to start with three letter words and figure out which ones are &#8220;the&#8221; or &#8220;and&#8221;, for example, then try to figure out other words from context and only use the grid to verify. It&#8217;s sort of like doing an acrostic puzzle (which, incidentally, might be something to include next year.)<br />
In re: hubcaps vs. wheels, it&#8217;s a sonic thing&#8211; the first word of the next line in the piece the team name is taken from is &#8220;perhaps&#8221;. Plus, hubcaps is an inherently funnier word.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
