a friend recently gave me this same advice, and it does seem like a good idea. i’ve been trying to rework my github readme’s to all start with why/what/how, an

a friend recently gave me this same advice, and it does seem like a good idea. i’ve been trying to rework my github readme’s to all start with why/what/how, and it's hard! they should be concise, and yet sufficiently explanatory. i’m not sure there is a why/what/how for all audiences. to get it right, you have to pick a subset of your potential readers and write for them. otherwise you trade concision for generality, and then lose some of your true target audience to boredom.