<?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: What would you like your software developers to learn?</title>
	<atom:link href="http://blog.gdinwiddie.com/2008/04/03/what-would-you-like-your-software-developers-to-learn/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.gdinwiddie.com/2008/04/03/what-would-you-like-your-software-developers-to-learn/</link>
	<description>Effective software development</description>
	<lastBuildDate>Mon, 08 Mar 2010 16:47:05 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ben</title>
		<link>http://blog.gdinwiddie.com/2008/04/03/what-would-you-like-your-software-developers-to-learn/comment-page-1/#comment-45818</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Tue, 19 Aug 2008 03:12:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gdinwiddie.com/2008/04/03/what-would-you-like-your-software-developers-to-learn/#comment-45818</guid>
		<description>I want the people I manage to get from what the customer thinks they want to what they need and can use.

I do this by getting them to put something into the customers hands as fast as possible, no matter how simple, and iterating from there. I get them to focus on workflow improvements rather then adding shiny things!</description>
		<content:encoded><![CDATA[<p>I want the people I manage to get from what the customer thinks they want to what they need and can use.</p>
<p>I do this by getting them to put something into the customers hands as fast as possible, no matter how simple, and iterating from there. I get them to focus on workflow improvements rather then adding shiny things!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Dinwiddie</title>
		<link>http://blog.gdinwiddie.com/2008/04/03/what-would-you-like-your-software-developers-to-learn/comment-page-1/#comment-28194</link>
		<dc:creator>George Dinwiddie</dc:creator>
		<pubDate>Sat, 05 Apr 2008 03:00:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gdinwiddie.com/2008/04/03/what-would-you-like-your-software-developers-to-learn/#comment-28194</guid>
		<description>Zeb, Tim,

What about the followup questions?</description>
		<content:encoded><![CDATA[<p>Zeb, Tim,</p>
<p>What about the followup questions?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Walker</title>
		<link>http://blog.gdinwiddie.com/2008/04/03/what-would-you-like-your-software-developers-to-learn/comment-page-1/#comment-28184</link>
		<dc:creator>Tim Walker</dc:creator>
		<pubDate>Fri, 04 Apr 2008 23:52:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gdinwiddie.com/2008/04/03/what-would-you-like-your-software-developers-to-learn/#comment-28184</guid>
		<description>Executable requirements and other agile best practices.</description>
		<content:encoded><![CDATA[<p>Executable requirements and other agile best practices.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ZebZiggle</title>
		<link>http://blog.gdinwiddie.com/2008/04/03/what-would-you-like-your-software-developers-to-learn/comment-page-1/#comment-28040</link>
		<dc:creator>ZebZiggle</dc:creator>
		<pubDate>Thu, 03 Apr 2008 22:18:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gdinwiddie.com/2008/04/03/what-would-you-like-your-software-developers-to-learn/#comment-28040</guid>
		<description>1. Learn the business. How do we make money? How do our customers make money by using our products? Why are these features important?

2. Sort of a variation of Don&#039;t Repeat Yourself (DRY) in code but Don&#039;t Do It Manually (DDIM) with business processes. Are you collecting metrics manually? Are you doing builds manually? Are you setting up/tearing down manually? 

Automate it and never do it again.

3. Don&#039;t get attracted to shiny objects. It&#039;s easy to go down a technical rabbit hole because something is cool &amp; new. Keep focused, stay on the task at hand. When the core work is done ... go play in the woodshed.

4. Don&#039;t make broken windows. There is a business process for a reason. If you aren&#039;t contributing to making it better or maintaining it, you are making broken windows. Before long the process fails and it&#039;s chaos.</description>
		<content:encoded><![CDATA[<p>1. Learn the business. How do we make money? How do our customers make money by using our products? Why are these features important?</p>
<p>2. Sort of a variation of Don&#8217;t Repeat Yourself (DRY) in code but Don&#8217;t Do It Manually (DDIM) with business processes. Are you collecting metrics manually? Are you doing builds manually? Are you setting up/tearing down manually? </p>
<p>Automate it and never do it again.</p>
<p>3. Don&#8217;t get attracted to shiny objects. It&#8217;s easy to go down a technical rabbit hole because something is cool &amp; new. Keep focused, stay on the task at hand. When the core work is done &#8230; go play in the woodshed.</p>
<p>4. Don&#8217;t make broken windows. There is a business process for a reason. If you aren&#8217;t contributing to making it better or maintaining it, you are making broken windows. Before long the process fails and it&#8217;s chaos.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
