We want to encourage people to ask questions on the DEV platform. That's one of the major reasons we're here, and we even have a #help tag for that purpose.
There are major cultural issues that are reflected on Stack Overflow, which many DEVers are hoping to address through our own community.
I think my actual realization here is that I would prefer that posts like these can utilize a different interface, or even a sub-dev.to experience.
Having a platform for both blogging and problem solving is unique, and a worthwhile endeavor, but that doesn't mean we all agree that DEV currently has the tooling and design choices to properly support all use cases. That's my opinion, and by the same token, that also should not (and does not) stop people from leveraging this community despite this.
Thank you for chiming in. It was important and we all appreciated it.
From what I've heard, there are long-distance plans for specific sub-DEV platforms. In the meantime, we organize with tags (e.g. #help). The core DEV team is always adjusting the platform to improve tooling for specific use cases.
By the way, if Ruby is your jam at all, you can always help improve tooling via pull requests on the DEV.to GitHub. Aside from that, bug reports and feature requests are always helpful too. :D
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.
We want to encourage people to ask questions on the DEV platform. That's one of the major reasons we're here, and we even have a
#helptag for that purpose.There are major cultural issues that are reflected on Stack Overflow, which many DEVers are hoping to address through our own community.
You're right. I'm sorry.
I think my actual realization here is that I would prefer that posts like these can utilize a different interface, or even a sub-dev.to experience.
Having a platform for both blogging and problem solving is unique, and a worthwhile endeavor, but that doesn't mean we all agree that DEV currently has the tooling and design choices to properly support all use cases. That's my opinion, and by the same token, that also should not (and does not) stop people from leveraging this community despite this.
Thank you for chiming in. It was important and we all appreciated it.
From what I've heard, there are long-distance plans for specific sub-DEV platforms. In the meantime, we organize with tags (e.g.
#help). The core DEV team is always adjusting the platform to improve tooling for specific use cases.By the way, if Ruby is your jam at all, you can always help improve tooling via pull requests on the DEV.to GitHub. Aside from that, bug reports and feature requests are always helpful too. :D