Your career has a Single Point of Failure


About a month ago, I got back from Paris. I was there for the FOST conference (formerly API Days), and while the tech was cool, the vibe was… heavy.

I talked to a lot of people. I’m talking about some of the best engineers in the world. People who know more about specific technologies than almost anyone else on the planet. But you know what I smelled?

Fear.

Way too many people were terrified of losing their jobs. Others had just been fired and were scrambling. And a huge chunk were stuck in roles they hated, unmotivated, but too scared to move because the market looks “scary.”

It really got me thinking.

I felt incredibly privileged standing there. I’m currently burning through my own savings to build Commune. I quit the “safe” path to start a new life. It’s scary, sure. It has a cost. But I’m doing exactly what I want. I’m focused on impact, not politics.

But here is the thing that surprised me: Every single person I spoke to has the skills to do exactly what I’m doing.

They could start a business. They could consult. They could build the next big thing. But they don’t see it.

We need to stop pretending that a full-time job is “stable.” It’s not.

In software architecture, we spend our whole lives trying to avoid Single Points of Failure (SPOF). We move from monoliths to Event-Driven Architectures (EDA) because we want loose-coupling.

Yet, most of you have a tightly-coupled career with your company.

You depend 100% on a single company. You rely on a single manager (who might be great, or might be totally crazy) to decide if you get paid next month. If that one node fails, your whole system crashes.

That isn’t stability. That’s high-risk gambling.

Why don’t these brilliant engineers jump? I think it’s because they don’t know their own value. The industry gaslights you into thinking you’re just a cog in the machine.

And let’s be honest: you hate marketing. You prefer to be in your room, solving complex engineering problems. The idea of “selling yourself” feels weird or scary.

But you have to reframe this. Building an audience isn’t about becoming a LinkedIn influencer posting inspirational quotes. It’s just public documentation of your expertise.

I’m not telling you to quit your job tomorrow. That would be reckless. I’m telling you to stop pretending you’re safe and start packing your parachute.

  1. Get your finances right: If you are earning a senior engineer’s salary, stop buying junk. Build a runway. You need 8–12 months of savings. This buys you the mental freedom to say “no” to bad deals and “yes” to risks.
  2. Start owning your distribution: This is where you fix the marketing bug. You need people to know who you are.
  3. Share the journey: You don’t need a massive audience. I have ~1,500 newsletter subscribers and ~3,000 followers on LinkedIn. In the grand scheme of the internet, that’s nothing. But it’s enough to test ideas. It’s enough to get that first customer.

Start a newsletter. Start a YouTube channel. Don’t sell anything yet. Just share what you know.

If you wait until you get fired to start building your network, it’s too late. You need to build the relationship with your audience now, while you don’t need their money.

The stability you think you have is an illusion. The market is messy, and relying on one employer is a bad architectural decision.

You have the skills to build the product. Now you need to put in the work to build the platform.

Start packing that parachute. You never know when you might need to pull the cord.

Leave a comment on Commune

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

Fran Méndez

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

I’ve been thinking a lot about what Commune should look like. Chatting with Steven Willmott, he suggested something I never thought about: is Commune really a Substack alternative? I mean, Commune doesn’t send the emails. It’s not a competitor to Kit, Mailchimp, Beehiiv, Ghost, and other ESPs. Instead, it integrates all these networks. Substack is a closed network. That’s a fact. And it’s a fair business model, this is not meant to be a critique. Kit, Mailchimp, Beehiiv, Ghost, Buttondown,...

Focus!

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

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