@davidaugust the problem with this philosophy is many people seem to grab on to any excuse they can find to avoid writing documentation. I'll take a crap UI with documentation over a great UI without any day. Firstly because things will always go wrong in ways the developer never expected, and secondly because the end users have a right to know how the systems they are using actually operate. If you don't properly document your project you take away the user's right to be educated about it.
@admin agreed, documentation should not be omitted, but in may applications also should not be necessary for use for the intended users.
We have more options than poorly designed UI with documentation or well designed UI without any. Many, if not most, UI will succeed at its goals if well designed _and_ documented.