<?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: Finding a satisfying answer.</title>
	<atom:link href="http://www.globalconfig.net/2008/12/23/finding-a-satisfying-answer/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.globalconfig.net/2008/12/23/finding-a-satisfying-answer/</link>
	<description>Studying for Cisco Certifications</description>
	<lastBuildDate>Thu, 22 Jul 2010 14:31:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Ethan</title>
		<link>http://www.globalconfig.net/2008/12/23/finding-a-satisfying-answer/comment-page-1/#comment-385</link>
		<dc:creator>Ethan</dc:creator>
		<pubDate>Thu, 25 Dec 2008 13:56:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.globalconfig.net/2008/12/23/finding-a-satisfying-answer/#comment-385</guid>
		<description>If I was working with a vendor&#039;s practice lab, sometimes I&#039;d read the explanation and just go, &quot;Huh?&quot;  It wouldn&#039;t stick at all.  So I&#039;d read it again.  And again.  Then review all the code line by line as well as the &quot;show&quot; command output to verify what had happened.  If it still wasn&#039;t sinking in, I&#039;d hit the DocCD and review Cisco&#039;s take on it.  Many times, that helped, as the problem I was working through was similar to an example in a configuration guide.  But if that didn&#039;t nail it down, I&#039;d grab a CiscoPress book to get yet another viewpoint.  (Wendell Odom has a way of phrasing things that works for me.)

None of the social networks were effective for me as a technical learning tool.  Usually the problems were so esoteric,  complicated, or just plain weird that few people would know what I was talking about.  Being able to explain the problem, find someone who grasped the issue and then was willing to help rarely worked out for me.  GroupStudy was pretty pointless, although I know it works out well for some people.

I did have a little luck blogging about a problem, where a reader might make a useful comment.  But overall, I found my time best spent reading, and then reading some more.

And you know what else?  There were a few things that I just said &quot;forget it&quot;, never really got it working right, but moved on anyway.  Not core stuff, but weird stuff like frame-relay bridging or building the multicast tree over a topology invented by Satan.  It just wasn&#039;t worth the cycles to me, assuming I understood what was *supposed* to be happening, even if it wasn&#039;t working out in my specific case.</description>
		<content:encoded><![CDATA[<p>If I was working with a vendor&#8217;s practice lab, sometimes I&#8217;d read the explanation and just go, &#8220;Huh?&#8221;  It wouldn&#8217;t stick at all.  So I&#8217;d read it again.  And again.  Then review all the code line by line as well as the &#8220;show&#8221; command output to verify what had happened.  If it still wasn&#8217;t sinking in, I&#8217;d hit the DocCD and review Cisco&#8217;s take on it.  Many times, that helped, as the problem I was working through was similar to an example in a configuration guide.  But if that didn&#8217;t nail it down, I&#8217;d grab a CiscoPress book to get yet another viewpoint.  (Wendell Odom has a way of phrasing things that works for me.)</p>
<p>None of the social networks were effective for me as a technical learning tool.  Usually the problems were so esoteric,  complicated, or just plain weird that few people would know what I was talking about.  Being able to explain the problem, find someone who grasped the issue and then was willing to help rarely worked out for me.  GroupStudy was pretty pointless, although I know it works out well for some people.</p>
<p>I did have a little luck blogging about a problem, where a reader might make a useful comment.  But overall, I found my time best spent reading, and then reading some more.</p>
<p>And you know what else?  There were a few things that I just said &#8220;forget it&#8221;, never really got it working right, but moved on anyway.  Not core stuff, but weird stuff like frame-relay bridging or building the multicast tree over a topology invented by Satan.  It just wasn&#8217;t worth the cycles to me, assuming I understood what was *supposed* to be happening, even if it wasn&#8217;t working out in my specific case.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stretch</title>
		<link>http://www.globalconfig.net/2008/12/23/finding-a-satisfying-answer/comment-page-1/#comment-379</link>
		<dc:creator>stretch</dc:creator>
		<pubDate>Wed, 24 Dec 2008 09:02:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.globalconfig.net/2008/12/23/finding-a-satisfying-answer/#comment-379</guid>
		<description>I&#039;d like to add http://networking-forum.com (a vendor-neutral forum) to your list. Good people and great opportunities for discussion there.</description>
		<content:encoded><![CDATA[<p>I&#8217;d like to add <a href="http://networking-forum.com" rel="nofollow">http://networking-forum.com</a> (a vendor-neutral forum) to your list. Good people and great opportunities for discussion there.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
