> I quite strongly disagree. Just like picture is worth a thousand words, working code (prototype) is worth a thousand words too. Working code is the easiest p

> I quite strongly disagree. Just like picture is worth a thousand words, working code (prototype) is worth a thousand words too. Working code is the easiest part. No one every throws it out and we are doomed to maintain the shitty prototype code for years. I find for internal software / consulting: "working code, ends arguments" but for enterprise software it is exactly the opposite. It's idiosyncratic code that doesn't scale to a team developing it. It's has no tests and no thought to broader usage. There is no documentation. It fails apart after you put load on it, want HA, load-balancing, disaster recovery. Almost all code works at the small scale. It's so hard to prove to even mid-range developers why an architecture that "works" doesn't really work. When you mix developers coming from the opposite spectrum it is disastrous.