<?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: Deadlines: On Being a Professional Software Developer</title>
	<atom:link href="http://www.softwarebyrob.com/2007/04/04/deadlines-on-being-a-professional-software-developer/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.softwarebyrob.com/2007/04/04/deadlines-on-being-a-professional-software-developer/</link>
	<description>Passionate about Startups and MicroISVs</description>
	<lastBuildDate>Tue, 07 Feb 2012 17:42:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: http://</title>
		<link>http://www.softwarebyrob.com/2007/04/04/deadlines-on-being-a-professional-software-developer/comment-page-1/#comment-444</link>
		<dc:creator>http://</dc:creator>
		<pubDate>Wed, 11 Apr 2007 05:33:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarebyrob.com/2007/04/04/deadlines-on-being-a-professional-software-developer/#comment-444</guid>
		<description>It&#039;s so easy to miss deadlines especially if the ones setting them are non-tech people, which unfortunately, in my company is the case.  Also, improper deadline estimates have a direct effect on software design and code quality.</description>
		<content:encoded><![CDATA[<p>It&#8217;s so easy to miss deadlines especially if the ones setting them are non-tech people, which unfortunately, in my company is the case.  Also, improper deadline estimates have a direct effect on software design and code quality.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.softwarebyrob.com/2007/04/04/deadlines-on-being-a-professional-software-developer/comment-page-1/#comment-443</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Sun, 08 Apr 2007 22:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarebyrob.com/2007/04/04/deadlines-on-being-a-professional-software-developer/#comment-443</guid>
		<description>Interesting, but seems like an ad hoc criteria for professionalism. Perhaps misguided deadlines are the actual culprit behind the infamous failure rates within software development project. And conversely, you might be nailing deadlines but delivering cruddy or ill-conceived product. You&#039;re raising a broad project management question that I think is a more nuanced affair.</description>
		<content:encoded><![CDATA[<p>Interesting, but seems like an ad hoc criteria for professionalism. Perhaps misguided deadlines are the actual culprit behind the infamous failure rates within software development project. And conversely, you might be nailing deadlines but delivering cruddy or ill-conceived product. You&#8217;re raising a broad project management question that I think is a more nuanced affair.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: http://</title>
		<link>http://www.softwarebyrob.com/2007/04/04/deadlines-on-being-a-professional-software-developer/comment-page-1/#comment-442</link>
		<dc:creator>http://</dc:creator>
		<pubDate>Thu, 05 Apr 2007 16:50:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarebyrob.com/2007/04/04/deadlines-on-being-a-professional-software-developer/#comment-442</guid>
		<description>Since software engineering has more to do with inventing/researching than manufactoring/production, I would argue that deadlines is a very dangerous thing to the quality of software.  Sure, we need some deliverables to keep the project going forward and avoid the student syndrome but I have seen too many hacks in the last week before a deadline to find them to be anything but unhealthy on the long term. The &quot;we can always refactor later&quot; just does not hold water, when managers gets to see any kind of output they immediately scream &quot;ship it&quot; and jump to the next version/phase in planning. So I try to provide frequent updates on my progress rather than saying &quot;done by xxx&quot;.</description>
		<content:encoded><![CDATA[<p>Since software engineering has more to do with inventing/researching than manufactoring/production, I would argue that deadlines is a very dangerous thing to the quality of software.  Sure, we need some deliverables to keep the project going forward and avoid the student syndrome but I have seen too many hacks in the last week before a deadline to find them to be anything but unhealthy on the long term. The &#8220;we can always refactor later&#8221; just does not hold water, when managers gets to see any kind of output they immediately scream &#8220;ship it&#8221; and jump to the next version/phase in planning. So I try to provide frequent updates on my progress rather than saying &#8220;done by xxx&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: http://</title>
		<link>http://www.softwarebyrob.com/2007/04/04/deadlines-on-being-a-professional-software-developer/comment-page-1/#comment-441</link>
		<dc:creator>http://</dc:creator>
		<pubDate>Thu, 05 Apr 2007 06:41:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarebyrob.com/2007/04/04/deadlines-on-being-a-professional-software-developer/#comment-441</guid>
		<description>I think professionals make quality products (and that quality is recognized by &quot;users&quot; when they pay for the products).  Hitting deadlines is a component of quality.  In some fields (software) it&#039;s more important, in others not so much. My guess is it&#039;s *very* important in fields that require large groups of people to work together.</description>
		<content:encoded><![CDATA[<p>I think professionals make quality products (and that quality is recognized by &#8220;users&#8221; when they pay for the products).  Hitting deadlines is a component of quality.  In some fields (software) it&#8217;s more important, in others not so much. My guess is it&#8217;s *very* important in fields that require large groups of people to work together.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Walling</title>
		<link>http://www.softwarebyrob.com/2007/04/04/deadlines-on-being-a-professional-software-developer/comment-page-1/#comment-440</link>
		<dc:creator>Rob Walling</dc:creator>
		<pubDate>Thu, 05 Apr 2007 04:00:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarebyrob.com/2007/04/04/deadlines-on-being-a-professional-software-developer/#comment-440</guid>
		<description>Good point.  In fact, your point holds for any great artist or performer: Picasso, Frank Gehry, Paul Simon, Bob Dylan, etc... A work by someone with clout can still be a smashing success and be months, even years late. Being famous, amazingly talented, or beloved by lots of people tends to get you out of things that tie the rest of us poor saps down...like deadlines. Douglas Adams was a legend and could do what he wanted because we would all buy his books even if he delievered them late. Was he a professional? Absolutely. But the same rules that apply to you and I don&#039;t apply to Mr. Adams.  In thinking more about this, success seems like a better measure of being a professional than deadlines. In some fields, such as software, part of success is hitting deadlines. In others, such as writing a book, if you&#039;re an unknown then success means hitting your deadlines and delivering a good book. If you&#039;re Douglas Adams success means delivering a good book, and deadlines are much less relevant.</description>
		<content:encoded><![CDATA[<p>Good point.  In fact, your point holds for any great artist or performer: Picasso, Frank Gehry, Paul Simon, Bob Dylan, etc&#8230; A work by someone with clout can still be a smashing success and be months, even years late. Being famous, amazingly talented, or beloved by lots of people tends to get you out of things that tie the rest of us poor saps down&#8230;like deadlines. Douglas Adams was a legend and could do what he wanted because we would all buy his books even if he delievered them late. Was he a professional? Absolutely. But the same rules that apply to you and I don&#8217;t apply to Mr. Adams.  In thinking more about this, success seems like a better measure of being a professional than deadlines. In some fields, such as software, part of success is hitting deadlines. In others, such as writing a book, if you&#8217;re an unknown then success means hitting your deadlines and delivering a good book. If you&#8217;re Douglas Adams success means delivering a good book, and deadlines are much less relevant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: http://</title>
		<link>http://www.softwarebyrob.com/2007/04/04/deadlines-on-being-a-professional-software-developer/comment-page-1/#comment-439</link>
		<dc:creator>http://</dc:creator>
		<pubDate>Thu, 05 Apr 2007 03:27:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarebyrob.com/2007/04/04/deadlines-on-being-a-professional-software-developer/#comment-439</guid>
		<description>So by your classification, Douglas Adams wasn&#039;t a professional writer...?</description>
		<content:encoded><![CDATA[<p>So by your classification, Douglas Adams wasn&#8217;t a professional writer&#8230;?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

