Yes we're in agreement that usability editing your docs and building automated processes that ensure that docs stay usable over time are the #1 priority.
> What I was saying is that if you do A/B testing of docs that are written in a non-minimalistic way with correct, functioning code, and docs written in the best style with code samples that do not work, the former will have more value and will generate more of the before-agreed metrics than the later.
Yes, also in agreement here. Usable docs is the table stakes.
Sorry about putting words in your mouth! I must have got triggered and jumped the gun without being very careful about looking at the exact words you used.
> What I was saying is that if you do A/B testing of docs that are written in a non-minimalistic way with correct, functioning code, and docs written in the best style with code samples that do not work, the former will have more value and will generate more of the before-agreed metrics than the later.
Yes, also in agreement here. Usable docs is the table stakes.
Sorry about putting words in your mouth! I must have got triggered and jumped the gun without being very careful about looking at the exact words you used.