The collapsing quality of dev.to (2021)
wagslane.devIt's not just dev.to, it's most online developer content sources these days.
A lot of people noticed that you can become 'famous' online which will gain you the ability to sell a course, earn from content or get better jobs and opportunities due to 'influence'. And it works especially good if you can find a new framework/language/platform that you can write content about, since there is less content and you can get 'famous' faster.
And as such, it has become an endless race of trading off content quality for eyeball quantity - people write bullshit blog posts and ask silly or provocative questions on twitter that are easy to engage with, thus gaming the algorithms and getting more eyeballs on their content.
Then, in a nice little reference loop from hell, the 'lower ranked' influencers will like and share this content, leave comments such as 'Omg great article!' not because it is good, but because they know that by engaging with another creator with 'more influence' they can get more eyeballs on their content, making the creator think 'hey this gets eyeballs' so they create more content like that. And then others will copy what works for the 'higher ranked' influencers, thus creating a stream of similar content which the 'lower ranked' influencers will copy from and so on and so on. With so many cyclic references and no garbage collection, all we are left with is garbage itself.
Oh if only the fallout stopped there.
The proliferation of these sources have torpedoed my Google effectiveness.
Not only do these sources amplify themselves, they are of near necessity targeted at simple use cases. The result? Google has ample popular material filled with my relevant keywords but void of any usefulness to anyone not just getting started. As it happens, the people with the most questions _are_ just getting started, and do find the results relevant pushing content on the margins further down the list.
Worse still, with Google's increased focus on natural language processing, their seeming approach of "what you're really asking is..." makes loose queries even more difficult. Definitionally the most common questions aren't edge cases, at least not the single one you're interested in.
After all these years, I think I need to retrain myself on how to Google (distinct keywords no longer cut it unless I have a sequence where I can look for an exact match), and recently started falling back to other search engines with some success.
Edit: grammar (believe it or not)
>unless I have a sequence where I can look for an exact match
Google these days treats quoted strings as guidelines anyways.
I think it's even worse:
Google these days treats your whole query as a suggestion
but quite frankly I am a bit of a glass-half-empty person
Yeah, but the quotes were meant to mean specifically, exactly this string and even that doesn't work anymore.
I've been experiencing that for years and it boggles my mind...
I think you hit the nail in the head here, and I'd also say that this is true for pretty much anything that is bloggable today (e.g financial advice, recipes, product reviews) and is a consequence of mass social media making people addicted to getting attention.
I’ve had a personal homepage for almost 20 years, and I’ve never looked at the traffic logs. I am certain I could learn what people care to read about, where people link from, and so on, but a big part of me likes that it’s my page and not my visitors’. It’s just a museum of quirky personality, this is not a potential revenue stream, and I’m not a “content creator”.
Affiliate links have ruined all product reviews.
This has been a growing problem in JavaScript land for many years. I feel it got a lot worse when Vue launched and it's creator got "JavaScript Famous" and was able to earn a salary via supporters and work on the thing full time. It created a gold rush of people trying to all become "JavaScript Famous" so they too could open a Patreon and quit their day jobs.
There was a time when it felt like nobody could learn React without blogging about it.
Or, the content that is popular right now (i.e. highly ranked in search results and heavily linked to) is dominated by material aimed at novices, because the readership is dominated by novices.
The issue is that the ranking stops working well for the minority of people who are in the advanced category.
The problem with dev.to, and pretty much every blogging platform like it, is that it encourages the mindset that the articles about problems you have yourself are the best articles to learn from, and that things that aren't directly applicable to other people won't get promoted. That leads people to think they should write boring, generic things about language fundamentals in order to become 'famous'. People end up rewriting the language docs in their own words. How dull.
The reality is that most interesting dev articles are about relatively unusual problems that a dev solved in an innovative way. You can learn a lot about dev work from those (approaching problems, thinking about things, some cornercase dev tools, algorithms, etc) even if you can't cut and paste code from them into your own project. This exposes a further problem though - you can't write those articles until you're sufficiently experienced to face those problems, and knowledgeable enough to solve them. If you're a new dev starting out with ambitions to be a 'thought leader' and wanting to get to the top fast, you're bound to end up writing another "Why Array.pop is the best array method ever!" article.
IMO these social blogging platforms for developers lowered the overall quality of online technical content by a lot, and made researching technical topics a fair bit harder.
It used to be that well-researched people and passionate people blogged about technical topics they knew very well, and when they blogged about unfamiliar topics they usually declared that upfront.
Nowadays there are an order of magnitude more grifters churning out a massive amount of blind-leading-the-blind garbage to "build a presence", and they usually pose as experts even though they barely know the topics. As an example, whenever I try to compare two similar technologies/libraries I'm not familiar with, I can almost always find one or more Medium or whatever articles on the topic, but 80+% of the time it's quite clear the author basically wrote the useless crap of an article after reading the READMEs, or slightly better, the bare minimum example projects.
This is a hard problem, and I'd love someone to solve it.
I was looking recently for some guides about Docker, as some parts were confusing me -- everything on the first couple of pages of Google was clearly just badly repeating the "getting started" guide, which I'd already read!
Blogging platforms that make it easier to publish and to be discoverable contribute to the problem just by making it easier to publish and to be discoverable. When writing a blog meant writing your own HTML, or at least installing and configuring some blogging software, and you’d have to write content other people linked to get a good page rank for your website, that served as a filter for low-quality content.
I’m not advocating to abolish blogging platforms, but they’ve been a double-edged sword in that way.
This is totally a function of the experience level of the reader. When I was a beginner/intermediate dev, I was actively seeking out articles about the basics in everyday language from different people so I could grok the language. I'm much more comfortable going straight to documentation now, but there is absolutely a place for beginner explanatory blog posts.
The fact that they are generally crap is an orthogonal problem and one the author addresses pretty well IMO.
> The reality is that most interesting dev articles are about relatively unusual problems that a dev solved in an innovative way
Do you have a list of those articles? And which sites do you visit to find those articles?
And which sites do you visit to find those articles?
A few that come to mind:
Hosting SQLite databases on GitHub Pages or any static file hoster https://news.ycombinator.com/item?id=27016630
How to crawl a quarter billion webpages in 40 hours https://news.ycombinator.com/item?id=4367933
Writing an open source GPU driver without the hardware https://news.ycombinator.com/item?id=30107002
Teleforking a process onto a different computer https://news.ycombinator.com/item?id=22987747
How NAT traversal works https://news.ycombinator.com/item?id=30707711
BPF, XDP, Packet Filters, and UDP https://news.ycombinator.com/item?id=24848391
A viable solution for Python concurrency https://news.ycombinator.com/item?id=28880782
Updating the Go Memory Model https://news.ycombinator.com/item?id=27810459
zig-cc: A drop in replacement for gcc/clang https://news.ycombinator.com/item?id=22679138
Finite state machines as data structure for representing ordered sets and maps https://news.ycombinator.com/item?id=10551280
Time-lock encryption https://news.ycombinator.com/item?id=22061752
My first impressions of Web3 https://news.ycombinator.com/item?id=29845208
How to build large scale end to end encrypted video calls https://news.ycombinator.com/item?id=29570938
Secure value recovery https://news.ycombinator.com/item?id=21838413
How Google code search worked https://news.ycombinator.com/item?id=18582469
Deploying authoritative DNS with Mirage Unikernels https://news.ycombinator.com/item?id=21868589
Playing around with Fuschia OS https://news.ycombinator.com/item?id=23466564
Making tokio scheduler 10x faster https://news.ycombinator.com/item?id=21249708
JVM Anatomy Quarks https://news.ycombinator.com/item?id=22190815
The hunt for a cluster-killer Erlang bug https://news.ycombinator.com/item?id=31746090
Static B Trees https://news.ycombinator.com/item?id=30376140
Files are hard https://news.ycombinator.com/item?id=10725859
Faster JavaScript calls https://news.ycombinator.com/item?id=26143648
Firefox's new compiler https://news.ycombinator.com/item?id=16169236
Abusing Linux's firewall: The hack that allowed us to build Spectrum https://news.ycombinator.com/item?id=16821807
Million packets per second ingress https://news.ycombinator.com/item?id=9726185
Streams: A general purpose data structure for Redis https://news.ycombinator.com/item?id=15384396
Let's build a compiler https://news.ycombinator.com/item?id=20444474
Improving compression with zstandard https://news.ycombinator.com/item?id=18719592
When bloom filters don't bloom https://news.ycombinator.com/item?id=22463979
Critbit trees https://news.ycombinator.com/item?id=6920862
Mobile physical memory security https://news.ycombinator.com/item?id=25505517
How the Linux kernel works https://news.ycombinator.com/item?id=14422605
https://news.ycombinator.com/item?id=11467309 Following a select statement through postgres internals
LMAX https://news.ycombinator.com/item?id=3173993
ELF https://news.ycombinator.com/item?id=17114672
Reading privileged memory with side channels https://news.ycombinator.com/item?id=16065845
How fast are Linux pipes anyway https://news.ycombinator.com/item?id=31592934
Reverse engineering a mysterious UDP stream in my hotel https://news.ycombinator.com/item?id=11744518
io_uring examples https://news.ycombinator.com/item?id=23132549
Clojure design patterns https://news.ycombinator.com/item?id=15771561
Inside the Magic Pocket https://news.ycombinator.com/item?id=11645536
A high performance cache in Go https://news.ycombinator.com/item?id=21023949
Lockfree data structures https://news.ycombinator.com/item?id=7734202
mtime considered harmful https://news.ycombinator.com/item?id=18473744
Bracket colorization https://news.ycombinator.com/item?id=28692470
Linux load averages https://news.ycombinator.com/item?id=14959288
A bump in the wire to make your internet go faster https://news.ycombinator.com/item?id=17721496
Backblaze durability https://news.ycombinator.com/item?id=17550837
H.264 is magic https://news.ycombinator.com/item?id=12871403
Redbean: single file web server https://news.ycombinator.com/item?id=26271117
Gotchas from 2 years with Node https://news.ycombinator.com/item?id=9372303
Counting objects https://news.ycombinator.com/item?id=10259471
Idempotent APIs https://news.ycombinator.com/item?id=13707681
Norvig's auto correct https://news.ycombinator.com/item?id=42587
QuickJS https://news.ycombinator.com/item?id=20411154
...
Thank you for this list. It's ironic that I've seen so many "Awesome.. curated" lists but this is the first one I really want to go through.
The few "awesome" (and "are we X yet") lists I've seen/contributed to were terrible; they have a very low barrier to entrance, and a very high barrier to exit - which made them nothing more than landfills, essentially. I think the valuable lists are personal ones.
I've had pretty good experiences with "awesome lists", usually if the topic is language or framework and I just want a concise list of mature things related to topic. Other examples I've personally enjoyed:
https://github.com/awesome-selfhosted/awesome-selfhosted
https://github.com/255kb/stack-on-a-budget
https://github.com/cloudcommunity/Cloud-Free-Tier-Comparison
I instantly found things in your list that will solve issues with some side projects and allow me to get them up and running.
A big thanks
This is great... thanks for sharing.
I have a page called “Library” in my blog where I collect articles I find interesting. https://leite.dev/pages/library/
I’ve been putting my own on https://swizec.com/blog for over 10 years. About 15,000 people agree they’re good enough to stay subscribed.
Already subscribed to yours ;) Good newsletter content.
Lobste.rs frankly.
More programming oriented, less ego boosting.
How does one get an invite to join though? The suggestion seems to be to scroll through a list of hundreds of online handles to see if you know someone by their pseudonym, and assumes you can reach them out of band, which is obviously not going to work for the vast majority of people.
That’s the beauty of it.
I’ll invite you.
Just send me an email.
Might I email you as well? I'm a regular lobste.rs reader, but not yet a member.
Yes. You should just have gone ahead and emailed me, since now I have to respond both here and there. ;-)
Late to the party but I've been really enjoying lobste.rs and been passively trying to get an account. Would you be able to facilitate this?
Are there magnets involved?
Neither quality nor truth are popularity contests.
It's worth noting that it's a shadowbanned domain on HN: https://news.ycombinator.com/from?site=dev.to
Jesus, what a clusterfuck. It’s spam.
Where do you see this?
If you have over a small threshold of HN karma, you can enable "showdead" in your account settings.
dev.to submissions will appear as dead by default in the "New" queue. These may be vouched, though truth to tell, I don't bother.
"Dead" submissions won't appear in Algolia search.
Clarification: Showdead should be available to any account.
Vouching does require a small karma threshold.
Thank you. I just enabled it and now I can see what the parent post was talking about.
You can ask HN moderators. There is no public list.
dev.to is also shadow banned on most developer subreddits and other news aggregators I know of.
Wow, any explanation from the HN mods why this happens?
HN is well known to have very “proactive” moderation, and as such kill low quality articles. As explained in this whole comment section, dev.to is almost entirely low-quality articles, and as such it’s not unexpected for HN to ban the site altogether.
I wish they would add Twitter to this list. Every tweet or "tweet thread" that's been posted has been incomprehensible to read and navigate beyond the actual title or first tweet.
I feel like most people in this thread have been explaining why
Thankfully!
I have left Dev.to long ago after being one of the early adopters. The quality of articles is going down every time I visit the site. And this is absolutely not surprising: Dev.to encourages clickbait and low effort articles. Likes seem to be the thriving factor for pushing articles and you can even earn achievements for post with the most likes and views. A possible solution could be to ditch likes and view counts entirely, so people focus on the content instead of trying to publish articles with the most likes. Fight the root cause and not the symptoms.
Then how would you rank the articles, measure their quality, and choose what to put on the front page?
The same way you check what you buy from an online store: by the number and content of the negative reviews or downvotes. But they don't exist here because inclusivity is wanted more than quality.
Like counts, be it likes alone or Reddit-style with downvotes, is the wrong mechanic for community-generated content, as it incentivises posting something "for a quick like". As explained in my other reply, Slashdot has a really healthy, decade-old community without having like counts. Posts are ranked by comment count and if there is something really bad, users can report it. It's that easy and it works.
Wouldn't comment counts incentivize controversy-inducing content instead?
That's how I feel about it, it's essentially the way stuff is incentivized on 4chan, and we all know that community isn't really know for its high quality, friendly discourse...
Why is it necessary to measure quality?
Slashdot is around for like decades, a real internet antiquity, and made it without any likes or view counts. Posts that generate a lot of comments are ranked higher, as one can assume it generates more discourse. What else is really needed for a community? Isn't it about sharing knowledge and discussing it?
A front page, as you mentioned it, can consist of either posts that generate a lot of discourse. Or make it simple and just display the latest posts of the people you follow on it.
Same way more sophisticated content algorithms work, such as measuring retention (e.g. % of scroll depth) and bounce rate as a source of relevancy.
I never understood how dev.to worked from an engagement perspective.
Back in 2018ish I mirror'd some of my blog posts from my personal site to dev.to. Within a few months I had over 7,000 followers by doing nothing other than copy a few posts there with canonical URLs pointing back to my domain. I never tried to gain a following there, all I did was mirror my own posts and answer any questions folks asked in the comments of those posts.
I'll admit I suck at Twitter but I've had an account there for 10 years and while I don't post a ton, I do at least try to tweet something every few days and I have about a third of the followers there as I do on dev.to current day. I don't know, it makes me think something doesn't line up. I have a hunch almost all of the followers I have on dev.to aren't humans because why would so many people follow me on a platform I don't post on much but on Twitter I'm lucky to get ~10 new followers a month? At the same time I've had a few direct chats with the co-founder of dev.to (Ben) over the years and he's a really genuine dude. I can't make sense of the situation. Maybe dev.to is really just super optimized for making it easy for someone to follow you?
As for content, I tend to only create posts and videos on things I encounter in my day to day from any topic related to developing and deploying web apps. That could be anything from using shellcheck's -x flag to live coding a pull request for a third party project. I find it difficult to build a readership with these styles of posts because it's usually some obscure thing I learned while actively working on something, not "10 reasons why XYZ sucks" or something that will get a lot of interaction or be heavily optimized for organic search. The posts are more to reflect on something I've learned so I don't really focus on "gaining an audience", but it would be nice to grow large enough to be able to make courses full time. The process of learning something new, using it in production for a while while understanding it in depth and then distilling that into a video is really fun to me.
I think this will always be the case with these adtech platforms. There is a conflict of interest at play. In the end, the ad revenue always wins.
The only way to really filter this stuff is through self-hosted blogs. These can also be connected, but in a decentralised way e.g. https://indieweb.org is a good intro to some of the protocols in use.
Substack seems to solve that pretty well. No ads because authors get paid by readers, yet articles are still viewable publicly.
Substack is a paid newsletter thing. Some Substack newsletters might have some publicly readable entries, but the user experience on Substack is geared heavily towards getting the thing in your e-mail and paying for it, not free reading on the web.
Dev.to does allow downvotes and blocking bad content. You need to become a moderator to do that. I'm such an external moderator and flagged a lot of abuse in the system. I've noticed an improvement in the past couple of months where I have less content to flag. So they probably improved their spam account detection.
There's a lot of beginner content which is fine. Some marketing/SEO content which is to be expected. It's still a better experience overall when compared to medium. Right now only dev.to and hashnode are significant unmoderated alternatives to medium (there are smaller players like tealfeed etc.). Both are doing a better job than medium and I blog on all of them.
If they add "publications" which is the editorialized capability of medium they would solve the segmented content problem but that might make their monetization harder.
Restricting downvotes to moderators only is not effective. Also creating an environment where blind are leading the blind is not a good thing and the article is pointing to that.
Let me ask you this: How would someone become "sighted"?
What filter can you use to discover the next great writer?
How can someone practice enough to become good?
That's the idea of these sites. People might have limitations but they can build them up. The voting system works but has problems. The alternative is often worse, individual silos, social network noise, etc.
> I blog on all of them.
Wouldn't that hurt your articles ? Since there are multiple sites with the same content? Or if you have a blog, that would also drive traffic away from it, no?
All of them support canonical links. So no.
Oh that's the first time I have heard about Canonical links, very neat thanks!.
There's a lot of beginner content which is fine.
Well, not really. That's the point.
I disagree. That's a matter of opinion. I think this can be improved with the introduction of publications but they have their downside too.
The main reason I commented was the mistake related to downvoting and about spam.
It's not really a matter of opinion that beginner content will - by definition - not come with the experience to have the authority and originality that contribute to the quality of the writing.
People need to start writing somewhere. The fact that they get visibility relates to upvotes and lack of publications. They also have advantages in communicating with other beginners.
Sure. However, if one specific platform becomes the location where everyone is writing their beginner content, then even if the writers may benefit, the platform will suffer. Or at the very least, appear low quality to someone who is beyond beginner level.
There are several sites like this including Hashnode, medium, tealfeed, etc. They all suffer from the same problem.
Medium solved this with publications. Others solved it by tagging, moderation etc. although that's not ideal either.
Yes. For all the frustrations with Stack Overflow, they actually do a pretty great job on the reader side.
The site isn’t spammed by people posting the same stuff repeatedly. And you can find solutions of varying difficulty levels and quality.
The problem for them is that makes it harder to contribute.
Which may actually be an intrinsic part of resolving the excess of low quality items problem.
I love stackoverflow. I think it's great for what it tries to solve and far exceeds sites like Quora.
But for articles the alternatives: Dzone, Hacker Noon and medium publications such as Better Programming, etc. aren't great either.
Generic good writing is hard and very subjective.
I agree - but the point was about quality, not learning your trade.
Sure. My point was about the fact that there are downvotes and spam blocking.
the real problem is that beginner oriented content is whats in top demand. I've written some advanced articles in the past on how to use more obscure locks and stored procedures in postgres in the past. it paled in popularity compared to random javascript content that only newbies wouldn't know. people are voting. just not for anything substantive.
That’s definitely tricky. When I have an issue like that, Google it, and find an article like you’re talking about, that’s awesome and I’m always so happy that someone took the time to write it. But I’m probably not going to read it until I need it, and if I did I probably wouldn’t have the context to appreciate it.
This was the core motivation behind why I started https://www.discoverdev.io/
Ran this for about 4 years before I called it a day earlier this year. Got busy with graduation and job searching! I do plan to start it again after I find a job and settle down :)
I followed this for a long time! Great work.
What's the average lifecycle of any website since the 2.0 days ? It's impressive how they constantly pop up and then pop out rapidly. Only to be replaced by the new -r variant.
Feels like articles talking about the low energy of lightning. Impressive but too short to matter.
Dev.to is suffering from the same problem that sites like Hacker Noon and Quora have already accepted as their faith. For the time being, Google is still treating Dev.to with quite generous "authority", so I imagine their organic traffic is through the roof.
But this has consequences of having your site infested with spammers, poorly written promotional content, etc. For example, one of the things you can do on Dev.to is publish an article, and then add a Canonical link to the original article (your website), which is what a lot of people do.
Having said that, you can find some great articles on the site from people who simply use Dev.to as their preferred blogging platform of choice. Though, even at a glance, the ratio of good and poorly written articles is probably around 25/75 which isn't all that great.
I stopped reading where they lamented grammatical errors and then proceeded to write “queue” when they obviously meant cue.
I have visited it four or five times in the past 9 months or so..
twice for something I knew was there (some time before) and could not find it - instead some other 'articles' talking around the subject with no answer.
and a few times because search results brought it up higher than other sites which actual had the answer I was looking for.
Didn't this site takeover some resource, trying to remember, something like robottxt.org or something get bought or pushed into this thing?
Now I can't remember the one thing it was good for so long ago, and do not intend to return to have it confuse and waste time in the future, I'll always be looking further down the results.
saw a post about 'farewell html5rocks' ( https://news.ycombinator.com/item?id=31935425 )
and that reminded me, that's the thing that I had occasionally googled for a quick html5 starter template.. and that had gotten pushed into the web dev thing - and that I could not find that via links or searches.. (not robottxt that I mentioned above)
I'm very glad that others are observing this as well. My last DEV post was literally the question of where I should hang out with possible future content to discuss on a more intermediate level.
It's great that beginners can start by diving into DEV but at some point you're just not a beginner anymore but because of all the noise your only option is to move on. Even if you put your 'experience level' to expert the relevant content shown in the DEV feed is for beginners. I think 'fostering a community for experienced developers' is really the only way for DEV if it wants to move beyond beginners.
I stopped reading after he admitted not actually reading the articles from his feed he is criticizing. He probably makes a valid point nonetheless but thats skipping your due dilligence in my book.
I pretty much agree with everything here. At the same time however, in the past 10 years official documentation for languages, frameworks, libraries, etc. has got _so_ much better. And while it’s true that googling stuff had become difficult, usually i can find the answer I need on how-to topics just by looking at the official docs.
I left dev.to awhile ago, largely in part because they encourage sexism, racism, etc. as prat of their code of conduct. It's truly sickening to me for a platform like this to not view all forms of sexism and racism as bad, not just the "correct" ones.
Dev.to simply is too focused on the open-source community and the web, it promotes and pushes up Javascript related content, presumably because a lot of the open-source repositories available on Github are JS or TS based.
It's not a true knowledge sharing platform, it's just a popularity platform where being the first to write about the new ANGULAR version 9999 is seen as a sign of great wisdom and being "on top of your game as a dev".
I wrote there a lot and stopped exactly due to the misalignment between what I wanted to consume and write about.
More generally, I find that ad-hoc aggregator websites like HN have a much higher hit ratio with my own interests. Also, if you're a professional developer actively involved in open-source and working within the JS/TS ecosystem you'll likely get a bit more value out of dev.to than I did, I guess it's just not my style...
NB: /has taken queues/s/queus/cues/
I too agree with lack of quality content. There are other platforms like Hashnode that you can definitely give a spin.
Hashnode is not so much better in this regard.
These days I primarily follow InfoQ, Habr, a few select individual bloggers, few larger company blogs and my feed has substantially improved.
Infoq is just a different kind of low quality IMO. It's experienced, enterprise Java/. NET devs and managers writing long articles that don't say anything or encourage you to overcomplicate things.
I'm sure it's not all like that just like I know there are some great devs/writers who use dev.to.
AFAIK, dev.to is shadowbanned here on HN.
Whenever I stumble upon dev.to, I can’t help but read everything with an indian accent. Is it just me?
I hate to say this but I feel like Dev had a nice start but went downhill fast.
Nearly all articles can be boiled down to “Look at this really basic thing, and follow me on A, B and C.
The first Dev talk I watched from the founder (Ben) was about how they gained a lot of traction being such a fast loading site, focus on content and less fluff. I loved the attention to performance, being open source and the customizations it enabled. Sounded great.
However the site got funding and started to focus on “diversity” and “inclusion” at all costs. Created a new CoC and the beginner content flooded in and has gone downhill since.
There is also a rampant spam issue and affiliate link farming.
> However the site got funding and started to focus on “diversity” and “inclusion” at all costs. Created a new CoC and the beginner content flooded in and has gone downhill since.
I was with you until that sentence. Focusing on “diversity” and “inclusion” or having a Code of Conduct with values like "Being respectful of differing viewpoints and experiences" is most likely not the reason for a community going downhill or beginner content flooding in.
The more likely reason is that the community became too big, the fluff posts from Medium shifted to other platforms and them not having a solid system for curating and surfacing interesting and valuable posts.
As the article is practically saying it, in order to be "inclusive" quality filtering does not exist. That makes quality nosedive, but it is inclusive - makes sense?
No, it doesn’t.
Unless you assume that only a certain group of people can put out quality articles.
Which based simply on HN articles is obviously not true (even though some people may continue thinking it is due to their preconceived biases, based on how HN comments in articles written by women will invariably have multiple people refer to the author with male pronouns).
Read again the paragraph with the title "What could Dev.to do better?". It is exactly that: no downvotes or flagging of low quality content in the name of inclusivity.
Same thing happened with Medium. Initially it had thoughtful content and once the platform became more popular, it also attracted worse content.
Typical articles:
How to build and Android app.
1. Learn android
2. Find and idea.
3. Build the app.
Thanks for reading this. Follow me on Twatter etc....
They basically baited you to open the link with an interesting title and the content had no substance.
> Follow me on Twatter etc....
Back in the good old days, forums typically heavily restricted self-promotion (even more so when it’s for commercial gain). Constantly shilling for your own website/Twitter/etc would end up earning you a ban.
I don’t understand why these social media platforms don’t enforce the same. Not only will this discourage this kind of crap but it would also benefit them as it would avoid people driving traffic away from the site (or having to pay for a paid commercial plan in order to do so).
I vowed never to use this site because I found certain elements of their code conduct to be questionable.
Why not prioritize everyone’s safety over anyone’s comfort?
And the bit about “reverse -isms” is wholly ambiguous.
It screams to never invest one second of effort in the site.
I will be downvoted for this, but the whole focus on marginalized people at the cost of everyone else, and not allowing any reverse-ism debates pretty much sums up the site.
A giant marginalized circle jerk.