<?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: Commuting is crazy!</title>
	<atom:link href="http://embeddedgurus.com/stack-overflow/2009/04/commuting-is-crazy/feed/" rel="self" type="application/rss+xml" />
	<link>http://embeddedgurus.com/stack-overflow/2009/04/commuting-is-crazy/</link>
	<description>Thoughts on embedded systems by Nigel Jones</description>
	<lastBuildDate>Thu, 09 Feb 2012 07:32:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: JayGA</title>
		<link>http://embeddedgurus.com/stack-overflow/2009/04/commuting-is-crazy/comment-page-1/#comment-184</link>
		<dc:creator>JayGA</dc:creator>
		<pubDate>Wed, 13 May 2009 18:59:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfcdev.org/test-stack/2009/04/03/commuting-is-crazy/#comment-184</guid>
		<description>Actually, I am an engineer and work mostly from home doing embedded software development.  I&#039;ve been doing it for about 2 years now.  Unfortunately, the only way I could accomplish this was to become self-employed.  My employer didn&#039;t want their employees doing this sort of thing.  However, my former employer didn&#039;t want to lose me, so that got me under contract.  They equipped me with VPN and equipment for development.Advantages:I&#039;m getting paid hourly (so paid overtime).Very flexible schedule. I can get work done around the house and yard, and work late at night if I have too. Can really crank the work out sometimes.Disadvantages:Communication issues to the point you feel a little left behind at times.  I usually go onsite twice a week.  Being able to sit down with other engineers over a whiteboard is invaluable.Paid hourly - well, sometimes it&#039;s hard to get the hours in. When VPN goes down, it can be a pain.When onsite equipment goes down, you can&#039;t just reach over and reset it.</description>
		<content:encoded><![CDATA[<p>Actually, I am an engineer and work mostly from home doing embedded software development.  I&#8217;ve been doing it for about 2 years now.  Unfortunately, the only way I could accomplish this was to become self-employed.  My employer didn&#8217;t want their employees doing this sort of thing.  However, my former employer didn&#8217;t want to lose me, so that got me under contract.  They equipped me with VPN and equipment for development.Advantages:I&#8217;m getting paid hourly (so paid overtime).Very flexible schedule. I can get work done around the house and yard, and work late at night if I have too. Can really crank the work out sometimes.Disadvantages:Communication issues to the point you feel a little left behind at times.  I usually go onsite twice a week.  Being able to sit down with other engineers over a whiteboard is invaluable.Paid hourly &#8211; well, sometimes it&#8217;s hard to get the hours in. When VPN goes down, it can be a pain.When onsite equipment goes down, you can&#8217;t just reach over and reset it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nigel Jones</title>
		<link>http://embeddedgurus.com/stack-overflow/2009/04/commuting-is-crazy/comment-page-1/#comment-183</link>
		<dc:creator>Nigel Jones</dc:creator>
		<pubDate>Wed, 06 May 2009 15:31:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfcdev.org/test-stack/2009/04/03/commuting-is-crazy/#comment-183</guid>
		<description>A very well reasoned response Kyle. I especially like your &quot;I&#039;ve always tried to find opportunity in what others find distracting&quot;. However, note that I wasn&#039;t advocating that engineers work from home every day. I think 1-2 days a week would be optimal for many jobs. With this approach I think you&#039;d still get the benefits you advocate, while achieving the productivity boost I mentioned.</description>
		<content:encoded><![CDATA[<p>A very well reasoned response Kyle. I especially like your &#8220;I&#8217;ve always tried to find opportunity in what others find distracting&#8221;. However, note that I wasn&#8217;t advocating that engineers work from home every day. I think 1-2 days a week would be optimal for many jobs. With this approach I think you&#8217;d still get the benefits you advocate, while achieving the productivity boost I mentioned.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kyle</title>
		<link>http://embeddedgurus.com/stack-overflow/2009/04/commuting-is-crazy/comment-page-1/#comment-182</link>
		<dc:creator>Kyle</dc:creator>
		<pubDate>Wed, 06 May 2009 02:46:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfcdev.org/test-stack/2009/04/03/commuting-is-crazy/#comment-182</guid>
		<description>While I&#039;d like to be able to go to my own bench in the basement and crank something out when I&#039;m under pressure, I am glad it is not the norm.  I think an engineer can exert a lot of positive influence by being present in the workplace.  Most importantly, the engineer is often the voice of the customer on the factory floor.  Just keeping your eyes and ears open when you are fetching a tool can help find problems and potential improvements.  It also often falls on the engineers to make technical and non-technical employees familiar with the company&#039;s technology.  No matter how well you have documented your product, a technician will remember what you have to say when they ask you questions about it.  Finally, engineers are often in the best position to identify opportunities for a company.  An engineer may find something valuable in a vendors that may otherwise be turned away by purchasing, or from a customer that sales may not think is a good fit.  These advantages may not help you with your budget or schedule for your current project but I&#039;ve always tried to find opportunity in what others find distracting.</description>
		<content:encoded><![CDATA[<p>While I&#8217;d like to be able to go to my own bench in the basement and crank something out when I&#8217;m under pressure, I am glad it is not the norm.  I think an engineer can exert a lot of positive influence by being present in the workplace.  Most importantly, the engineer is often the voice of the customer on the factory floor.  Just keeping your eyes and ears open when you are fetching a tool can help find problems and potential improvements.  It also often falls on the engineers to make technical and non-technical employees familiar with the company&#8217;s technology.  No matter how well you have documented your product, a technician will remember what you have to say when they ask you questions about it.  Finally, engineers are often in the best position to identify opportunities for a company.  An engineer may find something valuable in a vendors that may otherwise be turned away by purchasing, or from a customer that sales may not think is a good fit.  These advantages may not help you with your budget or schedule for your current project but I&#8217;ve always tried to find opportunity in what others find distracting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GregK</title>
		<link>http://embeddedgurus.com/stack-overflow/2009/04/commuting-is-crazy/comment-page-1/#comment-181</link>
		<dc:creator>GregK</dc:creator>
		<pubDate>Sat, 04 Apr 2009 13:59:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfcdev.org/test-stack/2009/04/03/commuting-is-crazy/#comment-181</guid>
		<description>Times changes rapidly, if your manager is not from the same era is almost impossible to understand such subtle issue.Employee who realize such &#039;obvious&#039; issue after some time simply start working on its own, or like consultants or similar if only possible.</description>
		<content:encoded><![CDATA[<p>Times changes rapidly, if your manager is not from the same era is almost impossible to understand such subtle issue.Employee who realize such &#8216;obvious&#8217; issue after some time simply start working on its own, or like consultants or similar if only possible.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

