You have a point, maybe my suggestion to make sure the prototype cannot possibly be taken into production is too extreme.

I agree with you that one shouldn't be embarrassed over it when it happens. Bad code that solves the problem and doesn't eat more maintenance resources than it's worth is good code.


I think it's one of those pieces of advice that, like all (?) good advice, has a dynamic to it should not be taken to far in either direction.

"Your prototype will be put in production" as a warning is counteracted by "... but perfect is the enemy of good". If your proof of concept actually solves the problem, maybe it *should* be put in production.

I think the nuanced lesson to take home from this aphorism is this: The hacker should be aware that their code may be put into production at any time, so that they can make the right balance of decisions on what quality it should be when presenting it.