Applications for DevRel Uni Cohort 7 are OPEN 🚨 Deadline: April 25th. If you're building in AI, Web3, or DevRel, this one's for you 🧵 Dive into a hands-on program featuring sessions led by @dabit8, @nutlope, @francescoswiss, @buzea200, @PSkinnerTech.

Demo Day is here! Builders from DevRel Uni Cohort 7 are showcasing the projects they've built during the cohort with the wider community. Come join and ask questions🎙️ Join the Space: x.com/i/spaces/1XxyggoDAPZGM

Writing from the bottom of the heart makes me happy. I was a part of the @DevrelUni Cohort 7 and learnt a lot. Have shared my experience and learnings, do take a look :)

I've been active in developer communities for years. Organizing events. Mentoring students. Running workshops. Building spaces for people to learn and grow. I thought I knew what @DevrelUni Cohort 7 would give me. That confidence was half right and half dangerous. Because it didn't just add to what I had it made me question the foundation. Here's what five weeks with five incredible mentors actually did to how I think. 𝗪𝗲𝗲𝗸 𝟭 @buzea200 I had been obsessing over building. She made me realize building is only one piece. If people can't discover your work, understand it quickly, or give you feedback on it the value stays invisible. Distribution and feedback loops aren't extras. They're the work. 𝗪𝗲𝗲𝗸 𝟮 @dabit3 "Don't optimize for a title. Become a technologist." The people who get left behind aren't the ones who lacked talent. They're the ones who got too attached to a specific identity and stopped looking up while the landscape shifted underneath them. Still thinking about this one daily. 𝗪𝗲𝗲𝗸 𝟯 @PSkinnerTech My busiest week of the year. Everything felt like it was slipping. Then he said: speed without systems is chaos. I didn't have a motivation problem. I had a structure problem. Those are very different things, and fixing the wrong one wastes months. 𝗪𝗲𝗲𝗸 𝟰 @nutlope Keep products simple enough to explain in one sentence. Mine took four words: Tinder for developers. A platform where devs can find hackathon teammates, study partners, collaborators, and contributors matched by goals, not just skills. GitHub login required. Real builders only. That became the product. Week 4 is also when I finally gave it a name. Welcome to Navra. 𝗪𝗲𝗲𝗸 𝟱 @francescoswiss The hardest question of the whole cohort: Are you building this community for yourself, or for the people in it? Communities don't survive on branding. They survive on solid foundations good onboarding, real learning resources, and members who feel like the thing was genuinely built for them. That's the bar I'm holding NavraCommunity to. Five weeks. One idea that became real. I wrote the full story every lesson, every moment it clicked, and where Navra goes from here. Link is here 👇 medium.com/@hardikbandhiya/d…

5 weeks ago at @DevrelUni , I entered as an engineer focused strictly on code complexity. I’m leaving understanding that DX, community, and distribution are what actually turn code into an ecosystem. What I achieved during the cohort: 🔹 Deployed 4 modular core contracts for LoreBase on @Base Sepolia ($STORY, Staking, Governor, Fractional IP). 🔹 Shifted from pure coding to designing frictionless onboarding loops. 🔹 Documented the future of machine-readable docs for AI Agents. Read my full graduation reflection & protocol breakdown on Medium: medium.com/@mintoumbacaleb/c…

Just wrapped up @DevrelUni Cohort 7 🎓 Over the last few months I: → published 3 Substack articles on APIs, developer tooling, and Solutions Engineering → shipped multiple npm packages → built a Testnet Wallet Agent MCP Server → recorded and shared tutorials on YouTube and X → explored MCP, AI agents, APIs, and agentic workflows → started building an SMS-based wallet monitoring agent → continued developing Ovia, a Web3 travel app helping crypto conference attendees discover events, guides, and people around them The biggest shift wasn't technical. I stopped thinking about AI as a coding assistant and started thinking about it as infrastructure. Instead of asking "How can AI write code for me?" I started asking "How can AI, APIs, tools, and users work together inside a product?" DevRel Uni pushed me to stop overthinking and start shipping. Looking back, the most valuable thing I built wasn't a single project it was the habit of building in public. Full article 👇 0xgks.substack.com/p/what-de…

I read a marketing email, end to end, and it was worth my time: It went about how people throw their work into the sea each day. Some of it is forgotten, some of it washes ashore years later, and makes someone stop and ask: "Who did this?" In @DevrelUni Uni's cohort 7...

@DevrelUni Cohort 7 taught me one thing: Build. Share. Iterate. Repeat. Grateful to all the mentors, speakers, and fellow builders who challenged my thinking and helped me grow. Onwards to building stronger communities, better products, and becoming a better DevRel. #DevRel

Joined @DevrelUni wondering if DevRel was dying. Left thinking about something else entirely: How do humans build understanding when answers become cheap? A few reflections: hackmd.io/@ziyinlox/HyQHZcN-…

As part of my week 4 assignment for @DevrelUni, I wrote an article on Medium after 2.5 years about what I am building in cohort 7. medium.com/@manik23265/what-… This project is gonna bring a revolution in the future.

