<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: When to Try Something vs When to Study Something</title>
	<atom:link href="http://chrisgammell.com/2009/07/07/when-to-try-something-vs-when-to-study-something/feed/" rel="self" type="application/rss+xml" />
	<link>http://chrisgammell.com/2009/07/07/when-to-try-something-vs-when-to-study-something/</link>
	<description>Analog electronics and everything else between 1 and 0</description>
	<lastBuildDate>Wed, 28 Jul 2010 16:00:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Thank You, Steven Chu &#124; Chris Gammell's Analog Life</title>
		<link>http://chrisgammell.com/2009/07/07/when-to-try-something-vs-when-to-study-something/comment-page-1/#comment-1023</link>
		<dc:creator>Thank You, Steven Chu &#124; Chris Gammell's Analog Life</dc:creator>
		<pubDate>Thu, 23 Jul 2009 02:49:23 +0000</pubDate>
		<guid isPermaLink="false">http://chrisgammell.com/?p=903#comment-1023</guid>
		<description>[...] like it when I understand things. The universe feels like a little safer place, even if I realize feeling secure is only a state of [...]</description>
		<content:encoded><![CDATA[<p>[...] like it when I understand things. The universe feels like a little safer place, even if I realize feeling secure is only a state of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fluxor</title>
		<link>http://chrisgammell.com/2009/07/07/when-to-try-something-vs-when-to-study-something/comment-page-1/#comment-1005</link>
		<dc:creator>Fluxor</dc:creator>
		<pubDate>Wed, 08 Jul 2009 18:45:02 +0000</pubDate>
		<guid isPermaLink="false">http://chrisgammell.com/?p=903#comment-1005</guid>
		<description>Every situation is different. When I first broke into doing RF IC design, I bought a text book and read it front to back. Before then, I had no clue about RF circuits or systems. However, it&#039;s not a method I&#039;d recommend. Personally, I&#039;m a tinkerer more than a reader. Tinker first. When that fails, search papers. Rarely have I had to go back to text books unless it&#039;s to pull out the odd equation or two. They do look nice sitting on the shelf though.</description>
		<content:encoded><![CDATA[<p>Every situation is different. When I first broke into doing RF IC design, I bought a text book and read it front to back. Before then, I had no clue about RF circuits or systems. However, it&#8217;s not a method I&#8217;d recommend. Personally, I&#8217;m a tinkerer more than a reader. Tinker first. When that fails, search papers. Rarely have I had to go back to text books unless it&#8217;s to pull out the odd equation or two. They do look nice sitting on the shelf though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate</title>
		<link>http://chrisgammell.com/2009/07/07/when-to-try-something-vs-when-to-study-something/comment-page-1/#comment-1003</link>
		<dc:creator>Nate</dc:creator>
		<pubDate>Tue, 07 Jul 2009 18:23:43 +0000</pubDate>
		<guid isPermaLink="false">http://chrisgammell.com/?p=903#comment-1003</guid>
		<description>Sounds about right to me. I keep a stack of textbooks on my desk within easy reach (as I&#039;m sure most engineers do) and whenever I come to a problem I don&#039;t understand, I pull out the books and read up on it to get a handle for the basic idea. Then I look online to see if there is anything out there that&#039;s more recent than my textbook, or if anyone has had a similar problem. Then I go try some things on my own to figure it out, and if I still have trouble, then I bug a coworker. I think coworkers are an excellent resource because they understand what you work on, how it fits in with the whole project, what tools you use to get your work done, and that sort of thing. However, if you haven&#039;t done some work on your own beforehand to figure it out, they aren&#039;t very pleased, so asking for help should never be the first thing you do. After that, it becomes an issue of working with your coworkers or anyone else around that might be an expert in your problem.</description>
		<content:encoded><![CDATA[<p>Sounds about right to me. I keep a stack of textbooks on my desk within easy reach (as I&#8217;m sure most engineers do) and whenever I come to a problem I don&#8217;t understand, I pull out the books and read up on it to get a handle for the basic idea. Then I look online to see if there is anything out there that&#8217;s more recent than my textbook, or if anyone has had a similar problem. Then I go try some things on my own to figure it out, and if I still have trouble, then I bug a coworker. I think coworkers are an excellent resource because they understand what you work on, how it fits in with the whole project, what tools you use to get your work done, and that sort of thing. However, if you haven&#8217;t done some work on your own beforehand to figure it out, they aren&#8217;t very pleased, so asking for help should never be the first thing you do. After that, it becomes an issue of working with your coworkers or anyone else around that might be an expert in your problem.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
