I stand by my opinion.
Code that does not work is of no use to anyone. It could be the best written, best documented but ultimately, if it doesn't work the programmer has failed in his/her task.
You say "best written, best documented " wihich does NOT mean "maintainable", if it is maintainable, and does not work, the "failure" can be rectified in no time at all.

Documentating the crap out of a piece of code is mistakingly seen by many as "maintainability", horsefeathers!. The source of maintainability is structure. You can write 100 pages about 10 pages of code, if that code is not structured it will still not be maintainable.

If you examined the marketplace, I dare say you'd find more poorly written code working as opposed to well written code not working.
There will be no "well written code not working" in the marketplace for obvious reasons, but there is an enormous amount of "if you ignore this little quirk, it is good" software out there. Such software is often the result of original code wiritten without structure making it impossible to fix "this little quirk"

Is it not about time we became responsible and instead of using "you'd find more poorly written code working" where the work working should have been in quotes, as an excuse, started wirting mainatainable code.

Erik