Should content discovery match your knowledge, not your following list?
A few years ago I created a Twitter account. I was using it to follow only tech-related accounts.
From a Twitter thread I header of Firebase authentication. Finding a blog post - I learned more about it. Implemented it in my first app. And used Stackoverflow to fix issues. And to perfect the implementation.
Me discovering it was unintentional. I was doing things the old way before. Reimplementing authentication modules for each project. (Using Passport for Laravel). And I wasn't aware I needed it - and it skyrocketed every project start.
But what if I was doing intentional work to discover what I don't know? What if I was able to get exposed to the content that should interest me? And that should make my life easier.
Thinking about the big wide internet, it seems endless. Navigating our way around the specific tech-related content is a tricky task. How do we find quality? How do we find what is, not only our interest, but the topics and discussions that we need? How do we get exposed to Firebase authentication - not by destiny, but by intention?
That's why we are building Codaroo.
We shouldn't separate content discovery and learning by default. Both mentioned should intervene - and what we know, learn and don't know should merge. Based on that, fate shouldn't discover the content we discover. It should be more factual.
I don't want to see the 100th post about useState hook - I know that. But, what the heck is this useOutsideClick hook? And where and how should it help me?
I should be able to learn about it in an interactive manner - then get the chance to deep dive into the details. And the next time I start stumbling across the app - it should know that I know about useOutsideClick. Eventually, it should remind me. Ideally, It should give me more and teach me something new. Something related to what I already know, but not overlapping with it.
It should ask me about testing. And then gradually teach me if I am not good at it.
It should ask me about GraphQL. And show me the whole power of it. Gave me fast digestible exercises, to get the first glance. And then full access to materials, to deep dive.
It should ask me about authentication. And then show me Firebase authentication, Auth0 or Incognito - by intention, not by fate.
That's why we are building Codaroo.
To make a content discovery and nano-learning intentional. Personalized, not by your following preferences, but by your actual knowledge. Personalized enough so it adapts and grows with you as you grow.
[Fellow hackers to the rescue]
We want to validate this take - and our idea of how to do so is to go out with a product MPV (prototype) that takes on content from the internet, indexes it, and serves it as interactive exercises. After the exercise, you will be able to access the content - so basically your first answer then learns (so we assess the knowledge level).
If you would want to validate this idea - what would you do differently from us?
And if you wouldn't want to validate it - why not? What do you see as the main issues?
Thank you!
