« Career Calculus | Main | The other side of 'Run it and See if it Works' »

January 29, 2004

Comments

Phil Spadaro

"Run it and see if it works" is the basis for a great deal of innovation. It exposes weaknesses (and new ways of thiking) in code and other processes that otherwise would have not been discovered because of analysing to perfection the code (or process).

The above is my best excuse for lazy, backwards engineering of solutions. There is a need to sit back and think through the logic before running it. Having a list of goals and functions for the code (or process) and logically matching process to function will allow for more concise code in less time.

Certainly, even the most well thought out code will have its problems (innovations?). If we can take the mistakes as discovery and the process / goal approach and merge them, we will not only have structure with innovation, but creation without paralysis of analysis.

The comments to this entry are closed.