The 68 minute read time might have something to do with it. I skip anything of that length regardless of title, tags, etc. I actually remember scrolling past your post the other day. I remember it not for the title or any other content indicator, but for the reading time.
If I'm going to spend over an hour reading something, it will be something like an article in a refereed journal, or a couple chapters of a book. If I'm browsing Dev, I'm not looking to invest that much time in one thing.
Accessibility First DevRel. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
So you think DEV would deliberately not promote the post on social media due to the fact it is long and in-depth? That would be an interesting take on it!
As for personal preference on reading length, interesting that you would say that.
It raises interesting questions about why you would be willing to read it elsewhere but not on DEV?
Is that due to the fact you don't expect the content to be the same quality here (which would make total sense) or something else?
There can certainly be high quality Dev posts. But the type of thing I'd spend an hour reading is entirely different than what one would normally find on Dev, Medium, etc. If I'm browsing Dev, I'm spending at most 30 to 45 minutes total while drinking morning coffee or tea. I'm more looking for things along the lines of "I found this or that useful and why", concisely written, or ShowDev type posts showing off cool things people built. And in that 30 to 45 minutes, I want to check out several posts.
I don't know how the Dev team picks posts to promote. But I imagine that they probably look at reading time as one of several factors. I don't think they would necessarily skip the long posts. But I imagine that they would at least ask themselves the question "Why should I recommend reading this one hour post instead of multiple shorter posts?" before doing so. Additionally they would have needed to spend that time reading the hour long post themselves to begin with. And with limited time and a ton of content posted daily to wade through, something special would likely need to draw their attention to it.
Accessibility First DevRel. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
I would hope that nobody reads a listicle like that in one sitting, but rather sees it as a reference piece. But it is useful feedback nevertheless that shorter articles in a series may be a better way to get exposure.
Also interesting that due to where it was posted you wouldn't even attempt to read it.
Not something I had considered but I suppose if you associate DEV with short content then long content isn't going to appeal.
It is interesting as I had never thought like that I just look at whether something interests me and either read it or bookmark it, but it is super useful to know people approach it that way!
Thanks for the thought provoking perspective, I will be taking it into account when designing larger posts!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The 68 minute read time might have something to do with it. I skip anything of that length regardless of title, tags, etc. I actually remember scrolling past your post the other day. I remember it not for the title or any other content indicator, but for the reading time.
If I'm going to spend over an hour reading something, it will be something like an article in a refereed journal, or a couple chapters of a book. If I'm browsing Dev, I'm not looking to invest that much time in one thing.
So you think DEV would deliberately not promote the post on social media due to the fact it is long and in-depth? That would be an interesting take on it!
As for personal preference on reading length, interesting that you would say that.
It raises interesting questions about why you would be willing to read it elsewhere but not on DEV?
Is that due to the fact you don't expect the content to be the same quality here (which would make total sense) or something else?
There can certainly be high quality Dev posts. But the type of thing I'd spend an hour reading is entirely different than what one would normally find on Dev, Medium, etc. If I'm browsing Dev, I'm spending at most 30 to 45 minutes total while drinking morning coffee or tea. I'm more looking for things along the lines of "I found this or that useful and why", concisely written, or ShowDev type posts showing off cool things people built. And in that 30 to 45 minutes, I want to check out several posts.
I don't know how the Dev team picks posts to promote. But I imagine that they probably look at reading time as one of several factors. I don't think they would necessarily skip the long posts. But I imagine that they would at least ask themselves the question "Why should I recommend reading this one hour post instead of multiple shorter posts?" before doing so. Additionally they would have needed to spend that time reading the hour long post themselves to begin with. And with limited time and a ton of content posted daily to wade through, something special would likely need to draw their attention to it.
I would hope that nobody reads a listicle like that in one sitting, but rather sees it as a reference piece. But it is useful feedback nevertheless that shorter articles in a series may be a better way to get exposure.
Also interesting that due to where it was posted you wouldn't even attempt to read it.
Not something I had considered but I suppose if you associate DEV with short content then long content isn't going to appeal.
It is interesting as I had never thought like that I just look at whether something interests me and either read it or bookmark it, but it is super useful to know people approach it that way!
Thanks for the thought provoking perspective, I will be taking it into account when designing larger posts!