I agree that some documentation can go stale pretty fast. My best approach to documentation (also code comments because they are inline documentation) was to describe "the why" we were doing something and not go so deep into the specifics of the how. The WHY you are building something usually never changes.
I agree that some documentation can go stale pretty fast. My best approach to documentation (also code comments because they are inline documentation) was to describe "the why" we were doing something and not go so deep into the specifics of the how. The WHY you are building something usually never changes.
But then it should be on Tools like confluence or code level?