profile

Fran Méndez

The problem with building a flagship community

Published 4 days ago • 1 min read

This week I have been super focused on strategy for Commune. For a while, I thought having a flagship community on the platform to use as a rock-solid case study would be a really great idea.

I played around with creating a paid community and newsletter to help people become unrejectable. It would be a space with periodic webinars from different folks teaching you how to improve your skills, share your work, and make jobs find you instead of the other way around. Building this would also give me a great excuse to test new Commune features like private groups and monetization.

After a bit, I completely discarded the unrejectable idea. I have my book, Shift, about to launch, so it made more sense to focus on that. Building a community around Event-Driven Architectures (EDA) and Shift seemed absolutely perfect. Plus, most of you already know me from my work on AsyncAPI, so it felt like a totally natural fit.

The problem is that neither of these ideas actually aligns with what Commune needs right now. Let me explain. For Commune to really work, we need a high density of communities. We need more newsletters and more people so cross-pollination naturally happens. We do not need a ton of people crammed into one single group. The goal is not a single massive audience, but rather a network of many different communities related to the same topics of interest.

Do not get me wrong here. I am not saying those communities are bad ideas. I only considered them because I genuinely believe they are useful. But running them does not push my main goal forward, which is making Commune grow.

So I decided to step back from all those side projects for now. I am fully focused on Commune. I am rolling up my sleeves and doing the not-so-glamorous job of reaching out to people one by one to get them on board. That is what will actually push this whole thing forward.

I am starting with my own network, as you have probably noticed. My network is mostly heavily into APIs, EDA, AsyncAPI, and that kind of stuff — and lately AI as well, but who is not on AI lately! Because of this, you should definitely expect more newsletters around these topics.

I know I'm not alone so I'm going to ask you for help here. What are some good newsletters around these topics that you think should be on Commune?


Pst! I see you're not on Commune yet. Click here to join us!​

Av. Joaquín Costa, 16, Badajoz, Badajoz 06001
​Unsubscribe · Preferences​

Fran Méndez

Creator of AsyncAPI | Empowering Staff+ Engineers & Architects to master Event-Driven Architectures with proven tools, processes, and best practices.

Hey hey! I'm Fran, the creator of the AsyncAPI specification (the industry standard for defining asynchronous APIs). Subscribe to my newsletter —The Weekly Shift— where I share expert advice about building Event-Driven Architecture and share my journey writing my first book, Shift: The Playbook for Event-Driven Architecture Advocacy.

Read more from Fran Méndez

The following is an article by Iván García Sainz-Aja, , in response to a previous essay I wrote. When I sent it, Iván quickly replied shocked by my words. He couldn't believe I was saying: ...right now, people are too focused on the “easy” wins of generation because building the runtime integration, like a rock-solid Spring plugin, is hard work. This is what he has been working on for years! And the worst part is that I was aware of it but, for someone reason, it didn't come to my mind when...

11 days ago • 8 min read

I recently got a couple of VCs interested in investing in Commune. Whenever this happens, I always ask why they want to invest and what they are asking in exchange. It's always the same. They want a huge part of the cake. Usually, they want more than half at this stage. And they offer some good money. It's good for me, but it's actually not much for them. I'm talking about tickets from 200k to 500k USD. However, what many people never tell you is that VCs strictly want hockey stick growth....

18 days ago • 2 min read

In my last issue, I asked you a simple question: should I make Commune open source? I got a lot of responses on Commune (yay!) and over on LinkedIn. Honestly, the feedback blew my mind. I expected everyone to shout a resounding yes. That absolutely was not the case. I was surprised most of you recommended I avoid it. Incredible. That included a lot of people in my network who have spent years maintaining open source projects or building open source products. I definitely did not expect that....

25 days ago • 2 min read