Post #3993671

A related peril is the stage where we have built enough that we have collected a set of regrets about the technology choices we made. Now we know how we could have done it differently. If we're not careful, we'll start rewriting the software before we've delivered it. Even if we give in to the urge and start swapping out components, we're likely to collect new regrets and form new ideas for improvement. I've heard of projects wallowing for years in rewrites and optimizations, never quite releasing. I think it's a superpower to use the proven-but-worse tool you have in the face of exciting tool improvement ideas. Can you think of a tool improvement and not act on it? Can you deliver in the face of viable improvement ideas?