> if you spend more than ~4 developer hours per month documenting/explaining/analyzing your architecture, then you've saving money with their product. Except t

> if you spend more than ~4 developer hours per month documenting/explaining/analyzing your architecture, then you've saving money with their product. Except this is a false equivalence. Not once have I documented something I was part of creating, in sufficient detail to explain it completely, without uncovering bugs/inconsistencies/oversights that otherwise would likely go unnoticed. Furthermore the practice refreshes the mental model in the minds of those documenting/explaining/analyzing, which otherwise atrophies and becomes out of sync with reality through the work of others.