5 ms·
Kudos for great instructions in the readme. However, bummer that despite the clear instructions, they never state what this does or why it might be helpful, fo
by natch 13y ago
Kudos for great instructions in the readme.
However, bummer that despite the clear instructions, they never state what this does or why it might be helpful, for what problem.
So many developers take the attitude of "if you don't know why you need it, you shouldn't be learning about it" but I don't see why they do that. You should always assume that some outsiders will come along, and some of them will have use cases that could benefit from your solution, if only you would explain what the hell it is.
- zimbatm 13y agoI think it's not fair to assume that the author is elitist about his tool. It's actually hard to remove enough context from one-selves to write documentation for new-comers. The author already wrote the tool and knows what it's about so it's easy for him to forget that not everyone does. That's my experience as a project writer at least.