1 year ago, most of my work lived in a very different world from Web3.
I was building and managing communities, writing technical content, and helping products grow. I’ve written dozens of technical articles, helped brands talk to their users in plain language, and seen firsthand how strong communities can make or break a product. But every time I opened Twitter or LinkedIn, there was one word I kept seeing everywhere: Web3.
People were talking about DAOs, DeFi, NFTs, on-chain communities, and “DevRel” as if it was obvious. It wasn’t obvious to me. I wasn’t a JavaScript wizard. I wasn’t deploying smart contracts. I was curious, a little intimidated, and very aware that I was late to the party.
So instead of pretending to understand it, I decided to do something different: learn Web3 in public, from scratch, and document the entire journey.
Who I Am (And Who I’m Not)
Quick introduction so you know who’s talking to you.
- I come from a mix of technical writing, community building, and startup experience.
- I’ve written 40+ technical articles for tech companies and communities like Huawei and Tether.
- I’ve helped build and run communities (online and offline) around products and brands.
- I care a lot about communication, clarity, and making complex things feel simple.
But here’s who I’m not:
- I’m not a hardcore developer.
- I’m not a Solidity expert.
- I’m not an “OG” crypto trader.
I’m someone who understands people and communication first, and technology second. And that’s exactly why Web3 DevRel and community roles attracted me.
Most Web3 projects struggle not because the tech is bad, but because:
- People don’t understand what they’re building.
- New users feel lost and intimidated.
- Developers don’t get the support, docs, or examples they need.
- Communities are created, but not truly cared for.
That gap between “we built it” and “people actually understand and use it” is where DevRel and community teams sit. That’s the gap I want to fill.
The 60-Day Experiment
Here’s the commitment I’m making publicly:
- 60 days
- 1 Web3 concept or topic per day
- 1 long-form article per day (roughly 1,000–1,500 words)
- Shared across Dev.to (main), my portfolio, Medium, Reddit, Twitter, LinkedIn
- Active participation in Web3 communities (Discord, Telegram, etc.)
These articles will not be “expert tutorials.” They’ll be “learning logs turned into useful explanations.”
Every article will follow a similar pattern:
- What I tried to understand today
- How I would explain it to a non-technical friend
- Why it actually matters in the real world
- Where I got confused and how I got unstuck
- Good resources I found for going deeper
At the end of 60 days, I want three things:
- A public portfolio that proves I understand Web3 fundamentals.
- Evidence that I can explain complex ideas in a simple way.
- Enough knowledge + proof of work to apply confidently for Web3 DevRel/community roles or internships.
Who This Series Is For
This series is for you if:
- You keep hearing about Web3, crypto, NFTs, DAOs, and feel like you missed the bus.
- You’re not a full-time developer but you’re curious about the space.
- You like technology but don’t want to drown in jargon.
- You’re exploring roles like DevRel, community manager, technical writer, or educator in Web3.
- You learn better when someone walks through things slowly and honestly, instead of pretending it’s easy.
It’s also for future hiring managers who might look at my work and wonder, “Can this person actually help our developers and community understand what we’re building?” Instead of answering that in a cover letter, I’d rather show them 60 days of consistent, public, practical learning.
What You Can Expect From Each Post
To keep things consistent (for you and for me), each post in this series will roughly follow this structure:
- Hook – why this topic matters right now.
- Simple explanation – like explaining to a smart friend who’s not technical.
- Real-world context – where you’ll see this in actual products/projects.
- My learning journey – what confused me, what finally clicked.
- Resources – 3–5 links (articles, videos, docs) that helped me.
Topics will go from absolute basics to more applied concepts. For example:
- Blockchain in plain English
- Bitcoin and why it was a big deal
- Ethereum and smart contracts
- Wallets, private keys, and staying safe
- Gas fees and why everything feels expensive
- DeFi basics (lending, borrowing, liquidity pools)
- NFTs beyond profile pictures
- DAOs and on-chain governance
- Layer 2s and scaling
- Web3 community building and DevRel
The goal is not to cover “everything in Web3” in 60 days. The goal is to build a strong, practical foundation and prove consistency.
What I’m Hoping to Get Out of This
Personally, I’m doing this for a few reasons:
- To remove the fear and fuzziness around Web3 concepts.
- To build a habit of daily structured learning and writing.
- To create a body of work that speaks louder than any bullet point on my resume.
- To meet people in the space who care about education, onboarding, and community.
Professionally, I’m aiming to transition into:
- Web3 developer relations roles (DevRel)
- Web3 community manager roles
- Web3 technical/content writer roles
If someone is hiring for those roles, I don’t want them to just see “interested in Web3” on my profile. I want them to see a full 60-day journey of actual learning, teaching, and community interaction.
How You Can Use This Series
Here’s how you can get value from this:
- If you’re new to Web3: Read along, ask questions, challenge things that don’t make sense.
- If you’re already in Web3: Tell me what I’m missing, correct mistakes, suggest better resources.
- If you’re also trying to transition careers: Steal this exact idea. Learn something in public for 30–60 days and document it.
And if you’re a DevRel or community manager already working in Web3, I’d especially love:
- Feedback on what beginners usually struggle with.
- Suggestions for concepts I absolutely shouldn’t skip.
- Thoughts on how someone with a writing + community background can be most useful to a Web3 team.
What’s Coming Next
The next post in this series will be:
“Blockchain for Non-Technical People: Breaking Down the Basics”
That article will try to answer:
- What is a blockchain, really, without buzzwords?
- Why do we even need it when we already have databases and banks?
- And how would you explain it to someone who doesn’t care about tech at all?
If that sounds interesting, you can:
- Follow me here on Dev.to: @ribhavmodi
- Bookmark my public portfolio (where every article in this journey will live):
- Connect with me on Hashnode, Twitter, LinkedIn, Medium if you’re on a similar path
This is Day 1 of 60.
Let’s see where this goes.
Top comments (0)