The Courage to Be Disliked: A Life-Altering Book for Indie Developers

⏱️ Reading time: approx. 10 min

Introduction
Denying Trauma and the Thirst for Approval
Horizontal vs. Vertical Relationships
Separation of Tasks
The Anatomy of True Happiness
Conclusion

1. Introduction

Key Takeaways from This Article

Cease living at the mercy of other people's judgment.
Gain unwavering, grounded confidence in your own software and writing.
Formulate an unmistakable internal compass for deciding what to build next.

Who This Is For

Developers, creators, and professionals intrigued by The Courage to Be Disliked and Adlerian psychology.
Anyone yearning to regain sovereign ownership of their career and emotional well-being.

Who This Is Not For

Those completely untroubled by self-doubt or external expectations.

Published in Japan in December 2013, The Courage to Be Disliked (by Ichiro Kishimi and Fumitake Koga / Diamond, Inc.) has surpassed 10 million copies sold globally. Framed as a fierce, razor-sharp dialogue between a cynical youth and an Adlerian philosopher, its pages gripped me like an electric current.

The philosopher’s core declaration struck like a lightning bolt:

"Your unhappiness cannot be blamed on your past. You yourself have chosen that unhappiness."

When I first encountered those words, I was genuinely furious.
"Excuse me? Who on earth would deliberately choose to be miserable?"

Yet as I kept reading, defensive indignation dissolved into profound, quiet conviction.

In this essay, I explore how Adlerian wisdom transforms the daily emotional battles of software creators, indie hackers, and builders.

2. Denying Trauma and the Thirst for Approval

Trauma Does Not Exist

Perhaps the most provocative pillar of Adlerian thought is the outright denial of psychological determinism:

"Trauma does not exist."

To be precise: past events do not dictate who you are right now.

Freudian psychoanalysis leans on etiology (cause and effect): "Because you endured X in your childhood, you are helplessly suffering Y today."
Alfred Adler, by contrast, operates on teleology (purpose and goals): "Because you currently wish to maintain a specific defensive posture today, you summon past experiences as your rationalization."

This is a complete 180-degree perceptual inversion.

Consider an indie hacker who laments:

"The last app I launched got zero traction. That trauma shook me so badly that I can't muster the courage to ship anything new."

Through a Freudian lens, this sounds reasonable. A painful past failure wounded their fragile ego, causing analytical paralysis. Poor soul.

Adler, however, delivers a merciless diagnosis:

"You summon your past failure because you have already decided that you do not want to ship right now."

In plain terms: you are terrified of shipping, terrified of hearing crickets, terrified of negative reviews. To flee that immediate, uncomfortable fear, you seize upon past failures as a convenient shield.

It stings. It cuts right to the bone.

Yet it holds boundless hope. If the past does not chain your feet, your stillness is simply an active, present-tense choice. And if you are choosing stillness, you possess the sovereign power to choose movement instead.

You cannot rewrite historical events, but you retain absolute freedom over how you interpret them. Whether you view past flops as "fatal trauma" or as "compounding tuition" is a judgment call that belongs entirely to you today.

Renounce the Thirst for Validation

Adler dissects our addiction to social approval with equal ruthlessness:

"You must never use the desire for praise as the primary engine of your actions."

For indie creators, this lands right between the eyes.

Let's tell the truth.
Most builders harbor a secret longing for applause. We want peers to marvel: "That's incredible! How did you build that all by yourself?"

We post launch tweets on X, refreshing obsessively to count impressions.
We debut on Product Hunt, staring anxiously at upvote leaderboards.
We check GitHub stars like dopamine slot machines.

Such cravings are deeply human. The catastrophic pathology emerges when validation becomes the primary fuel of your creative engine.

When you are governed by the need for approval:

You pivot to building products designed to chase algorithmic trends rather than solving authentic problems.
You trap yourself in toxic perfectionism, paralyzed by the fear that someone might scoff at your work.
You poison your mental health comparing your modest milestones to viral success stories.
You extinguish your internal spark, handing the master power switch of your self-worth to strangers on the internet.

