I've been on several sizeable projects where what you suggest, i.e., starting over, was tried. When they jumped into it without any clear idea of what they were doing, the attempt failed in each case.
The most expensive failure cost the firm then employing me, which shall remain nameless, $8 million. Early on, I told the project manager and my boss that the project was doomed and why, in considerable detail. Then I made sure everyone on my team found jobs elsewhere.
If you can't answer any of my questions, I'm going to avoid participating. I don't like failure.
Ed Poor
Poor, Edmund W wrote:
I've been on several sizeable projects where what you suggest, i.e., starting over, was tried. When they jumped into it without any clear idea of what they were doing, the attempt failed in each case.
The most expensive failure cost the firm then employing me, which shall remain nameless, $8 million. Early on, I told the project manager and my boss that the project was doomed and why, in considerable detail. Then I made sure everyone on my team found jobs elsewhere.
If you can't answer any of my questions, I'm going to avoid participating. I don't like failure.
This sounds like something out of a Dilbert comic strip. Dilbert should be required reading in any business administration program.
Eclecticology
On Tue, 2002-12-10 at 08:03, Poor, Edmund W wrote:
If you can't answer any of my questions, I'm going to avoid participating. I don't like failure.
Whether we ever use Jonathan's code or not, his asking questions about how our current code works is a _very good thing_. It gives us a chance to rethink it and see what can be improved here and now.
-- brion vibber (brion @ pobox.com)
wikitech-l@lists.wikimedia.org