3 ms·
Because a poorly-documented product that does something, is much better than a well-documented product that does nothing. Engineers have to decide where to spe
by yen223 4y ago
Because a poorly-documented product that does something, is much better than a well-documented product that does nothing.
Engineers have to decide where to spend their time, and taking time away from feature development when your early-stage product doesn't have many features is not a winning move.
- replygirl 4y ago> a poorly-documented product that does something, is much better than a well-documented product that does nothing not necessarily. with the latter, you know the constraints of a solution and can make an accurate judgment on whether it's worth using
- wruza 4y agoTrue, but if it’s too early for a good documentation then talking about taking someone’s crown is too early as well.