depends. when the code changes, how do you enforce that the documentation changes, and that they change in sync? depending on how you're storing the documenta

depends. when the code changes, how do you enforce that the documentation changes, and that they change in sync? depending on how you're storing the documentation off to the side, do you have two versioning schemes to reconcile when trying to look at code history? does you documentation even ha e versioning? if you keep the docs in the repo, during code review you can say "hey, update the doc while you're at it" or "this doc change doesn't agree with this code change, can you take another look at it?"