2 ms·
Well, I personally start most of my projects from scratch. To me, there are 4 phases to a project cycle, and the cycle is always repeating: First, is informati
by moron4hire 13y ago
Well, I personally start most of my projects from scratch. To me, there are 4 phases to a project cycle, and the cycle is always repeating:
First, is information collection: I want to know as much about the problem as possible. I'm not even looking at code yet.
Second, is fitting that information together. This could involve code to test theories, or writing documentation to communicate them to others. I'm trying to understand how the constituent parts of the problem fit together. I'm usually working with a subject matter expert on the problem domain, as the subject matter expert on software development. I'm usually going to end up telling the person I'm working with that some aspect of their problem or how they do work--as currently stated--will be difficult to encode as a program, but a small change in business practice would make it simpler.
Third, we come to a decision on how to progress. At this point, we basically have a few proposals for how to proceed, involving some initiatives for writing code and some initiatives for changing business practice. It has to be that way. You can't write code to completely synthesize an organic process. The best human processes will seek to build redundancy into the system. The best computer systems will seek to eliminate redundancy.
And finally, we act on it. We don't second guess our decisions until we're done doing it. We don't add to it, we don't take away from it, because that would all be changing the plan without collecting new information and understanding it in the greater context.
Then we start over from scratch. We always, always need to go back to collecting as much information as possible, which now includes "how well does the current software fit our expectations".