Skip to main content
7 events
when toggle format what by license comment
Jun 30, 2016 at 19:51 comment added Peter Cordes This is a great way to express the same thing I said recentlyl on meta stackoverflow. Putting the real question as early as possible in a TL;DR section is huge. I also like bullet lists for the key points, since the eye tracks down a list more easily than a paragraph of English.
Jun 23, 2016 at 15:20 comment added Floris I like your use of the bold subtitles. I could skim this answer by just reading those, and get a good feeling for the direction of your thinking on the topic. Part of clear technical writing is indeed to make sure that people can skim without fear of losing the most important information.
Jun 22, 2016 at 20:44 vote accept M Barbosa
Jun 19, 2016 at 19:22 comment added dmckee --- ex-moderator kitten Mod Here's the thing: I let my better half proofread all my documents because things that I think are "clearly stated" are sometimes not at all clear to someone not approaching the text with my own mindset. It's easy to feel that a direction to ignore friction is a formality and not question when and where in your post to to put it while your reader has a different mindset. That mostly relates to things more complicated than "ignoring friction", but the way you get people to read those short and simple phrase is by making it easy and rewarding for them to read your post in the first place.
Jun 19, 2016 at 18:03 comment added M Barbosa Thanks for the tips! I agree that sometimes it can be miscommunication. But for example, if I state in my answer that I am ignoring the effects of friction and someone answers using friction then it seems like they were just too lazy to read.
Jun 19, 2016 at 17:58 history edited dmckee --- ex-moderator kittenMod CC BY-SA 3.0
deleted 1 character in body
Jun 19, 2016 at 17:52 history answered dmckee --- ex-moderator kittenMod CC BY-SA 3.0