<?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 for Grant&#039;s Grunts</title>
	<atom:link href="http://www.grantingersoll.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.grantingersoll.com</link>
	<description>Thoughts on Lucene, Solr, Search, Engineering, Leadership, Money and Life</description>
	<lastBuildDate>Tue, 18 Sep 2012 18:02:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>Comment on 5 Things Every Software Engineer Should Try by Dmitry</title>
		<link>http://www.grantingersoll.com/2012/09/18/5-things-every-software-engineer-should-try/#comment-196</link>
		<dc:creator>Dmitry</dc:creator>
		<pubDate>Tue, 18 Sep 2012 18:02:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.grantingersoll.com/?p=49#comment-196</guid>
		<description><![CDATA[Really nice and inspiring post!
To share, what I believe has helped me a lot, is perhaps a slightly controversial thing: changing gigs in the beginning of my sw eng career about every two years. In my particular case there have been some extremes, like moving from digital image processing to telecom and big data. That hasn&#039;t produced super-deep knowledge in each of the particular areas, but helped understand where my passion is, what type of people I enjoy working with, and eventually, the area I&#039;m willing to contribute over a longer (more than 2y) period. Another thing that proves useful is to teach oneself to learn new things in sw dev periodically, even for fun. That can help to gain more knowledge in the area of expertise and get out of your comfort zone. More systematic way of doing this is to enroll into some publicly available course (some can be taken on the Internet for free nowadays) with programming assignments and grading. It proved to be rather rewarding learning experience.]]></description>
		<content:encoded><![CDATA[<p>Really nice and inspiring post!<br />
To share, what I believe has helped me a lot, is perhaps a slightly controversial thing: changing gigs in the beginning of my sw eng career about every two years. In my particular case there have been some extremes, like moving from digital image processing to telecom and big data. That hasn&#8217;t produced super-deep knowledge in each of the particular areas, but helped understand where my passion is, what type of people I enjoy working with, and eventually, the area I&#8217;m willing to contribute over a longer (more than 2y) period. Another thing that proves useful is to teach oneself to learn new things in sw dev periodically, even for fun. That can help to gain more knowledge in the area of expertise and get out of your comfort zone. More systematic way of doing this is to enroll into some publicly available course (some can be taken on the Internet for free nowadays) with programming assignments and grading. It proved to be rather rewarding learning experience.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
