What I underlined in Taleb's The Black Swan, through the eyes of a founder

I read Nassim Taleb's "The Black Swan" in the summer of 2022. At the time I was learning to write my first app and trying to put a team together for the first time. The book landed at a very specific moment in my life, which is why it stayed with me not as literature but as a working tool. I'm not retelling it — there's plenty of that online. I'm breaking down four propositions that genuinely changed my approach to projects and tying them to the decisions I made — or, conversely, didn't make — over the next four years.
Thesis 1. Failure stories matter more than success stories
"A victory is often individual and outwardly appears open. The motives, the past, the starting point are unclear. Often it's simply luck."
I rewrote this quote in my notes three times in a row to make it stick. It explains why the stories of successful people are useless to those who are just starting out.
When I listen to an interview with a founder whose product took off, I hear a post-hoc rationalization. The person looks back and reconstructs the logic. In reality, at the moment of the decision, he didn't have that logic. He had a gut feeling, luck, chance, and a thousand unaccounted-for factors.
My first product, Meerno, failed. 500 downloads, 0 rubles. But the failure turned out to be more informative than other people's successes. I know exactly what I did wrong. I didn't validate demand before building, I chose native iOS instead of a quick Telegram bot for validation, and I misjudged what would motivate users to pay. If I hadn't failed, I wouldn't have that knowledge.
When people ask me now how to build a first product, I don't talk about MeerGuard, which has 9000+ users. I talk about Meerno. Because MeerGuard grew out of Meerno's mistakes, and without them it wouldn't exist.
What changed in my work. I stopped being proud of successes and I'm not ashamed of failures. I end every client project not with a post-mortem of "here's how great it turned out," but with a list of "what I did that wasn't optimal." That list is my main asset, worth more than a portfolio.
Thesis 2. Better with allies than alone
"If you're a black swan hunter, it's better to have allies than to hunt alone."
One man is no army. Everyone has heard it, but few people actually live by that principle. Especially among indie developers who take pride in "solo products."
I was the same. I built Meerno essentially alone. With a mentor and a contract backend developer, but no partner. A year and a half alone on the project. I could sustain concentration for four months at most, then motivation would drop, then rise again, then drop again. That's the normal cycle for one person.
I started MeerGuard with a partner. We're building MeerBot as a two-person team. The difference is enormous. Not in how tasks are split — technically, each of us can do everything. The difference is that we each have motivation slumps, and they never coincide. When I want to throw in the towel, my partner is driven. When he has a hard week, I carry it. All told, there's never a day on the project when no one is moving forward.
That's what "hunting the black swan as a pair" means. It's not about money, not about roles. It's about the fact that the black swan demands sustained concentration amid uncertainty, and one person can't hold that alone.
What changed. I no longer pick partners "by competence." I used to look at it this way: this one is strong in design, this one in marketing, I'm strong in code. Now I look at something else. Is this person able to carry the load when I can't? And conversely, can I carry it when he can't? Competencies you can buy or learn. Emotional endurance in a team, you can't.
Thesis 3. The cumulative effect
"The intensification of the effect of an explosion by concentrating it in a given direction. The poor lose, and the rich multiply. The transmission of ideas happens in the same epidemiological way."
For a long time I didn't understand how this thesis applies to development. I got it later. It's about results adding up in one direction.
When I take on a client iOS project, I get more than money. I get:
- A new case study for my portfolio
- Experience with a specific library or framework
- Sometimes a testimonial or a referral
- Sometimes repeat business
- Sometimes a project from someone in that client's network
If all my projects are in one area (native iOS, AI integrations, Telegram bots), the effect compounds. I become known in that niche, people come to me more and more often, and I can raise my price.
If I take one app in Flutter, one in React Native, one in Kotlin Multiplatform, each project will bring in money on its own, but the effect won't add up. I'll be a mid-level developer in three stacks instead of a lead in one.
I deliberately turn down work in stacks I don't use. That goes against the "take everything you're offered" principle. But it works in favor of the cumulative effect. Over three years I became not just an "iOS developer" but the person people come to with "iOS, AI, Telegram, VPN infrastructure" tasks. It's a very narrow niche, and in it, people know me.
What changed. I look at a new project not in terms of "will it make money" (yes, everyone looks at that), but "does it add up with what I've already done." If not, I either decline or raise the price to offset the lack of cumulative effect.
Thesis 4. Choosing a field with "good" black swans
"When choosing a profession, you can lean toward the kind of work where good black swans are possible."
Taleb gives an example. An actor and a bus driver work equally hard, but the actor has a higher chance of waking up famous. That doesn't mean the actor is better, and it doesn't mean the driver is unhappy. It's about the distribution of possible outcomes.
I applied this thesis to choosing what to do. I had several options. Stay in sales, take a job as a project manager, learn programming for my own products. The first two are stable and predictable. The third has a long tail of possibilities. You can stay a freelancer, you can build a product that takes off, you can assemble a team, you can build an agency.
I chose the third. And it's not because I'm sure of success. It's because the third option has a chance of success that exceeds expectations. In the first two, the ceiling is clear and low.
Four years later, I have freelance income, I have my own product with 9000+ users, I have a growing MeerBot with paying clients. The black swan hasn't arrived yet, but the opportunities for one are there.
What changed. When I choose a project or a task, I look not only at the expected outcome but also at the tail of the distribution. A task like "build a landing page for a client for 50K" has almost no tail. I get exactly what I earn. A task like "build an MVP of MeerBot and try to sell it to the first ten businesses" has a huge tail. It could come to zero, it could turn into a product at $10K MRR, it could turn into a product someone big buys. I prefer the second, even if the expected value is lower.
What I stopped doing
I stopped planning five years out. Five-year plans don't work in a startup. If nothing unforeseen happens in five years, it means I wasn't doing anything interesting. Long-term plans are written for predictable systems. We work with unpredictable ones.
I stopped looking at success stories as templates. Listening to interviews is useful, but not for replication. I watch them as the context of an era, not as instructions. Instructions only work in systems where the rules are fixed. In startups, the rules change to fit you.
I stopped being afraid of mistakes in general. Specific expensive ones (losing user data, breaking an agreement with a client) — yes, those I'm afraid of. The "afraid just because" kind of mistake — no. Every cheap mistake brings knowledge you can't get any other way.
What I didn't do thanks to Taleb
I didn't take on a partner I liked but who didn't pull his weight. There was a temptation. The guy is great, we're friends. Taleb reminded me: emotional endurance matters more than competence. We stayed friends and didn't become partners. A year later I saw I was right. He got stuck in his comfort zone, and the project we could have gone into together I would have been doing alone.
I didn't take an order that was attractive money-wise but wasn't in my niche. I was offered a cross-platform app in Flutter. The price was good, the scope of work was interesting. I turned it down. The cumulative effect wouldn't have come together. I don't regret it now.
I didn't build an MVP "like everyone else's." Every time someone says "let's do it like Notion / Slack / Whoever," I think about how that success was a black swan, impossible to copy. We can borrow the mechanics, but we won't repeat the trajectory. Better to build an honest product for a specific niche than a copy of a big player.
What to take away
In short:
- Your failures are worth more than other people's successes. Start a list of "how I screwed up."
- A partner isn't for splitting the work; a partner is for keeping your motivation up when you don't have enough of your own.
- The cumulative effect only adds up when you concentrate your efforts in one niche. Spreading thin is an illusion of diversification.
- A field with good black swans matters more than a predictable field. Not because the swan is guaranteed to arrive, but because the tail of the distribution is wider.
- Plans, yes. Long-term plans, no. Hypotheses and tests, yes. Five-year strategies are garbage.
And the main thing. Taleb didn't teach me how to think. He taught me to doubt my own certainties. That's his real gift: to be able to look at your own plan and see the holes in it before you fall into them.
What's next
Thinking about your own project and not sure which way the tail of the distribution is moving? Write to me and we'll work through your hypothesis — I won't begrudge the hour. If you decide to go ahead, we'll rough out a budget.


