Solving a Problem with Community Learning

1 points by morris14 ↗ HN
I often find when I'm trying to learn a new skill, reading 1 or 2 blog posts doesn't give me a wide scope of the skill I'm learning. Whether it's a new language (I'm a developer), or a new productivity tool. More often than not, the articles need to be paired with 1 or 10+ other articles to get a good idea of the topic I'm learning. I often spend a large amount of time trying to source those articles...

"Did I find a reliable article?"

"This article assumes I have a certain level of knowledge already, I'll come back to this."

"What should I do now that I've read this article?"

Thats where I thought up the idea of resrcr.io. Users can sign up, and start to collate their resources into what I call "Journeys". A Journey can be as simple as "I want to learn ReactJS", or "I want to use the GTD methodology in Notion". I highly doubt any of these topics can be summed up in a single blog post, article or resource. resrcr.io allows you to map out a number of resources in a "Journey", allowing you to keep the resources neatly together, not needing to remember where you saved an article last month, and go through your Journey at your own pace!

Hey, why not explore Journeys that other people have collated? Why not give them an "Upvote" if you found someone else's Journey helpful? Have a question but can't find a Resource or Journey on the site? Ask, and wait for another user on resrcr.io to suggest a Journey!

Along with many other benefits such as adding private notes to a resource, and following your favourite "Pathfinders" (other users on resrcr.io), there are many benefits you can gain from being a member!

Today I've launched an early access registration form on resrcr.io. If you're interested, take a look and sign up! I won't use your email for anything other than letting you know when you can get access to the site! Also, if you register your interest before 1st November 2020, you'll get access to the Gold membership for 2 months at no cost!

0 comments

[ 2.4 ms ] story [ 10.7 ms ] thread

No comments yet.