Living this way is indistinguishable from running someone else's errand for your entire life.

Adler summarizes the antidote in one immortal maxim:

"Freedom is being disliked by other people."

If your emotional survival depends on everyone approving of your choices, you will remain perpetually enslaved. Universal acclaim is mathematically impossible.

3. Horizontal vs. Vertical Relationships

Adlerian psychology rejects vertical relationships (hierarchies of superior vs. inferior) and advocates for horizontal relationships (equal dignity despite distinct roles).

In corporate hierarchies, people judge their value by titles, salary bands, and managerial deference. They flatter bosses and condescend to subordinates.

When creators carry this hierarchical conditioning into the open market, disaster strikes. They either grovel before potential enterprise clients as timid subservients or look down upon casual users with technical snobbery.

In a healthy creative life, you stand on horizontal ground:

A customer paying for your software is not your feudal master; they are a peer engaging in voluntary, mutual value exchange.
A prominent influencer reviewing your tool is not inherently superior to you; they simply possess an audience, while you possess a functional codebase.
A critical user complaining on a forum is neither a judge nor an enemy; they are simply offering feedback regarding their subjective experience.

When you treat every participant as a horizontal peer, interpersonal terror evaporates. You stop flattering, you stop cowering, and you build software from a position of quiet, dignified equilibrium.

4. Separation of Tasks

If you take only a single practical concept from Adler, let it be this:

"The Separation of Tasks (課題の分離 - Kadai no Bunri)."

Ask yourself with surgical clarity: "Whose task is this, ultimately? Who bears the direct consequence of this choice?"

Consider shipping a software product:

Building clean architecture, designing an intuitive interface, and hitting "Publish" is YOUR task.
Whether a user clicks buy, writes a glowing testimonial, or dismisses it as redundant garbage is THE USER'S task.

You have zero control over how another human being perceives or reacts to your work. Attempting to manage, manipulate, or worry about other people's tasks is the universal root of psychological exhaustion.

[Your Task: 100% Controllable]
- Write the code
- Polish the copy
- Deploy the build
- Set fair pricing

--- THE DEMARCATION LINE ---

[Other People's Task: 0% Controllable]
- Will they purchase?
- Will they applaud or criticize?
- Will the algorithm promote it?

Focus with fierce discipline only on your side of the boundary. When you release a project, send it into the world with wholehearted commitment, step back, and leave the judgment to the market. Whatever they decide is their task, not yours.

5. The Anatomy of True Happiness

What is real happiness according to Adler?

"Happiness is the subjective feeling of contribution (貢献感 - Kōkenkan)."

Notice the precision of this phrasing: it is not about being acknowledged for your contribution. It is the internal, quiet conviction that "I am of use to someone in this community."

If your happiness depended on external recognition, you would be back in the prison of validation. But when happiness is rooted in the quiet realization that your software solved a real friction for a human being, you become immune to vanity.

Even if your indie project serves only twenty niche users worldwide, if it saves each of them two hours of grueling administrative busywork every week, you have made a tangible contribution to human welfare. That knowledge alone is complete and self-sustaining.

You do not need viral fame. You do not need venture capital accolades. You only need the quiet certainty that your effort made the world slightly less friction-filled for someone else.

6. Conclusion

The Courage to Be Disliked is not an excuse to be rude, arrogant, or antisocial.
It is the resolve to live your own life without surrendering your compass to external approval.

As builders and developers, we step into the arena every time we ship:

We accept that some will misunderstand our vision.
We accept that some will criticize our pricing.
We accept that our projects will not please everybody.

And we ship anyway.

Because our task is to build, contribute, and grow. Everything else belongs to the world.

Reclaim your agency. Separate your tasks. Ship your work.

Do you have the courage to build what you believe in, even if it is misunderstood?

The Courage to Be Disliked: A Life-Altering Book for Indie Developers