<?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"
	>
<channel>
	<title>Comments on: Does Thirdi have Good Programmers?</title>
	<atom:link href="http://senses.thirdi.com/posts/7-does-thirdi-have-good-programmers/feed/" rel="self" type="application/rss+xml" />
	<link>http://senses.thirdi.com/posts/7-does-thirdi-have-good-programmers/</link>
	<description>Welcome to Senses: a place for Thirdi Software to explore what's seen, heard, and felt about technology, software development, and life experiences.</description>
	<pubDate>Tue, 06 Jan 2009 03:37:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: isim</title>
		<link>http://senses.thirdi.com/posts/7-does-thirdi-have-good-programmers/#comment-4</link>
		<dc:creator>isim</dc:creator>
		<pubDate>Thu, 28 Feb 2008 07:56:41 +0000</pubDate>
		<guid isPermaLink="false">http://senses.thirdi.com/posts/7-does-thirdi-have-good-programmers/#comment-4</guid>
		<description>Two other important attributes that the Thirdi development team has is our &lt;i&gt;unwillingness to compromise the quality of our work&lt;/i&gt; and &lt;i&gt;our ability to work with inherited codes&lt;/i&gt;. 

Although as software developers, most of us are guilty of cutting corners in our codes at one point or the other, as much as humanly possible and our sanity permits, the Thirdi team has gone the extra miles and put in the extra hours to deliver quality products.

In terms of working with inherited codes, I always think it takes relatively more patience and skills to work with and improve on others' codes (without breaking them) than  when working with my own codes. In addition to trying to understand the function of a block of codes, the deeper question that needs to be answered is, &lt;i&gt;"Why did the other developer did it this way?"&lt;/i&gt; Contrary to popular belief, the answer &lt;i&gt;"because they are stupid and unprofessional" &lt;/i&gt; is often the wrong answer. More logical answers can often be found in the constraints in the development environment, technology framework, business requirement, architectural and database design, background processes etc.

For the past year, the Thirdi team has really stepped up to take on any challenge that came our way. And we are still going strong this year! Our goal, as Mark pointed out, is to deliver insightful and painless software. I am proud to be on the team :-)</description>
		<content:encoded><![CDATA[<p>Two other important attributes that the Thirdi development team has is our <i>unwillingness to compromise the quality of our work</i> and <i>our ability to work with inherited codes</i>. </p>
<p>Although as software developers, most of us are guilty of cutting corners in our codes at one point or the other, as much as humanly possible and our sanity permits, the Thirdi team has gone the extra miles and put in the extra hours to deliver quality products.</p>
<p>In terms of working with inherited codes, I always think it takes relatively more patience and skills to work with and improve on others&#8217; codes (without breaking them) than  when working with my own codes. In addition to trying to understand the function of a block of codes, the deeper question that needs to be answered is, <i>&#8220;Why did the other developer did it this way?&#8221;</i> Contrary to popular belief, the answer <i>&#8220;because they are stupid and unprofessional&#8221; </i> is often the wrong answer. More logical answers can often be found in the constraints in the development environment, technology framework, business requirement, architectural and database design, background processes etc.</p>
<p>For the past year, the Thirdi team has really stepped up to take on any challenge that came our way. And we are still going strong this year! Our goal, as Mark pointed out, is to deliver insightful and painless software. I am proud to be on the team <img src='http://senses.thirdi.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
</channel>
</rss>
