Every Building Journey Deserves Respect

Yesterday, I shared a simple observation from my own work: Claude Opus 4.8 currently fits the way I build better than Opus 5.

It was not an absolute conclusion.

I was not saying that Opus 5 is a bad model, nor was I claiming that everyone should have the same experience. I was simply doing what building in public means to me: sharing what I tried, what worked, what did not, and what I learned along the way.

Many people agreed with me. Others had completely different experiences.

Some found Opus 5 much stronger for coding and complex reasoning. Others discovered that changing the effort level made it work better. A few explained how they combine different models as architects, coders, reviewers, and orchestrators.

Those conversations were valuable because they were driven by curiosity.

We were not trying to prove that one experience was the only truth. We were placing different experiences next to each other so that everyone could understand these tools a little better.

That is what healthy disagreement can create.

I know I am not the best programmer in the world. I am certainly not an expert in using AI.

I am still learning, experimenting, making mistakes, correcting them, and continuing to build every day.

When we build in public, we cannot expect everyone to agree with our methods, vision, or ambitions. Different perspectives are part of the journey.

A thoughtful criticism can reveal something we missed. A different experience can introduce a better approach. The right question at the right moment can even change the direction of a product.

But criticism and humiliation are not the same thing.

Disagreeing with someone’s technical choices is normal. Mocking their work, dismissing their effort, or attacking the person behind the product is something entirely different.

Everything I share on this journey is real.

Behind Kitwork are years of learning, time taken away from other opportunities, money spent on infrastructure and experiments, architectural decisions that turned out to be wrong, code that had to be rewritten, and countless iterations that most people will never see.

Kitwork is still small.

It currently serves two customers and handles real traffic from people across the Internet. That may not sound impressive compared with large companies or widely adopted open-source projects, but it is real.

Real people are using something that once existed only as an idea in my mind.

For me, that is enough reason to keep learning, improving, and shipping.

Kitwork may never become a successful product.

Its direction may be too unusual, too early, or simply irrelevant to most people. Some of its current ideas may eventually prove to be wrong.

I accept all of those possibilities.

But it remains the serious work of someone trying to turn an idea into reality.

I do not expect everyone to like Kitwork. I do not expect everyone to understand why I am building a runtime, language, compiler, bytecode engine, and virtual machine from the foundations up.

I only believe that people in technology should be able to criticize each other’s work without dismissing the human effort and ambition behind it.

What keeps me building is not universal agreement.

It is the sincere encouragement, thoughtful feedback, honest disagreement, and unexpected connections that come from sharing the unfinished journey.

Sometimes, two builders use the same tool and reach completely different conclusions.

Sometimes, someone from another part of the world discovers your work through a single post.

Sometimes, a stranger offers an idea that changes how you think.

Sometimes, a few kind words give a builder enough energy to continue for another day.

That is the build in public community I believe in.

It is not only a place to announce launches, celebrate revenue, or display polished results.

It is a place to share unfinished work, failed experiments, difficult decisions, lessons learned, and the slow process of becoming a better builder.

Every builder begins somewhere different.

Every product carries a story that outsiders may never fully see.

Behind even the smallest project may be someone’s nights, savings, doubts, family responsibilities, abandoned ideas, and belief that something better can still be created.

That is why every building journey deserves respect.

There is a story often shared in Buddhist teachings: when someone offers you a gift and you refuse to accept it, the gift remains with the person who brought it.

An insult can be treated in the same way.

I do not have to carry every unkind word into my work. I do not have to let someone else’s contempt become part of my identity or the story of what I am building.

I can leave it with them and return to the work.

So I will continue building.

I will continue experimenting, failing, rewriting, learning, and sharing what I discover.

Not because I need to prove that I am always right.

Not because I believe Kitwork must succeed at any cost.

I will continue because the journey itself is teaching me how to think, how to create, and how to become the kind of builder I want to be.

And perhaps by documenting that journey honestly, another builder somewhere will feel a little less alone.

Putting people and their work down does not make us or our own work more valuable.

But a sincere word of encouragement, an honest perspective, a moment of empathy, or a little help at the right time can give someone the strength to continue building.

Sometimes, that small act creates more value than we will ever know.

The real measure of a builder is not how effectively they can diminish someone else’s work.

It is what they create, what they contribute, what they help others understand, and how they treat people while everyone is still trying to find their way forward.