4 ms·
That writing style also annoys the heck out of me. Get to the point! That style was great when a person received perhaps two or three magazines a month in the
by PhantomGremlin 6y ago
That writing style also annoys the heck out of me. Get to the point!
That style was great when a person received perhaps two or three magazines a month in the mail. Today, if I don't get some inklings about the Five W's[1] in the first paragraph or two, then I'm on to the next article.
Life is too short for me to read the ramblings of someone being paid by the word. There's a need for, and a place for, long form writing. But not for 99%+ of what's out there.
[1] https://en.wikipedia.org/wiki/Five_Ws https://en.wikipedia.org/wiki/Five_Ws
- afavour 6y agoI have to disagree. When I’m reading API documentation (or a particular bugbear, a recipe) then yes, cut the crap and get to the point. But when it’s an article like this telling the story of the rise and fall of a business? I want to be taken on a journey, not receive a bullet point list of things they did wrong. There’s no reason why this topic should not be covered long form style.