tag:blogger.com,1999:blog-11200164.post3221470899905695990..comments2023-09-19T05:02:58.359-04:00Comments on Nirav's Contemplations: The State of softwareNirav Thakerhttp://www.blogger.com/profile/07204297663478577248noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-11200164.post-49880000960822494122007-03-05T14:46:00.000-05:002007-03-05T14:46:00.000-05:00"These days, People comfortably accept existence o...<I>"These days, People comfortably accept existence of bugs in most software"</I> <BR/>It's not actually these days but the software industry has always been like that; and as you suggested the real problem lies in the fact that industry has become used to it. We take it for granted.<BR/>Reason is - we close our eyes and do not want to see the costs incurred in fixing issues and all the rework. While in other engineering streams, say manufacturing, rework costs are more tangible in the form of raw material and processing costs and cannot just be ignored. <BR/>Strange are our practices!<BR/>Historical languages might not be the problem. <BR/>The way out is definitely using the best tools, best practices and technologies and to shed off our inefficiencies. Reusability is the saviour.<BR/>And this can be achieved only through componentization. <BR/>Some 15 years back, lot of people in domain industries had to take VRS (voluntary retirement). It happened because of the inflow of viable and efficient tools and technologies. May the software industry see such a day soon enuff! <BR/>Let people be more efficient without considering bugs and rework for granted, enabling them to become knowledge workers rather than laborers.Nawal Kishore Lodhahttps://www.blogger.com/profile/15677947753540944526noreply@blogger.com