Documentation describing whats already their and why, or documentation describing what's suppose to be there and why? Or both?
If the code is where the “why” is found, those who are the end goal consumers of the product will be frustrated, for a small example.