On Jun 1, 2007, at 2:13 PM, Russell Wallace wrote:
Given a precise specification, the cost of converting it into code is reasonably predictable, yes. The more difficult and unpredictable part is coming up with the spec in the first place. I'm not talking about writing version 3 of your in-house payroll program using the same tools you used for versions 1 and 2; sure, that doesn't take a big leap into the unknown - it doesn't require new algorithms either. I'm talking about creating products that didn't exist before.
Designing and building new systems with novel ideas from scratch, systems the likes of which have not been built before, is not new to me. I've done it for Global 100 companies, and numerous smaller ones. I am perfectly familiar with the problem space on the systems engineering side. In some of the more interesting cases, it was taking risks with several hundred million dollars in transactions based on exotic analytics, in spaces and using techniques that had never been attempted.
I have, on occasion, dabbled in mundane systems but most have involved odd problem spaces. Fundamentally new apps are not something I have not experienced before.
Cheers, J. Andrew Rogers ----- This list is sponsored by AGIRI: http://www.agiri.org/email To unsubscribe or change your options, please go to: http://v2.listbox.com/member/?member_id=231415&user_secret=e9e40a7e
