<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Tech Talk &#8211; 2 : KST Software life cycle</title>
	<atom:link href="http://invaders4ever.wordpress.com/2008/04/27/tech-talk-2-kst-software-life-cycle/feed/" rel="self" type="application/rss+xml" />
	<link>http://invaders4ever.wordpress.com/2008/04/27/tech-talk-2-kst-software-life-cycle/</link>
	<description>Just another WordPress.com weblog</description>
	<lastBuildDate>Mon, 28 Jul 2008 15:41:09 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: nana</title>
		<link>http://invaders4ever.wordpress.com/2008/04/27/tech-talk-2-kst-software-life-cycle/#comment-47</link>
		<dc:creator>nana</dc:creator>
		<pubDate>Fri, 09 May 2008 09:43:22 +0000</pubDate>
		<guid isPermaLink="false">http://invaders4ever.wordpress.com/?p=15#comment-47</guid>
		<description>



</description>
		<content:encoded><![CDATA[]]></content:encoded>
	</item>
	<item>
		<title>By: Madhu Prasanna</title>
		<link>http://invaders4ever.wordpress.com/2008/04/27/tech-talk-2-kst-software-life-cycle/#comment-23</link>
		<dc:creator>Madhu Prasanna</dc:creator>
		<pubDate>Sun, 27 Apr 2008 03:43:17 +0000</pubDate>
		<guid isPermaLink="false">http://invaders4ever.wordpress.com/?p=15#comment-23</guid>
		<description>Unfortunately, in mobile software business, things are not so well defined. As you know the time to market on mobile phones is very very important. Delay means potential customers buying some other phone and less sales. So the schedule is always tight. 

On top of it, code reuse cannot be done 100%, as each phone model has to be different from other. There goes lot of customization, especially in multimedia components. Multimedia capabilities are the main differentiators these days. When you take two phones, what you will check first is the multimedia capabilities. 

So, from a single company, there comes no phone that are same in everything. This makes our life difficult and we DO NOT follow these processes. Coding is very adhoc. No reviews.  No solid testing. Our mantra is &quot;release first, fix next&quot;. 

One way this is very flexible. You will have awsome power at your hands. You can determine how things goes into the phone. You can be creative, innovative. But this comes with responsibility. Have to be very very careful. 

I really enjoy this kind of environment. This makes me learn a lot and gives me &quot;near-market-experience&quot; every product developer longs for. When I see the phones I worked on market it gives me satisfaction. :)

I could code more, experiment more and I feel like life is in my control. It is addictive.

I guess over the period of time, software matures as other engineering practices. At that time we will get a easy &quot;ready-to-use&quot; solutions for all these problems, as other engineering practices. 

Evolving software maturity means evolving human minds. Way to go!!</description>
		<content:encoded><![CDATA[<p>Unfortunately, in mobile software business, things are not so well defined. As you know the time to market on mobile phones is very very important. Delay means potential customers buying some other phone and less sales. So the schedule is always tight. </p>
<p>On top of it, code reuse cannot be done 100%, as each phone model has to be different from other. There goes lot of customization, especially in multimedia components. Multimedia capabilities are the main differentiators these days. When you take two phones, what you will check first is the multimedia capabilities. </p>
<p>So, from a single company, there comes no phone that are same in everything. This makes our life difficult and we DO NOT follow these processes. Coding is very adhoc. No reviews.  No solid testing. Our mantra is &#8220;release first, fix next&#8221;. </p>
<p>One way this is very flexible. You will have awsome power at your hands. You can determine how things goes into the phone. You can be creative, innovative. But this comes with responsibility. Have to be very very careful. </p>
<p>I really enjoy this kind of environment. This makes me learn a lot and gives me &#8220;near-market-experience&#8221; every product developer longs for. When I see the phones I worked on market it gives me satisfaction. <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>I could code more, experiment more and I feel like life is in my control. It is addictive.</p>
<p>I guess over the period of time, software matures as other engineering practices. At that time we will get a easy &#8220;ready-to-use&#8221; solutions for all these problems, as other engineering practices. </p>
<p>Evolving software maturity means evolving human minds. Way to go!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
