When to do documentation:
- Nuggets of information, need to be referred by more people or more frequently - for example, Test Data, Deep links in different environment etc.
- It can speed up a new joiner's on-boarding. For example, some basic knowledge using which a developer can jump-start into building new feature and deploy stuff.
- Something you feel you are likely to forget for example, an assumptions you were forced to made for whatever reason.
When it comes to an API is used by different sets of users/clients, it needs to be documented properly. Otherwise, your consumers will either assume things, or, they will keep coming back to you with trivial questions, and that can result in low productivity on both provider's and consumer's end.
Look out for overdoing of documentations - its not good - rather, sometime its a waste of time and energy.