I Wrote 51 Articles in Web3. Here Is What Actually Happened
Source: Dev.to
Quick Note
The dashboard project from Days 46‑50 continues on the backend. I’ll share a live update on Day 56 and a final build recap on Day 59.
Today we shift to Phase 5 of this series: Career and Leadership in Web3.
If you want to keep up with this 60‑day Web3 journey, you can follow me on:
- X
- Medium
- Future
- Web3ForHumans Telegram community
My Writing Journey
I used to write every night, pour my thoughts into words, hit publish, and wait… then nothing. No clicks, no noise—just silence.
I thought maybe people didn’t like my voice, or worse, maybe I didn’t have one. I was wrong.
People didn’t skip my content because it was bad; they skipped because I gave them no reason to stop scrolling. That was the first lesson I learned about DevRel—without even knowing it had a name.
What 51 Days of Showing Up Looks Like (Numbers)
Medium Stats (Dec – Feb)
| Month | Presentations | Views | Reads | New Followers |
|---|---|---|---|---|
| December | 3.5 K | 428 | 93 | +13 |
| January | 1.8 K | 548 | 62 | +7 |
| February | 5 K | 689 | 105 | +8 |
Community
- Web3ForHumans Telegram: 40 members (and growing)
- Medium followers: 47
- Twitter/X followers: 19
Freelance Writing
Two articles published by Bitquery and CoinCodeCap:
- Top Prediction Market APIs
- DEX Router Slippage for Algo Traders
None of these numbers are viral, but every single one moved. That is what consistency does, and that is what DevRel is built on.
What Developer Relations Really Is
Developer Relations (DevRel) sounds corporate until you realize it’s simply “be genuinely helpful to builders in public.”
A DevRel engineer sits at the intersection of product, engineering, and community. They:
- Write docs
- Run workshops
- Answer Discord questions at midnight
- Speak at hackathons
- Tweet code snippets that save someone three hours of debugging
What It Is Not
A marketing job with a GitHub account.
The best DevRels are builders first. They feel the pain of a bad API or confusing onboarding flow because they’ve been there themselves.
In Web3, DevRel means being the bridge between a protocol’s technical team and the developers building on top of it. Protocol engineers are brilliant but often lack time to explain their work; DevRel does that translation—making the complex feel approachable without dumbing it down.
My two freelance pieces for Bitquery (prediction‑market APIs and DEX router slippage) came directly from this translation work: taking complex on‑chain concepts and making them readable for developers who needed them.
Writing Lessons That Apply to Community Building & DevRel
I used to think writing was about expression. Turns out it’s about tension. Your first line decides if your story lives or dies. If the opening sentence doesn’t make someone wonder, they’ll never reach your second.
The Open Loop
- Start a story but don’t finish the first thought.
- Leave a question hanging → create a curiosity gap.
Instead of: “I learned to write better by practicing daily.”
Try: “It took me six months to realize I was practicing the wrong way.”
The first time I used it, I posted:
“I used to think no one cared about my writing, until one comment changed everything.”
Twenty‑four hours later it got ten times more clicks than any of my old posts. People stopped scrolling because they needed to know what that comment was. That’s the power of an open loop—it pulls, it doesn’t shout.
The DevRel Content Formula
- Don’t start with the truth.
- Start with the mystery that leads to it.
Writing isn’t about dumping information; it’s about invitation. Invite readers to lean in, wonder, and need to know.
Building a Web3 Community
It’s not about follower counts; it’s about creating a space where people feel smarter after showing up.
Web3ForHumans grew to 40 members without any paid promotion—just daily content and genuine conversation. Small but activated.
The communities that win in Web3 share three things consistently:
-
A Clear Villain
- Every strong community knows what it’s fighting against (centralization, bad UX, information gatekeeping, etc.).
- Web3ForHumans exists because Web3 feels unnecessarily complicated. That shared frustration is the glue that holds early members together.
-
Reward Contribution Over Consumption
- Discord servers with 10 K members and zero active threads are graveyards.
- The best communities make it easy to contribute something small—answer a question, share a resource, test a new protocol—and recognize that contribution publicly.
- Every reply I got on Medium or Future came from someone who felt seen, not sold to.
-
Build in Public
- This 60‑day series is a community‑building exercise disguised as a learning journal.
- Every article is an invitation to follow along, disagree, or build on top of.
- Transparency creates trust faster than any marketing campaign.
February’s 5 K presentations on Medium with 689 views happened not because the content was perfect, but because it was honest and consistent.
The Real Work of Community Management
The romantic version: hosting Twitter Spaces, giving keynotes.
The real version:
- Replying to every comment
- Writing the weekly recap nobody asked for
- DMing the new member who joined but never spoke
- Staying consistent when engagement drops
In Web3 the tools are Telegram, Discord, Farcaster, and Lens, but the work is the same as any community: show up, add value, repeat.
The Metric That Matters
Size is secondary; the activation rate is what truly counts. If your community members are actively engaging, contributing, and growing together, you’ve built a thriving Web3 community.
Community & DevRel in Web3
nity has 500 members and 50 engage weekly, that is a 10 % activation rate, which is genuinely strong for Web3. Most large communities hover at 1 %–2 %. Quality over quantity is not a cliché here; it is the strategy. Web3ForHumans at 40 members with daily conversation beats a 4 000‑member ghost town every time.
- DevRel without community is just documentation.
- Community without DevRel is just vibes.
The best Web3 projects treat them as one function:
- The DevRel team creates content that attracts builders.
- The community gives those builders a place to land, stay, and grow.
- Feedback from the community flows back into the product via DevRel.
It’s a loop, and when it works it compounds fast.
Portfolio Before Resume
The freelance writing that came from this series happened because the content proved I understood the space. If you are targeting a DevRel or community role in Web3, the single most valuable thing you can do is build your own small community around something you genuinely care about.
- Web3ForHumans started as a Telegram group.
- This 60‑day series is its content engine.
That combination—community + content + consistency—is the portfolio that gets you hired.
Social Presence
- Twitter/X: 19 followers (not a big number, but every follower came from Web3 content, meaning each is a potential collaborator, reader, or future community member).
- 19 engaged followers are more valuable than 1 000 random follows.
Follow the Journey
If you want to follow along as I keep learning, building, and occasionally changing my mind about Web3, you can find the rest of this 60‑day journey on:
- X (Twitter)
- Medium
- Future
- Web3ForHumans Telegram community – discuss these topics with us.
Recent Milestones
- Day 46 – Dashboard origin and Phase 5 pivot
- Day 49 – Community coordination mechanics from games
- Day 50 – v0 scope for the dashboard
Resources & Projects
- Web3ForHumans Telegram – the community this series is building
- Top Prediction Market APIs – Bitquery freelance piece 1
- DEX Router Slippage for Algo Traders – Bitquery freelance piece 2
- Developer DAO – largest Web3 developer community to study and join