Re^2: Estimating Task Complexity VS Loudmouth

Heh - Brilliant! But I would add that, against your better judgement (and no matter how much you warn against it), the prototype *will* become the production code.

Factor in some time to redesign the ugly bits once you more fully grok the problem domain.

Comment on Re^2: Estimating Task Complexity VS Loudmouth

Replies are listed 'Best First'.
Re^3: Estimating Task Complexity VS Loudmouth by BrowserUk (Patriarch) on Nov 23, 2004 at 17:35 UTC
... the prototype will* become the production code.* That is the intent. But only once the omissions of the prototype are demonstrated and acknowledged. That way the refactoring of the prototype has budget for, or an explicit waiver covering, those omissions. Examine what is said, not who speaks. "But you should never overestimate the ingenuity of the sceptics to come up with a counter-argument." -Myles Allen "Think for yourself!" - Abigail "Time is a poor substitute for thought"--theorbtwo "Efficiency is intelligent laziness." -David Dunham "Memory, processor, disk in that order on the hardware side. Algorithm, algorithm, algorithm on the code side." - tachyon	[reply]
Re^4: Estimating Task Complexity VS Loudmouth by bibliophile (Prior) on Nov 23, 2004 at 18:59 UTC
Ah, I see. I wholeheartedly agree - and I'll try that tactic on my next project :-) (My biggest problem seems to be convincing the Powers-That-Be that my learning how to do something needs to be part of the timeline.... folks seem to think that because you are a "computer guy", anything computer-related must be already-internalized knowledge. Sigh.)	[reply]