8 ms·
You're assuming someone places value on proper documentation because they need proper documentation to make it "accessible to you". That doesn't have to be the
by blindluke 4y ago
You're assuming someone places value on proper documentation because they need proper documentation to make it "accessible to you". That doesn't have to be the case.
For me, lack of proper documentation constitutes a red flag, and says something very negative about the project. The question "Is it properly documented?" serves as a simple and convenient way to filter out projects that have a low chance of being mature enough to fit my needs.
- makeitdouble 4y ago> The question "Is it properly documented?" serves as a simple and convenient way to filter out projects I hear you, my point is there are dozens of other convenient questions you can ask to filter out projects. For me personally "Is it widely used in production" is a better one for instance.
- blindluke 4y ago> my point is there are dozens of other convenient questions you can ask to filter out projects Absolutely. And I agree with you that "Is it widely used in production?" is a better filter. But that does not diminish the value of the filtering done by "Is it properly documented?". After all, it's not like we're limited in the number of criteria we can use to filter out bad projects.