How do you tell the difference between a 'genuine insight' and 'content' when posting here?
by•
Meta question, but it's been on my mind since I had a post rejected and, rereading it, agreed with the rejection.
The difference I've landed on: content is written to be agreed with. An insight is written to be argued with. Content says "here are five lessons." An insight says "here's the one thing I believe that you might not, and here's why."
The test I now run before posting: could someone reasonably disagree with this? If not, it's content. If yes, and I can defend it, it's worth posting.
I'm curious whether other people have their own test, especially people who post here regularly and don't get rejected. What's the thing you check before hitting submit?
45 views
Replies
I had two threads rejected here, both build stories about adding Siri support to my app, the second one even with the product name taken out. The one that survived was a plain question with no product and no link: how much of your mobile app lives on the server. So my test is close to yours but from the other side: would this still be worth reading if nobody knew what I build? My second check is for comments: every number I quote has to be one I can point to in my own notes. A specific number someone could look up is the opposite of content.
I've had a couple of threads rejected here too, and looking back, both were basically me introducing a tool I'd built. The ones that went through were questions I genuinely wanted answered. So the check I've landed on is close to yours, just from a different side: am I asking because I want to know, or because I want people to see what I made?