4 ms·
https://news.ycombinator.com/item?id=31361023#31365022 https://news.ycombinator.com/item?id=31361023#31365022 Ridiculing the value of documentation does not ma
by tzmudzin 4y ago
https://news.ycombinator.com/item?id=31361023#31365022 https://news.ycombinator.com/item?id=31361023#31365022
Ridiculing the value of documentation does not make you look smart.
It rather hints at lack of experience with truly complex systems or collaboration in teams.
- gitonthescene 4y agoAre you saying this is a complex system or that any decisions made in the context of complex systems must be used for all software? Also, this was not in response to a post about documentation but rather a post about the file names. In any event, it says nothing about my experience and you are simply extrapolating.
- zozbot234 4y agoYou can always write documentation in comments. Using terse names for the identifiers when feasible can make it a lot easier to see the bigger picture wrt. multiple components interacting. It's a tradeoff.
- tzmudzin 4y agoAgreed, and it would probably be my preference. The code referenced here is pretty extreme NOT providing the guidance, hence my response to the poster defending the extreme and ridiculing the good practice.