[tomstoms]

I think you’re interpreting the advice way too literally. The author probably didn’t mean for you to document the answer to every single question you get, but questions you get about the system or domain you’re working, and where the answer isn’t readily available anywhere else.

[axaxs]

I don't disagree with you. If the question was about design decisions I'd made, I'd be in full agreement. But the article quite literally says 'every time.' You could rightly say I'm being pedantic, but if you're going to write life advice, it should be quite specific IMO. I'm not trying to be a jerk, but rightly (also IMO) pointing out flaws with the wording and tone.

[tomstoms]

> Every time someone asks you a question, they are highlighting a gap in the documentation.

This is a sensible statement assuming that the question is about the domain or system you’re an expert in. Not “what time is it” or anything like that.

> Take the chance to write the answer down

Perhaps the author should have qualified this advise with “take the chance to consider”, but I think the advise stands well on its own and I understand to apply common sense to it.