왜 나는 Web3를 배우는가: 초보자에서 DevRel/커뮤니티까지 60일 여정

Source: Dev.to

Who I Am (And Who I’m Not)

Quick introduction so you know who’s talking to you.

• Mix of technical writing, community building, and startup experience.
• 40+ technical articles for companies and communities like Huawei and Tether.
• Built and run online/offline communities around products and brands.
• Passionate about communication, clarity, and making complex things feel simple.

What I’m not:

• Not a hardcore developer.
• Not a Solidity expert.
• Not an “OG” crypto trader.

I understand people and communication first, technology second – which is why Web3 DevRel and community roles attracted me.

Why Web3 Needs Better DevRel & Community

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 lack support, docs, or examples.
• Communities are created but not truly cared for.

The 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.

My Public Commitment

• Duration: 60 days
• Goal: 1 Web3 concept or topic per day
• Output: 1 long‑form article per day (≈1,000–1,500 words)
• Distribution: Dev.to (main), personal portfolio, Medium, Reddit, Twitter, LinkedIn
• Engagement: Active participation in Web3 communities (Discord, Telegram, etc.)

These articles will be learning logs turned into useful explanations, not “expert tutorials.”

Article Structure (Daily)

1. What I tried to understand today
2. How I would explain it to a non‑technical friend
3. Why it actually matters in the real world
4. Where I got confused and how I got unstuck
5. Good resources I found for going deeper

End‑of‑Journey Goals (After 60 Days)

1. A public portfolio that proves I understand Web3 fundamentals.
2. Evidence that I can explain complex ideas in a simple way.
3. Enough knowledge + proof of work to apply confidently for Web3 DevRel/community roles or internships.

Who This Series Is For

• Anyone hearing about Web3, crypto, NFTs, DAOs and feeling they missed the bus.
• Non‑developers who are curious about the space.
• People who like technology but don’t want to drown in jargon.
• Those exploring DevRel, community manager, technical writer, or educator roles in Web3.
• Hiring managers who want to see concrete proof of capability rather than just a claim on a resume.

Consistent Post Structure

• Hook: Why this topic matters right now.
• Simple explanation: Like explaining to a smart, non‑technical friend.
• 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.

Planned Topics (From Basics to Applied Concepts)

1. Blockchain in plain English
2. Bitcoin and why it was a big deal
3. Ethereum and smart contracts
4. Wallets, private keys, and staying safe
5. Gas fees and why everything feels expensive
6. DeFi basics (lending, borrowing, liquidity pools)
7. NFTs beyond profile pictures
8. DAOs and on‑chain governance
9. Layer 2s and scaling
10. Web3 community building and DevRel

The goal isn’t to cover “everything in Web3” in 60 days, but to build a strong, practical foundation and prove consistency.

Personal Reasons for This Journey

• Remove the fear and fuzziness around Web3 concepts.
• Build a habit of daily structured learning and writing.
• Create a body of work that speaks louder than any bullet point on a resume.
• Meet people in the space who care about education, onboarding, and community.

Professional Aspirations

• Web3 Developer Relations (DevRel)
• Web3 Community Manager
• Web3 Technical/Content Writer

If hiring for these roles, I want recruiters to see a full 60‑day journey of actual learning, teaching, and community interaction.

How You Can Get Value

• 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 transitioning careers: Steal this exact idea—learn something in public for 30–60 days and document it.
• If you’re a DevRel or community manager in Web3: I’d 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.

Next Post

“Blockchain for Non‑Technical People: Breaking Down the Basics”

It will answer:

• What is a blockchain, really, without buzzwords?
• Why do we even need it when we already have databases and banks?
• How would you explain it to someone who doesn’t care about tech at all?

Stay Connected

• Follow me on Dev.to: @ribhavmodi
• Bookmark my public portfolio (where every article in this journey will live).
• Connect on Hashnode, Twitter, LinkedIn, Medium if you’re on a similar path.

Day 1 of 60. Let’s see where this goes.