5 weeks. 5 sessions. 4 tools shipped. @DevrelUni Cohort 7 changed three assumptions I walked in with. The biggest: your docs audience is no longer just developers. Coding agents are reading them too, and they don't infer gaps. Links for the writeup and the tool I built below.

Wrote an article sharing my journey from a member to an alumnus at @DevrelUni :) Give it a read - linkedin.com/posts/mrmanik_m… As I bid adieu to an amazing journey. Thanks @buzea200 !!

About two months ago, I was accepted into #DevrelUni Cohort 7. I’m excited, grateful & honestly behind. Family, full-time work, weekly sessions, reflection, homework: it’s a lot. But learning in public means showing the messy middle too. So I created a repo to document it all.

I taught a class to @DevrelUni about developing systems to solve the most difficult problems, fast. "Doing the hard things upfront" is no longer enough. "Doing the hard things fast repeatedly" is the only way to stay relevant in AI's ever-changing landscape. I say this all the time. "Shoot with both eyes open." Looking through the scope with one eye closed may seem like focus, but it means you lose immediate situational awareness. On the battlefield, that gets you killed. Great video @mahima_thacker!

Is AI replacing DevRel? No. But the job is changing. My biggest takeaway from @DevrelUni Cohort 7 Session 5 with @francescoswiss: DevRel now needs better frameworks, AI-readable docs, and permissionless ways for builders to contribute. Watch the summary below 👇

Session 4 of @DevrelUni Cohort 7 with @nutlope changed how I think about Developer Experience. Developers are not the only ones reading docs anymore. AI agents, coding assistants, and automation tools are becoming part of the builder journey. My takeaway: great DevRel now needs to serve both humans and agents. I shared the summary in this video👇

Last week, we had the pleasure of having @francescoswiss, director of DevRel at @MetaMask, for the final session of @DevrelUni Cohort 7. Thank you, Francesco, for sharing your lessons and frameworks with the cohort. Here are some of the learnings from the session: - Francesco's Pyramid of builder needs. A Maslow-style hierarchy adapted for developers. You can't skip levels: if your docs are bad, no one cares about your grants, events, or hackathons. - Engagement / developer funnel. This separates value-driven onboarding from product conversion. Francesco gave the example of Builder Nights, the event series he created, and the methodology behind its success: non-shilling, open to the whole ecosystem (L2s, ZK tech, EIPs, different chains) rather than pushing one product. Only after that value-first stage do you run product-specific conversions. - DevRel Operations Grid. This maps the gradual shift from human-only workstreams to AI-assisted to agent-native across categories (education, community ops, content, agent coordination, support). The point is that AI adoption is gradual onboarding, not a sudden migration. - Docs are no longer just lower-funnel reference material. They're now top-of-funnel decision-making content that gets crawled by agents (the shift from SEO to GEO). Well-structured docs beat marketing-heavy websites as agent sources. - You now serve two audiences: humans and agents. That means LLM-friendly docs (llms.txt), MCP servers, agent skills, and guides agents can reason over. - Community work. Build a trusted inner circle (~50 superstars) and amplify their wins rather than your own.

Been Around the Block(chain): Episode 30 🎙️ A spotlight on stellar talent in Web3 & AI 💫 "It's important that the DevRel inspires builders how to use certain technologies and kind of removes the blockers for them to be successful with that technology." Wow. Number 30. And what better way to celebrate than a sit down with @ChronicleLabs very own Head of DevRel, Bianca Buzea (@buzea200). 😍 This one's nothing short of a devrel deep-dive — here's what we discussed: 🫴 The importance of the empathy muscle 🤖 The impact of AI on developer engagement and a DevRel's day-to-day 👩‍🎓 Building @DevrelUni 🗒️ Everything you need to know to be a good DevRel Aspiring DevRels: this one's for you. Want to watch / listen on Spotify? Link below! 👇 open.spotify.com/episode/2AQ… - Chapter list: 01:09 - Bianca's background 01:57 - From developing tech to helping others develop tech 04:40 - The most surprising parts about the DevRel vertical 06:42 - The absolute BEST parts about being a DevRel 08:31 - Why Bianca built DevRel Uni 11:54 - Explain what you do to a 10 year old 13:59 - How to be an exceptional DevRel 16:19 - The hardest part about being a DevRel 17:17 - Balancing spinning plates as a DevRel 19:41 - How has AI's rapid advancement affected the role of a DevRel? 23:38 - Qualities that you NEED to have to be successful 28:24 - The roles that set you up best to become a DevRel 31:11 - Creating the BEST working environment / culture in crypto 32:49 - Quick-fire questions 🔥 - Disclaimer: the views expressed in this episode are for informational purposes only and do not constitute financial advice. Always do your own research before making any investment decisions.

Finished DevRel Uni Cohort 7: A lot changed for me during this cohort. I joined thinking mostly like an engineer. I’m leaving with a much stronger appreciation for: - Developer Experience - Technical Writing - Community - Building in public - AI-assisted developer workflows

Episode 10 of my podcast series is out. We talked about @Parul27Y journey, experience so far of being a Blockchain Developer in multiple companies, then a business analyst at Accenture and currently DevRel at Kleros. Watch Here - youtu.be/dBTkuamJTJM?si=9Ekh…