By bloid
via nhibernate.codebetter.com
Published: Feb 21 2008 / 22:40
Before you flame me, I'm not talking about the canonical book by Steve McConnell. What I mean is that this statement is a lie - "we're code complete on feature xyz." That phrase is a lie, or at least misleading, because you really aren't complete with the feature. Code complete doesn't tell you anything definitive about the quality of the code, or most importantly, the readiness of the code for actual deployment.
Comments
markturansky replied ago:
You're right. Code complete does not mean you're done. I think I've read that somewhere recently.... ;)
http://www.dzone.com/links/code_complete_doesnt_mean_youre_done.html
I'm happy to say it made it to the front page, too.
http://java.dzone.com/news/code-complete-doesnt-mean-your
Voters For This Link (10)
Voters Against This Link (0)