Question: What are your thoughts about having the content of this repo discoverable via the dev.to search? I've been interested in projects like this which create material which is more "canonical" than the typical blog post.
Whether yes, no, or maybe, I'm just curious how this thought jives with the maintainer of such an incredibly successful project.
The technical articles on the site are great because each one is told just the way the author wanted, they have a personal touch and are the core of the whole platform.
But additionally, I feel like we could host more stuff that acts as the one true "source of truth" on a type of issue, which is community-driven. Projects like yours are the essence of how great this kind of thing can be.
The feature I'd be describing is a way for the pages in your project and other ones to be discoverable and readable and observes the GitHub project as the source for the whole thing.
Here's a project which sort of accomplishes that I like: devhints.io/
I think it might be a good idea to have such community driven GitHub repo as a "source of truth" for different useful information. Especially when dev.to is going open-source! This way dev.to could have algorithms related repo that might have been managed by community.
This is actually what happens now in JS Algorithms repository. People are creating pull requests and changing things there. But yes it is only about algorithms there.
I am so blown away by this!
Question: What are your thoughts about having the content of this repo discoverable via the dev.to search? I've been interested in projects like this which create material which is more "canonical" than the typical blog post.
Whether yes, no, or maybe, I'm just curious how this thought jives with the maintainer of such an incredibly successful project.
Hi Ben! I'm glad that you liked the repo! :)
I sometimes post small articles here in dev.to that may be related to algorithms. I mean something like dev.to/trekhleb/permutationscombin... or dev.to/trekhleb/dynamic-programmin.... But I'm not sure if this is something you meant by "canonical"?
Sorry I could have been much more clear.
The technical articles on the site are great because each one is told just the way the author wanted, they have a personal touch and are the core of the whole platform.
But additionally, I feel like we could host more stuff that acts as the one true "source of truth" on a type of issue, which is community-driven. Projects like yours are the essence of how great this kind of thing can be.
The feature I'd be describing is a way for the pages in your project and other ones to be discoverable and readable and observes the GitHub project as the source for the whole thing.
Here's a project which sort of accomplishes that I like: devhints.io/
Agree, the devhints.io is a great example!
I think it might be a good idea to have such community driven GitHub repo as a "source of truth" for different useful information. Especially when dev.to is going open-source! This way dev.to could have algorithms related repo that might have been managed by community.
This is actually what happens now in JS Algorithms repository. People are creating pull requests and changing things there. But yes it is only about algorithms there.
I am currently working on an article series here on dev.to explaining each of these JS algorithms and their implementation. Would that interest you?
Checkout my last article. I'm publishing one on palindromes today.
Oh absolutely. The community eats this stuff up!
Nice. I should continue then.