I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
Top posts are based on a bunch of different weights. Last time I looked (a long time ago...) they are based on a handful of signals like, whether the user has posted before, whether any tags are subscribed, etc. It's not a simple case of "more views" or "more likes" driving things to the top.
On the other hand, some people already curate "best xxxx-topic posts of the week" meta-posts, which puts the whole thing into our hands as a community.
If you do that, be careful not to make your curated list reflect the top traffic items otherwise it's adding noise!
Last time I looked (a long time ago...) they are based on a handful of signals like, whether the user has posted before, whether any tags are subscribed, etc.
I am not sure if this is the way the top posts are selected now. But if it is, I don't think none of it matters. If I join Dev.to today, make a mind blowing post and never do anything else, the quality of the content should make the cut. Not engagement or traffic or whether they have subscribed to any other tags etc. Which is why I am saying there is a need for Editor's picks. Those traffic/engagement should be employed for algorithmic sections like top/relevant. Not editor's pick. Editor's picks should be completely non-algorithmic. What do you think?
Every Tuesday we round up the previous week's top posts based on traffic, engagement, and a hint of editorial curation.
This is from the dev team posting one of those top 7 posts. Editorial curation should be the only thing necessary if we are to discuss "Editorial picks" feature. Engagement and traffic doesn't always align with what a good post should be. Not to mention, currently dev writers seek validation happening through engagement and traffic. The validation should also be from fellow devs and editors who are experienced. Not just traffic or engagement.
Think of editor's picks as a feature to solve the edge cases from algorithmic sections too. NOT as a complete replacement or just as a new section.
Also, you don't have to ditch one method. It doesn't have to be this OR that. We can have both and people who crave engagement and traffic work towards that. And people who want to work and get noticed by more nerdier folks can work towards getting featured in Editor's picks.
To be clear, I am not saying one is better than the other. I am saying it's just preference. And I would ideally like to work towards both. Cos why not? :)
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.
Top posts are based on a bunch of different weights. Last time I looked (a long time ago...) they are based on a handful of signals like, whether the user has posted before, whether any tags are subscribed, etc. It's not a simple case of "more views" or "more likes" driving things to the top.
On the other hand, some people already curate "best xxxx-topic posts of the week" meta-posts, which puts the whole thing into our hands as a community.
If you do that, be careful not to make your curated list reflect the top traffic items otherwise it's adding noise!
Hey thanks for taking the time to reply.
I am not sure if this is the way the top posts are selected now. But if it is, I don't think none of it matters. If I join Dev.to today, make a mind blowing post and never do anything else, the quality of the content should make the cut. Not engagement or traffic or whether they have subscribed to any other tags etc. Which is why I am saying there is a need for Editor's picks. Those traffic/engagement should be employed for algorithmic sections like top/relevant. Not editor's pick. Editor's picks should be completely non-algorithmic. What do you think?
This is from the dev team posting one of those top 7 posts. Editorial curation should be the only thing necessary if we are to discuss "Editorial picks" feature. Engagement and traffic doesn't always align with what a good post should be. Not to mention, currently dev writers seek validation happening through engagement and traffic. The validation should also be from fellow devs and editors who are experienced. Not just traffic or engagement.
Think of editor's picks as a feature to solve the edge cases from algorithmic sections too. NOT as a complete replacement or just as a new section.
Also, you don't have to ditch one method. It doesn't have to be this OR that. We can have both and people who crave engagement and traffic work towards that. And people who want to work and get noticed by more nerdier folks can work towards getting featured in Editor's picks.
To be clear, I am not saying one is better than the other. I am saying it's just preference. And I would ideally like to work towards both. Cos why not? :)