There is no such thing as a “Final Product”

by James 17. July 2011 03:49

A long-time client recently remarked that my solution delivered "Standardized Customization", confirming how pivotal those design decisions were ten years prior, when I initially conceived much of the architecture that still prevails today in that software.  Core to that success, I believe, was a fundamental understanding that one can not anticipate the changes that will inevitably occur, leading me to focus on flexibility rather than simply a final product.  This, in my opinion, is the key ingredient in any successful implementation, from the smallest features to mission critical solutions - there is no final product. 

The world evolves, thus does business, thus must software.

Tags:

Software | Architecture | Philosophy

Comments

7/27/2011 1:43:24 AM #

I whole heartedly agree with "The world evolves, thus does business, thus must software.", and as a corollary think the insistence of concrete requirements is ridiculous. An intelligent Team should be able to work with loose requirements, common sense, strong business knowledge and a healthy dose of forward thinking possibilities to develop software that meets the immediate needs, is delivered on time, and flexibly suited for unknown future enhancements.

ekim ottac United States

9/21/2011 3:59:56 AM #

Just informing you that I love your site, and I come here every day for the valuable information you provide. Keep up the great work!

15 passenger van United States

9/28/2011 12:21:03 PM #

Howdy! This is a real neat web site.

straight jeans United States

Add comment




  Country flag

biuquote
  • Comment
  • Preview
Loading



Advertisement

RecentPosts