4 ms·
Documentation describing whats already their and why, or documentation describing what's suppose to be there and why? Or both?
by drbojingle 4y ago
Documentation describing whats already their and why, or documentation describing what's suppose to be there and why? Or both?
- flandish 4y agoBoth, in my opinion. From incipient need (rfc, etc) to use-cases, to design specifications, tolerance acceptances, expectation management, support, and finally sunset/archival. 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.