>>While I sometimes ridicule bad or sloppy thought and code, "Good enough" is often the fitting strategy, as Pareto principle will deplete funds otherwise and might scuttle the whole project. When faced with exponential growth or danger of extinction via punitive compensation or indemnification, this argument becomes thin, but for coding covering "good enough" for 1st release IMO is quite acceptable if done on features, not code quality. If the code itself is written in a way to allow fixing problems arising without total overhaul, that is often ok.
>
>Amazingly, on the same day, without reading this, our daughter finally decided to stop fiddling with her website and find a host. Because it has come to the point where she's fiddling with things she may make look differently or... various decorations and behaviors. Which means it's exactly "good enough on features", time to shove it into the field. And knowing her coding style, she's left it flexible enough to accommodate for future changes.

Give her a high five from a weird german...