It’s hard to measure the cost of code. Simple stuff can be ferociously time-consuming to develop, and bad coders often produce reams of poorly structured code.
But let’s assume you’re dealing with a typical, decent developer who doesn’t take the long route, or dangerous shortcuts. Read more
I was reading through some project management methodology just now (yay! My life is full of joy at last!) and came across the phrase “The Wicked Problem” in this line on Wikipedia:
Steve McConnell in Code Complete (a book which criticizes the widespread use of the waterfall model) refers to design as a “wicked problem” - a problem whose requirements and limitations cannot be entirely known before completion. The implication is that it is impossible to get one phase of software development “perfected” before time is spent in “reconnaissance” working out exactly where and what the big problems are.
