Passionate generalist conquering the web one project at a time. Whether authoring libraries for node, JS, PHP, or Rust, I am always on the lookout for better solutions to common problems.
Location
USA
Work
Lead Developer & Co-founder at corpscrypt, CTO at REtech
If by applying this concepts/code they got into trouble.
Thanks for clarifying. One of the problems with this current de facto reality is that this could lead to dev.to (or the complete forem concept, for that matter) being regarded as an untrusted source for research one day. As you can conclude from my original post, I am under the subjective impression that what I am talking about is a growing issue, not one that was around enough to be concerned about in the past.
That might work if we are talking about in terms of the context in a academic research or wiki for a single source of truth [...]
I think this serves as a good qualifier for the type of articles I am referring to as I still have the feeling we might not think about the exact same kind of content. There are many articles on dev.to that are written in a manner that can only be interpreted as if they would be based on exactly that premise. It is within this exact categorization of content where I see said problem.
With that you increase the barrier of entry for potential new writers to start writing as a developer
Yes, that is indeed the culprit, isn't it? Everything I theorize about here is a potential danger to the very charm of dev.to.
The last paragraphs seem to be centered around topics concerning quality and/or outreach. I just want to make clear that I by no means propose any intervention on such a level. For me this falls under the same umbrella as opinion or perspective and I personally reject any form of content government that is based on anything that can be considered subjective. It is obvious to me now that I should have spent more time defining the type of content I am "targeting" here.
Max is a life enhancer for tech & entrepreneurship. Which seeks to blend both to build innovative products or services for the world that solves hard problems.
One of the problems with this current de facto reality is that this could lead to dev.to (or the complete forem concept, for that matter) being regarded as an untrusted source for research one day
Sure if it's aiming towards a Academic level context and it is not instead, Dev.to is a developer community focus with a diverse range of people in different level of nationality, expertise or perspective.
In terms of untrusted source wise, i agree that your mileage my vary in dev.to. Personally, I doubt you place a 100% trust on the results of Google or Stackoverflow codes without doing your due dilligence. If you do that who am I to judge? I would just say whatever works for you. You just might not be the intented reader of that article that all, so you just move on. So let's agree to disagree this :)
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.
Thanks for clarifying. One of the problems with this current de facto reality is that this could lead to dev.to (or the complete forem concept, for that matter) being regarded as an untrusted source for research one day. As you can conclude from my original post, I am under the subjective impression that what I am talking about is a growing issue, not one that was around enough to be concerned about in the past.
I think this serves as a good qualifier for the type of articles I am referring to as I still have the feeling we might not think about the exact same kind of content. There are many articles on dev.to that are written in a manner that can only be interpreted as if they would be based on exactly that premise. It is within this exact categorization of content where I see said problem.
Yes, that is indeed the culprit, isn't it? Everything I theorize about here is a potential danger to the very charm of dev.to.
The last paragraphs seem to be centered around topics concerning quality and/or outreach. I just want to make clear that I by no means propose any intervention on such a level. For me this falls under the same umbrella as opinion or perspective and I personally reject any form of content government that is based on anything that can be considered subjective. It is obvious to me now that I should have spent more time defining the type of content I am "targeting" here.
Sure if it's aiming towards a Academic level context and it is not instead, Dev.to is a developer community focus with a diverse range of people in different level of nationality, expertise or perspective.
In terms of untrusted source wise, i agree that your mileage my vary in dev.to. Personally, I doubt you place a 100% trust on the results of Google or Stackoverflow codes without doing your due dilligence. If you do that who am I to judge? I would just say whatever works for you. You just might not be the intented reader of that article that all, so you just move on. So let's agree to disagree this :)