<?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: Assumptions and Flaws: Focus on the Argument Engine</title>
	<atom:link href="http://www.manhattanlsat.com/blog/index.php/2009/10/13/assumptions-and-flaws-focus-on-the-argument-engine/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.manhattanlsat.com/blog/index.php/2009/10/13/assumptions-and-flaws-focus-on-the-argument-engine/</link>
	<description>LSAT Prep Strategies, Logic Games, and more....</description>
	<lastBuildDate>Tue, 31 Jan 2012 22:40:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Han</title>
		<link>http://www.manhattanlsat.com/blog/index.php/2009/10/13/assumptions-and-flaws-focus-on-the-argument-engine/comment-page-1/#comment-1452</link>
		<dc:creator>Han</dc:creator>
		<pubDate>Tue, 02 Mar 2010 00:12:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.atlaslsat.com/blog/?p=139#comment-1452</guid>
		<description>I really think there is a lot of value in this article. I never really thought of it in the terms expressed above, but I believe that my approach implicitly endorsed this concept. I used to actually read the conclusion of LR arguments first, and THEN read the argument. I think there were two major benefits: (1) I got really good at skimming an argument and spotting premise/conclusion markers, and (2) I would always be able to discern the relevant argument and not get sidetracked by irrelevant details (which are ripe for incorrect answers, by the way).

I did this both times I took the LSAT and it resulted in two 99th percentile scores. But this method isn&#039;t really for everyone, I must warn you, it&#039;s sort of confusing reading the conclusion first.</description>
		<content:encoded><![CDATA[<p>I really think there is a lot of value in this article. I never really thought of it in the terms expressed above, but I believe that my approach implicitly endorsed this concept. I used to actually read the conclusion of LR arguments first, and THEN read the argument. I think there were two major benefits: (1) I got really good at skimming an argument and spotting premise/conclusion markers, and (2) I would always be able to discern the relevant argument and not get sidetracked by irrelevant details (which are ripe for incorrect answers, by the way).</p>
<p>I did this both times I took the LSAT and it resulted in two 99th percentile scores. But this method isn&#8217;t really for everyone, I must warn you, it&#8217;s sort of confusing reading the conclusion first.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: noah@atlaslsat.com</title>
		<link>http://www.manhattanlsat.com/blog/index.php/2009/10/13/assumptions-and-flaws-focus-on-the-argument-engine/comment-page-1/#comment-1420</link>
		<dc:creator>noah@atlaslsat.com</dc:creator>
		<pubDate>Wed, 27 Jan 2010 23:23:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.atlaslsat.com/blog/?p=139#comment-1420</guid>
		<description>Great -- good luck and tell me how it goes.</description>
		<content:encoded><![CDATA[<p>Great &#8212; good luck and tell me how it goes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KayKay</title>
		<link>http://www.manhattanlsat.com/blog/index.php/2009/10/13/assumptions-and-flaws-focus-on-the-argument-engine/comment-page-1/#comment-1418</link>
		<dc:creator>KayKay</dc:creator>
		<pubDate>Sat, 23 Jan 2010 01:45:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.atlaslsat.com/blog/?p=139#comment-1418</guid>
		<description>Am going to try this right now and i will let you know if it works for but thanks.</description>
		<content:encoded><![CDATA[<p>Am going to try this right now and i will let you know if it works for but thanks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

